The cast

Meet the thirteen agents

Your whole AI team, in one place. Each agent owns one part of building a feature. They start on their own, hand work to each other, and all work from the same up-to-date picture of your code.

The shift

AI helps with the code. The process is still manual.

Triage, specs, estimates, status updates and retrospectives are still done by hand on most teams. That is the part these agents take on.

84%

of developers are using or planning to use AI tools in their development process, up from 76% the year before.

SourceStack Overflow Developer Survey 2025· 33,662 responses

Industry research from the sources linked above. These are not Glideship results.

The roster

Thirteen agents, one job each.

Grouped by the part of the work they own, in the order they act on a feature.

01

Intake and spec

Turn a request into a written spec.

2 agents

  • Chat / Slack Event

    Triage Agent

    Asks the right questions, spots duplicates, sizes the work and suggests a priority.

    • Intake interview
    • Duplicate detection
    • Priority scoring
    • Complexity estimation
  • PM Trigger

    BUD Agent

    Writes the spec from your real code, your team's rules and similar past work.

    • Codebase context
    • Enterprise rules
    • Competitor analysis
    • Tech spec + tests
02

Design and plan

Shape the build and suggest who does it.

3 agents

  • BUD Approved

    Design Agent

    Draws wireframes that use your product's own colours, fonts and components.

    • HTML wireframes
    • Design system aware
    • UX considerations
    • Accessibility
  • BUD Approved

    Tech Plan Agent

    Turns an approved BUD into a step-by-step build plan, down to which files to change.

    • Architecture analysis
    • File-level TODOs
    • Dependency mapping
    • API contracts
  • Phase Gate Approved

    Smart Assignment Agent

    Suggests the best developer for the job by skills, workload and who knows the code.

    • Skill matching
    • Capacity balancing
    • Module expertise
    • Workload optimization
03

Build and track

Keep the board true without status meetings.

2 agents

  • GitHub Webhook

    Status Agent

    Watches pull requests, moves each BUD forward when code merges, and keeps everyone posted.

    • PR merge detection
    • Status from branches
    • Folder management
    • Notifications
  • Daily Cron 08:30

    Standup Agent

    Writes the daily standup from commits, pull requests, bugs and chat, and flags risks early.

    • Activity aggregation
    • Risk flags
    • Lagging BUD alerts
    • Scope tracking
04

Test and quality

Test the work and send bugs back to the right place.

3 agents

  • Dev Complete

    Test Plan Agent

    Writes automated tests and manual test cases from the BUD's acceptance criteria and the code.

    • Playwright e2e
    • Unit/integration tests
    • Manual UAT cases
    • Security tests
  • New Bug Filed

    Bug Linker Agent

    Connects each new bug to the feature it came from, and calls for help when bugs pile up.

    • Bug-BUD linking
    • Bug limit watch
    • Calls in reassignment
    • Classification
  • Bug Linker Trigger

    Reassignment Agent

    Sends the developer back to review bugs, moves QA on to the next BUD, keeps workloads even.

    • Dev reassignment
    • QA rotation
    • Team notification
    • Workload balance
05

Learn and grow

Learn from every release and keep the team sharp.

3 agents

  • BUD Deployed

    Learning Agent

    Writes the retrospective, compares estimates with reality, and remembers the lessons.

    • Cycle time analysis
    • Estimate accuracy
    • Pattern matching
    • Retrospectives
  • Daily Cron 02:00

    Skill Agent

    Keeps skill profiles current and warns when only one person knows a part of the code.

    • Profile rebuilds
    • Skill scores
    • Bus factor alerts
    • Recommendations
  • Weekly Cron

    Quiz Master Agent

    Turns your own features into a daily team quiz, so everyone keeps up with what you've built.

    • AI question generation
    • Admin approval queue
    • Scheduled daily play
    • Gamified leaderboard + SP
How they work

Same rules for all thirteen.

  1. Step 1

    Something starts it

    An event, a phase gate or a schedule. A Slack message, a merged pull request, a new bug or the morning standup.

  2. Step 2

    It works from your code

    Every agent reads the same picture of your code. That picture is re-learned on every pull-request merge to your main branch.

  3. Step 3

    A person decides

    What comes out is a draft. A person reviews it, changes it if needed and decides what happens next.

Runs onClaude CodeGitHub CopilotOpenAI CodexOllama (local)

Put the agents to work

Get started on GitHub

One command. Needs Docker and Node.js 18 or later. Your code and data stay on your machine. npx glideship init