/bootstrap

The single-entry-point aggregator command that runs the full four-phase project bootstrap wizard. One command, one run, ready to ship.

v1.6.0+ — Phase 4 is beads-native. New forks never see GitHub Projects. The wizard creates and seeds the beads tracker (bd), not a GitHub project board.

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 the per-phase commands in sequence, checking idempotency markers in .claude/.bootstrap-status so it skips phases that are already complete.

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`	Beads tracker + branch protection + seeded backlog

After a successful run you have a configured project: seven specialized agents, a beads tracker with the seeded backlog visible via bd ready, branch protection on main, and the two durable planning artifacts every agent reads on every session start.

No GitHub project board is created. The visual board is .gembaflow-boards/kanban.html — a read-only HTML projection of bd state rendered locally by hooks.

Usage


/bootstrap           # default — skip phases already marked complete
/bootstrap --force   # ignore status markers, re-run every phase

No --force on first run. The wizard prompts you interactively for product details, architecture choices, and GitHub configuration.

PAT scopes required

Scope	Required
`repo`	Yes
`workflow`	Yes
`project`	No — beads needs none

/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