Stagekeeper docs — Claude Code pipeline with approval gates
Learn how Stagekeeper connects Claude Code to a development pipeline, approval gates, and records in your own repository.
Your session runs the work
Stagekeeper keeps the board, pipeline state, approval gates, and records. Your own Claude Code session runs the agents and changes files in your repository. Stagekeeper does not run agents for you.
Add an item to the backlog, choose where the pipeline should wait, and continue from your session. Start with Get started, then read how automation works.
Steps and responsibilities
The pipeline decides the order. Required steps stay in every runnable pipeline; other steps depend on the plan and the saved definition.
| Step | Who runs it | In the pipeline | Available on |
|---|---|---|---|
| Plan | dev | Required | Free, Pro, Max |
| Verify | plan-verifier | Optional | Pro, Max |
| Implement | dev | Required | Free, Pro, Max |
| Implementation check | impl-verifier | Opt-in | Pro, Max |
| QA | qa-verifier | Opt-in | Pro, Max |
| Accept | Your session | Required | Free, Pro, Max |
| Doc audit | doc-auditor | Optional | Pro, Max |
| Scout | feature-scout | Opt-in | Free, Pro, Max |
Availability means the step is permitted by your plan. Free keeps its default pipeline; editing opens on Pro. Automatic scouting is separate from an item's Scout step.
The workspace dev agent writes the plan and implementation. Accept is your main session reproducing the result and recording the five acceptance checks. It is separate from an approval gate.
Default pipelines by plan
Free
- Plan
- Implement
- Accept
Pro
- Plan
- Verify
- Implement
- Accept
- Doc audit
Max
- Plan
- Verify
- Implement
- Accept
- Doc audit
The default gates wait before Plan and Implement. On plans that allow editing, you can choose different gates and steps. Learn how to edit pipelines and approve gates.
Verified only with a record
A submitted plan is not automatically Verified. That label appears only after an independent pass has a validation record. Verify is optional in an editable pipeline; without that record the item remains Not verified.
Done means the implementation span has finished. Accepted also needs the main session's acceptance record. Plans and reports are committed alongside your code; the board keeps their references.