/bootstrap-product
The first phase of project setup — guides you through a structured
questionnaire that produces docs/PRODUCT-REQUIREMENTS.md and
docs/PRODUCT-ROADMAP.md, the documents every later phase reads.
When to use it
Run this immediately after cloning a fresh Gemba Flow project and before any agents start work. The command walks you through a question sequence — what you’re building, who it’s for, what problem it solves, what’s in scope for the MVP, what comes after — and produces the PRD and roadmap as artifacts. Without these artifacts, downstream commands have nothing concrete to reason about, and agents fall back to generic engineering judgment instead of project-specific guidance.
If you’ve already done the strategic homework with
/research, /jtbd, and
/positioning, this command reads those
artifacts at the start and pre-fills the relevant sections. You’re
then confirming or correcting rather than typing from scratch. The
Plan phase is the leverage point — one focused session there saves
you from re-deriving the same answers in the bootstrap questionnaire.
Don’t skip this even if you “already know” what you’re building. The act of writing it down surfaces the parts you thought were locked but weren’t. Future agents will read the PRD; the operator’s mental model is not enough.
How it fits
Inputs are the Plan phase artifacts (optional but valuable).
Outputs are the PRD and roadmap, which become the substrate for
/bootstrap-architecture.
What it does (quick)
- Reads any existing Plan phase artifacts and pre-fills sections
- Walks the structured questionnaire one question at a time
- Drafts
docs/PRODUCT-REQUIREMENTS.md— problem, audience, success criteria, scope boundaries, non-functional requirements - Drafts
docs/PRODUCT-ROADMAP.md— phased feature list, success criteria per phase, target dates, risks and mitigations - Surfaces the decisions you skipped without realizing — these become open items at the bottom of the PRD
Related commands
/research+/jtbd+/positioning— upstream Plan phase that enriches this command’s inputs/bootstrap-architecture— successor; reads the PRD this command produced/lock-scope— the gate that locks MVP scope after both bootstrap-product and bootstrap-architecture have shipped
Canonical spec: .claude/commands/bootstrap-product.md