From a Slack message to production. Agents handle triage, specs, estimates and retrospectives, and people review and decide. No sprints, no story points, no standups.
Specs, status updates, estimates and meetings fill the rest. That is the work Glideship hands to agents, so people keep the decisions and get the time back.
is how much of their time developers spend coding, Atlassian reports. The rest of the week goes on everything around the code.
Industry research from the sources linked above. These are not Glideship results.
Every feature follows the same path. At each step an agent drafts the work and a person reviews it, changes it and moves it on.
Someone asks for something in Slack. The Triage Agent reads it, checks for duplicates and runs a short interview about business impact, who it is for, timing and dependencies.
Reads the request, looks for duplicates, sizes the work from the code, and suggests a priority to the product manager.
Shares the idea and answers the questions. A product manager or the org owner reviews the triage, adjusts it and moves it on to a BUD.
An agent never ships on its own say-so. Each draft lands in front of a person, who can approve it, change it or send it back.
of developers distrust the accuracy of AI tools, more than the 33% who trust it. Only 3% highly trust the output.
SourceStack Overflow Developer Survey 2025· 33,244 responses
Agent-Driven Development (ADD) is a way of building software where specialised AI agents drive every phase of the lifecycle — intake, spec, design, tech architecture, implementation, testing, UAT, deployment, retrospective — and humans review, decide, and steer. Glideship is the open-source reference implementation.
Yes — for the workflow layer. Glideship sits between IDE-side AI coding assistants and traditional PM tools. It is especially relevant to teams looking for an Atlassian DC alternative, since Atlassian is sunsetting new self-hosted Jira licences in March 2026 with full shutdown in 2029.
The data plane is always local — Postgres, embeddings, BUDs, scanned repos, and the audit log all sit on your hardware. Only the LLM prompts leave your machine, and only when you choose a cloud inference mode.
BUD stands for Business Understanding Document. Every feature lives in one BUD containing spec, tech spec, test plan, acceptance criteria, and full history — all in markdown.
Glideship is licensed under the Apache License 2.0, which permits commercial use including embedding in proprietary products. Contributions require DCO sign-off via git commit -s.
One command. Needs Docker and Node.js 18 or later. Your code and data stay on your machine. npx glideship init