Slash Commands
Gemba Flow ships a set of slash commands you run from inside Claude Code to drive the framework’s workflow. This page is the cheat sheet — every command, grouped by SDLC phase, with one-line “when to use” and example invocation. Per-command pages with diagrams and deeper context live under the phase groups in the sidebar.
All commands by phase
1. Plan & evaluate
| Command | When to use | Example invocation |
|---|---|---|
/research | Build a competitive landscape before defining the product | /research |
/jtbd | Ground the PRD in real user motivations, not assumptions | /jtbd |
/positioning | Decide the differentiation story (Dunford framework) | /positioning |
/evaluate-feature | Decide BUILD / DEFER / DECLINE on one feature request | /evaluate-feature "bulk export" |
/lock-scope | Formally lock MVP scope before execution begins | /lock-scope |
2. Set up & maintain
| Command | When to use | Example invocation |
|---|---|---|
/bootstrap | Run the full four-phase bootstrap wizard in one command | /bootstrap |
/bootstrap-product | Draft the PRD + roadmap from a structured questionnaire | /bootstrap-product |
/bootstrap-architecture | Define the technical architecture from the PRD | /bootstrap-architecture |
/bootstrap-agents | Inject project-specific context into agent configs | /bootstrap-agents |
/bootstrap-workflow | Activate the board, branch protection, seed backlog | /bootstrap-workflow |
/doctor | Health-check the local + remote environment | /doctor |
/upgrade | Sync framework files from the latest upstream release | /upgrade |
3. Groom & prioritize
| Command | When to use | Example invocation |
|---|---|---|
/create-ticket | File a single ticket against Definition of Ready | /create-ticket |
/groom-backlog | Prioritize backlog + promote top tickets to Ready | /groom-backlog |
/sprint-status | Read-only board health snapshot | /sprint-status |
/check-milestone | Milestone-scoped progress + risk report | /check-milestone M1 |
4. Implement
| Command | When to use | Example invocation | Status |
|---|---|---|---|
/work-ticket | Ship the top Ready ticket through PR + CI + review | /work-ticket | GA |
/quick-fix | Apply a small change without ticket ceremony | /quick-fix fix typo | GA |
/swarm | Run N parallel implementations of one ticket | /swarm 3 #123 | GA |
/drain | Drain the Ready column autonomously overnight | /drain --include-reversible | GA |
/goal | Promote a feature flag from dark-shipped to GA | /goal deploy --feature my-flag | GA |
/eli5 | Translate a ticket / PR for non-engineer readers during implementation | /eli5 #91 | GA |
5. Review & ship
| Command | When to use | Example invocation |
|---|---|---|
/review-pr | Review a PR; GO / NO-GO recommendation | /review-pr 234 |
/architect-review | Architectural guidance on a single design question | /architect-review "auth shape" |
/test-feature | Draft + execute a feature-level test plan | /test-feature "auth flow" |
/release-decision | Explicit go / no-go gate for a whole release | /release-decision v2.0 |
/eli5 | Translate a ticket / PR for non-engineer readers during review | /eli5 #91 |
6. Reflect & communicate
| Command | When to use | Example invocation |
|---|---|---|
/log-session | Capture a session journal + propose memory entities | /log-session |
/prune-memory | Archive stale Memory MCP entities via time-decay | /prune-memory |
/validate-memory | Ensure Done tickets have CompletedTicket entities | /validate-memory |
/report-issue | File a structured bug report to upstream Gemba Flow | /report-issue |
Visual overview
The phases are designed as an SDLC progression — Plan precedes Setup
precedes Grooming precedes Implementation precedes Review precedes
Reflection — but commands inside a phase are not strictly sequential.
For example, /sprint-status and /check-milestone are observational
commands you might run anywhere in the cycle; /quick-fix is a
lightweight alternative to /work-ticket rather than a successor.
The phase grouping answers “where in the SDLC does this command live?”
not “in what order do I run the commands within a phase?”
Workshop printing
This page is designed to print cleanly — the tables flow column-by-column and the swimlane diagram fits a single sheet at landscape orientation. Workshop participants can grab a printed copy and follow along as the phases are introduced.