/bootstrap
The single-entry-point aggregator command that runs the full four-phase project bootstrap wizard. One command, one run, ready to ship.
When to use it
Run /bootstrap once when you first clone the Gemba Flow template into your
own repository — before /groom-backlog, before /work-ticket, before
anything else. The wizard asks questions in order and writes the durable
artifacts every subsequent agent reads as context.
You can also re-run individual phases via /bootstrap-product,
/bootstrap-architecture, /bootstrap-agents, or /bootstrap-workflow to
refresh a single artifact without re-running the full sequence. Those
per-phase commands continue to work independently; /bootstrap wraps them,
not replaces them.
How it works
Under the hood, /bootstrap runs:
bash bootstrap.shThe shell script orchestrates the four phases in order, passing the output artifact from each phase as input context to the next.
What it creates
| Phase | Per-phase command | Artifact |
|---|---|---|
| 1 — Product | /bootstrap-product | docs/PRODUCT-REQUIREMENTS.md |
| 2 — Architecture | /bootstrap-architecture | docs/TECHNICAL-ARCHITECTURE.md |
| 3 — Agents | /bootstrap-agents | Updated .claude/agents/ configs |
| 4 — Workflow | /bootstrap-workflow | GitHub board + branch protection |
After a successful run you have a configured project: six specialized agents,
a project board with five columns (Backlog, Ready, In Progress,
In Review, Done), branch protection on main, and the two durable
planning artifacts every agent reads on every session start.
Usage
/bootstrapNo arguments. The wizard prompts you interactively for product details, architecture choices, and GitHub configuration.
Related commands
/bootstrap-product— Phase 1 only/bootstrap-architecture— Phase 2 only/bootstrap-agents— Phase 3 only/bootstrap-workflow— Phase 4 only/doctor— verify the environment after bootstrapping/upgrade— sync framework files from a later release
Canonical spec: .claude/commands/bootstrap.md