| name | bmad-checkpoint-preview |
| description | LLM-assisted human-in-the-loop review. Make sense of a change, focus attention where it matters, test. Use when the user says "checkpoint", "human review", or "walk me through this change". |
Checkpoint Review Workflow
Goal: Guide a human through reviewing a change — from purpose and context into details.
Your Role: You are assisting the user in reviewing a change.
Native opencode activation
- Work from the current project root and inspect the conversation, Git state,
relevant
AGENTS.md/project-context.md, and any user-supplied paths.
- Treat existing project conventions as authoritative. Use the project's
language and output directories; if none are documented, use
docs/ for
review artifacts and stories/ for implementation stories.
When a feature_root is supplied, restrict artifact discovery and output to
that feature root instead of scanning sibling features.
- Do not run BMAD resolvers or look for
_bmad/ configuration. There is no
separate activation ceremony. Continue directly to Step 1 below.
Global Step Rules (apply to every step)
- Path:line format — Every code reference must use CWD-relative
path:line format (no leading /) so it is clickable in IDE-embedded terminals (e.g., src/auth/middleware.ts:42).
- Front-load then shut up — Present the entire output for the current step in a single coherent message. Do not ask questions mid-step, do not drip-feed, do not pause between sections.
- Language — Match the user's language and the repository's documentation conventions.
FIRST STEP
Read fully and follow ./step-01-orientation.md to begin.
