diff --git a/docs/explanation/named-agents.md b/docs/explanation/named-agents.md index e5a92511c..ba17851ad 100644 --- a/docs/explanation/named-agents.md +++ b/docs/explanation/named-agents.md @@ -77,7 +77,7 @@ Every agent ships a `customize.toml` with sensible defaults. Teams commit overri Most users never hand-author these files. The `bmad-customize` skill walks through picking the target, choosing agent vs workflow scope, authoring the override, and verifying the merge — so the customization surface stays accessible to anyone who understands their intent, not just those fluent in TOML. -Concrete example: a team commits a single file telling Amelia to always use the Context7 MCP tool for library docs and to fall back to Linear when a story isn't in the local epics list. Every dev workflow Amelia dispatches (dev-story, quick-dev, create-story, code-review) inherits that behavior, with no source edits or per-workflow duplication required. +Concrete example: a team commits a single file telling Amelia to always use the Context7 MCP tool for library docs and to fall back to Linear when a story isn't in the local epics list. Every dev workflow Amelia dispatches (quick-dev, code-review, qa-generate) inherits that behavior, with no source edits or per-workflow duplication required. There's also a second customization surface for *cross-cutting* concerns: the central `_bmad/config.toml` and `_bmad/config.user.toml` (both installer-owned, rebuilt from each module's `module.yaml`) plus `_bmad/custom/config.toml` (team, committed) and `_bmad/custom/config.user.toml` (personal, gitignored) for overrides. This is where the **agent roster** lives — the lightweight descriptors that roster consumers like `bmad-party-mode`, `bmad-retrospective`, and `bmad-advanced-elicitation` read to know who's available and how to embody them. Rebrand an agent org-wide with a team override; add fictional voices (Kirk, Spock, a domain expert persona) as personal experiments via the `.user.toml` override — without touching any skill folder. The per-skill file shapes how Mary *behaves* when she activates; the central config shapes how other skills *see* her when they look at the field. diff --git a/docs/explanation/project-context.md b/docs/explanation/project-context.md index 4d3a90768..6ddb73bb5 100644 --- a/docs/explanation/project-context.md +++ b/docs/explanation/project-context.md @@ -22,10 +22,8 @@ Every implementation workflow automatically loads `project-context.md` if it exi **Loaded by these workflows:** - `bmad-architecture` — respects technical preferences during solutioning -- `bmad-create-story` — informs story creation with project patterns -- `bmad-dev-story` — guides implementation decisions +- `bmad-quick-dev` — informs story planning and implementation with project patterns - `bmad-code-review` — validates against project standards -- `bmad-quick-dev` — applies patterns when implementing specs - `bmad-sprint-planning`, `bmad-retrospective`, `bmad-correct-course` — provides project-wide context ## When to Create It diff --git a/docs/how-to/expand-bmad-for-your-org.md b/docs/how-to/expand-bmad-for-your-org.md index 582eb329a..84f32800a 100644 --- a/docs/how-to/expand-bmad-for-your-org.md +++ b/docs/how-to/expand-bmad-for-your-org.md @@ -41,8 +41,8 @@ Rule of thumb: if the rule should apply everywhere an engineer does dev work, cu [agent] -# Applied on every activation. Carries into dev-story, quick-dev, -# create-story, code-review, qa-generate — every skill Amelia dispatches. +# Applied on every activation. Carries into quick-dev, code-review, +# qa-generate — every skill Amelia dispatches. persistent_facts = [ "For any library documentation lookup (React, TypeScript, Zod, Prisma, etc.), call the context7 MCP tool (`mcp__context7__resolve_library_id` then `mcp__context7__get_library_docs`) before relying on training-data knowledge. Up-to-date docs trump memorized APIs.", "When a story reference isn't found in {planning_artifacts}/epics-and-stories.md, search Linear via `mcp__linear__search_issues` using the story ID or title before asking the user to clarify. If Linear returns a match, treat it as the authoritative story source.", diff --git a/docs/reference/commands.md b/docs/reference/commands.md index 458a908d9..747d9a9a6 100644 --- a/docs/reference/commands.md +++ b/docs/reference/commands.md @@ -97,9 +97,8 @@ Workflow skills run a structured, multi-step process without loading an agent pe | `bmad-ux` | Design user experience | | `bmad-architecture` | Design system architecture | | `bmad-create-epics-and-stories` | Create epics and stories | -| `bmad-dev-story` | Implement a story | +| `bmad-quick-dev` | Implement a feature, fix, or story | | `bmad-code-review` | Run a code review | -| `bmad-quick-dev` | Implement a story or any other small intent — clarify, plan, implement, review, present | | `bmad-dev-auto` | Run one unattended development-loop iteration — small intent in, code out, no human interaction | See [Workflow Map](./workflow-map.md) for the complete workflow reference organized by phase. diff --git a/docs/reference/workflow-map.md b/docs/reference/workflow-map.md index 44733a179..3c3b298b3 100644 --- a/docs/reference/workflow-map.md +++ b/docs/reference/workflow-map.md @@ -81,17 +81,16 @@ Decide how to build it and break work into stories. ## Phase 4: Implementation -Build it, one story at a time. Phase 4 epic and story automation is now available also. So you can choose how you want to stay in the loop. You can choose the full flow, or go right to quick flow. +Build it with `bmad-quick-dev` as the official implementation method. The legacy `bmad-create-story` / `bmad-dev-story` split is deprecated and remains available only when explicitly invoked by name. -| Workflow | Purpose | Produces | -|------------------------|-------------------------------------------------------------------------------|------------------------------------------------------| -| `bmad-sprint-planning` | Initialize tracking (once per project to sequence the dev cycle) | `sprint-status.yaml` | -| `bmad-create-story` | Prepare next story for implementation | `story-[slug].md` | -| `bmad-dev-story` | Implement the story | Working code + tests | -| `bmad-code-review` | Validate implementation quality | Approved or changes requested | -| `bmad-correct-course` | Handle significant mid-sprint changes | Updated plan or re-routing | -| `bmad-sprint-status` | Track sprint progress and story status | Sprint status update | -| `bmad-retrospective` | Review after epic completion | Lessons learned | +| Workflow | Purpose | Produces | +|----------|---------|----------| +| `bmad-quick-dev` | Turn an intent or story into implemented, reviewed code | `spec-*.md` + code | +| `bmad-sprint-planning` | Initialize tracking (once per project to sequence the dev cycle) | `sprint-status.yaml` | +| `bmad-code-review` | Ad hoc review of any code change | Findings + applied patches | +| `bmad-correct-course` | Handle significant mid-sprint changes | Updated plan or re-routing | +| `bmad-sprint-status` | Track sprint progress and story status | Sprint status update | +| `bmad-retrospective` | Review after epic completion | Lessons learned | ## Quick Flow (Parallel Track) @@ -99,7 +98,7 @@ Skip phases 1-3 for small, well-understood work. | Workflow | Purpose | Produces | |------------------|---------------------------------------------------------------------------|--------------------| -| `bmad-quick-dev` | Unified quick flow — clarify intent, plan, implement, review, and present | `spec-*.md` + code | +| `bmad-quick-dev` | Turn an intent or story into implemented, reviewed code | `spec-*.md` + code | | `bmad-dev-auto` | Runs one unattended development-loop iteration — small intent in, code out | `spec-*.md` + code | For the reference on unattended development loops with `bmad-dev-auto`, see [Autonomous Development Loops](./dev-auto.md). @@ -107,7 +106,7 @@ For the reference on unattended development loops with `bmad-dev-auto`, see [Aut ## Context Management Each document becomes context for the next phase. The PRD tells the architect what constraints matter. The architecture -tells the dev agent which patterns to follow. Story files give focused, complete context for implementation. Without +tells the dev agent which patterns to follow. Spec files give focused, complete context for implementation. Without this structure, agents make inconsistent decisions. ### Project Context diff --git a/docs/tutorials/getting-started.md b/docs/tutorials/getting-started.md index defc88fd6..f8da0a50a 100644 --- a/docs/tutorials/getting-started.md +++ b/docs/tutorials/getting-started.md @@ -202,11 +202,12 @@ Invoke the **Developer agent** (`bmad-agent-dev`) and run `bmad-sprint-planning` For each story, repeat this cycle with fresh chats: -| Step | Agent | Workflow | Command | Purpose | -| ---- | ----- | ------------------- | ------------------- | ---------------------------------- | -| 1 | DEV | `bmad-create-story` | `bmad-create-story` | Create story file from epic | -| 2 | DEV | `bmad-dev-story` | `bmad-dev-story` | Implement the story | -| 3 | DEV | `bmad-code-review` | `bmad-code-review` | Quality validation _(recommended)_ | +| Step | Agent | Workflow | Command | Purpose | +| ---- | ----- | -------- | ------- | ------- | +| 1 | DEV | `bmad-quick-dev` | `bmad-quick-dev` | Create the story spec, implement, review, present | +| 2 | DEV | `bmad-code-review` | `bmad-code-review` | Additional quality validation _(recommended)_ | + +The older `bmad-create-story` / `bmad-dev-story` split flow is deprecated; `bmad-quick-dev` is the official implementation method. After completing all stories in an epic, invoke the **Developer agent** (`bmad-agent-dev`) and run `bmad-retrospective` (`bmad-retrospective`). @@ -246,8 +247,7 @@ your-project/ | `bmad-create-epics-and-stories` | `bmad-create-epics-and-stories` | PM | Break down PRD into epics | | `bmad-check-implementation-readiness` | `bmad-check-implementation-readiness` | Architect | Validate planning cohesion | | `bmad-sprint-planning` | `bmad-sprint-planning` | DEV | Initialize sprint tracking | -| `bmad-create-story` | `bmad-create-story` | DEV | Create a story file | -| `bmad-dev-story` | `bmad-dev-story` | DEV | Implement a story | +| `bmad-quick-dev` | `bmad-quick-dev` | DEV | Implement a feature, fix, or story | | `bmad-code-review` | `bmad-code-review` | DEV | Review implemented code | ## Common Questions diff --git a/src/bmm-skills/2-plan-workflows/bmad-ux/SKILL.md b/src/bmm-skills/2-plan-workflows/bmad-ux/SKILL.md index b441b2196..32b0d5428 100644 --- a/src/bmm-skills/2-plan-workflows/bmad-ux/SKILL.md +++ b/src/bmm-skills/2-plan-workflows/bmad-ux/SKILL.md @@ -87,4 +87,4 @@ Outcomes, in order: - **Key-screen mocks rendered.** Key-screens tool → `.working/` for surfaces where layout drives behavior or anchors visual language. - **Mock coverage confirmed.** Walk every IA surface; classify *mocked* vs *spine-only*. Ask: *"These will be built from spine tables alone — any need a visual reference?"* Render more if named; log spine-only choices. - **Layout extracted, artifacts promoted.** Distill subagent re-reads each `.working/` and `imports/` artifact; lifts visual decisions into DESIGN.md and behavioral decisions into EXPERIENCE.md. Promote `.working/` keepers to `mockups/` (HTML) or `wireframes/` (Excalidraw); imports stay. Inline relative links at relevant spine sections; state spines-win-on-conflict once. -- **Polished, handed off, closed.** Apply `{workflow.doc_standards}` in order. Execute `{workflow.external_handoffs}`; surface URLs. Set both files' `status: final`, `updated: {date}`. Log finalization via `uv run {project-root}/_bmad/scripts/memlog.py append --workspace {doc_workspace} --type event --text "spines finalized"`. Share paths. Common next: `bmad-architecture`, `bmad-create-epics-and-stories`, `bmad-dev-story`. Run `{workflow.on_complete}`. +- **Polished, handed off, closed.** Apply `{workflow.doc_standards}` in order. Execute `{workflow.external_handoffs}`; surface URLs. Set both files' `status: final`, `updated: {date}`. Log finalization via `uv run {project-root}/_bmad/scripts/memlog.py append --workspace {doc_workspace} --type event --text "spines finalized"`. Share paths. Common next: `bmad-architecture`, `bmad-create-epics-and-stories`, `bmad-quick-dev`. Run `{workflow.on_complete}`. diff --git a/src/bmm-skills/3-solutioning/bmad-architecture/SKILL.md b/src/bmm-skills/3-solutioning/bmad-architecture/SKILL.md index e18eaf703..ddd9fe8a8 100644 --- a/src/bmm-skills/3-solutioning/bmad-architecture/SKILL.md +++ b/src/bmm-skills/3-solutioning/bmad-architecture/SKILL.md @@ -73,7 +73,7 @@ Walk the sequence; reviewer fixes land before polish. 4. **Triage.** Open questions and `[ASSUMPTION]` tags: blockers (unsafe for what's next) resolved one at a time; the rest deferred with a revisit condition in the memlog. 5. **Renderings & polish.** The spine is the build deliverable; with it and the memlog now in place, produce any *additional* human-facing artifact the user needs, scoped to the purpose and audience drawn out up front. The up-front question already flagged whether one's needed; if it wasn't, still offer one here, seeding concrete options: an interactive HTML+SVG deck to walk a team through the architecture and drive discussion, a fuller HTML/md solution design, a C4 set, or a view of how the work splits across teams/epics. Build only what they pick, right-sized to that purpose; apply `{workflow.doc_standards}` polish to that prose only, never to the spine. 6. **External handoffs.** Run `{workflow.external_handoffs}`; surface returned URLs/IDs. Offer to invoke the `bmad-spec` skill to adopt the spine as a companion, keeping `AD` IDs stable so downstream can cite them. -7. **Close.** Set the spine's own frontmatter `status: final`, `updated: {date}`; log a `memlog.py append --type event --text "spine finalized"` (the memlog has no status field). Share paths. Next, **lead with `bmad-spec`** — recommend adopting/refreshing the spine as a spec companion (always the top recommendation when a spec was an input, and a useful next step even when it wasn't), then `bmad-create-epics-and-stories` or — epic altitude — `bmad-create-story`; or invoke `bmad-help` to route. +7. **Close.** Set the spine's own frontmatter `status: final`, `updated: {date}`; log a `memlog.py append --type event --text "spine finalized"` (the memlog has no status field). Share paths. Next, **lead with `bmad-spec`** — recommend adopting/refreshing the spine as a spec companion (always the top recommendation when a spec was an input, and a useful next step even when it wasn't), then `bmad-create-epics-and-stories` or — epic altitude — `bmad-quick-dev`; or invoke `bmad-help` to route. 8. Run `{workflow.on_complete}`. ## Update diff --git a/src/bmm-skills/4-implementation/bmad-agent-dev/customize.toml b/src/bmm-skills/4-implementation/bmad-agent-dev/customize.toml index e9bb952f8..065781c91 100644 --- a/src/bmm-skills/4-implementation/bmad-agent-dev/customize.toml +++ b/src/bmm-skills/4-implementation/bmad-agent-dev/customize.toml @@ -57,14 +57,9 @@ principles = [ # in place, new codes append. Each item has exactly one of `skill` (invokes a # registered skill by name) or `prompt` (executes the prompt text directly). -[[agent.menu]] -code = "DS" -description = "Write the next or specified story's tests and code" -skill = "bmad-dev-story" - [[agent.menu]] code = "QD" -description = "Unified quick flow — clarify intent, plan, implement, review, present" +description = "Implement a feature, fix, or story" skill = "bmad-quick-dev" [[agent.menu]] @@ -82,11 +77,6 @@ code = "SP" description = "Generate or update the sprint plan that sequences tasks for implementation" skill = "bmad-sprint-planning" -[[agent.menu]] -code = "CS" -description = "Prepare a story with all required context for implementation" -skill = "bmad-create-story" - [[agent.menu]] code = "ER" description = "Party mode review of all work completed across an epic" diff --git a/src/bmm-skills/4-implementation/bmad-quick-dev/step-03-implement.md b/src/bmm-skills/4-implementation/bmad-quick-dev/step-03-implement.md index 979e8cf92..d377fc794 100644 --- a/src/bmm-skills/4-implementation/bmad-quick-dev/step-03-implement.md +++ b/src/bmm-skills/4-implementation/bmad-quick-dev/step-03-implement.md @@ -18,7 +18,7 @@ Verify `{spec_file}` resolves to a non-empty path and the file exists on disk. I ### Baseline -Capture `baseline_commit` (current HEAD, or `NO_VCS` if version control is unavailable) into `{spec_file}` frontmatter before making any changes. +Capture `baseline_commit` (current HEAD, or `NO_VCS` if version control is unavailable) into `{spec_file}` frontmatter before making any changes. If the frontmatter already contains `baseline_commit` (resumed run), preserve the existing value — never overwrite it. ### Implement diff --git a/src/bmm-skills/4-implementation/bmad-retrospective/SKILL.md b/src/bmm-skills/4-implementation/bmad-retrospective/SKILL.md index 46998b6b2..364ea5e18 100644 --- a/src/bmm-skills/4-implementation/bmad-retrospective/SKILL.md +++ b/src/bmm-skills/4-implementation/bmad-retrospective/SKILL.md @@ -149,7 +149,7 @@ Amelia (Developer): "I'm having trouble detecting the completed epic from {sprin PRIORITY 3: Fallback to stories folder Scan {implementation_artifacts} for highest numbered story files -Extract epic numbers from story filenames (pattern: epic-X-Y-story-name.md) +Extract epic numbers from story filenames (patterns: epic-X-Y-story-name.md and spec-X-Y-story-name.md) Set {{detected_epic}} = highest epic number found @@ -238,13 +238,13 @@ Amelia (Developer): "Before we start the team discussion, let me review all the Charlie (Senior Dev): "Good idea - those dev notes always have gold in them." -For each story in epic {{epic_number}}, read the complete story file from {implementation_artifacts}/{{epic_number}}-{{story_num}}-*.md +For each story in epic {{epic_number}}, read the complete story record from {implementation_artifacts}/{{epic_number}}-{{story_num}}-*.md (legacy story files) and {implementation_artifacts}/spec-{{epic_number}}-{{story_num}}-*.md (quick-dev specs) Extract and analyze from each story: **Dev Notes and Struggles:** -- Look for sections like "## Dev Notes", "## Implementation Notes", "## Challenges", "## Development Log" +- Look for sections like "## Dev Notes", "## Implementation Notes", "## Challenges", "## Development Log" — in quick-dev specs: "## Tasks & Acceptance", "## Code Map", "## Design Notes", "## Spec Change Log" - Identify where developers struggled or made mistakes - Note unexpected complexity or gotchas discovered - Record technical decisions that didn't work out as planned @@ -1480,7 +1480,7 @@ Retrospective document was saved successfully, but {sprint_status_file} may need {{else}} 4. **Begin Epic {{next_epic_num}} when ready** - - Start creating stories with Developer agent's `create-story` + - Start the next epic's stories with Developer agent's `quick-dev` - Epic will be marked as `in-progress` automatically when first story is created - Ensure all critical path items are done first {{/if}} diff --git a/src/bmm-skills/4-implementation/bmad-sprint-planning/SKILL.md b/src/bmm-skills/4-implementation/bmad-sprint-planning/SKILL.md index c56f9091b..c14010e3d 100644 --- a/src/bmm-skills/4-implementation/bmad-sprint-planning/SKILL.md +++ b/src/bmm-skills/4-implementation/bmad-sprint-planning/SKILL.md @@ -181,7 +181,7 @@ development_status: # - done: All stories in epic completed # # Epic Status Transitions: -# - backlog → in-progress: Automatically when first story is created (via create-story) +# - backlog → in-progress: Automatically when first story starts (via quick-dev's sprint sync) # - in-progress → done: Manually when all stories reach 'done' status # # Story Status: @@ -202,7 +202,7 @@ development_status: # # WORKFLOW NOTES: # =============== -# - Epic transitions to 'in-progress' automatically when first story is created +# - Epic transitions to 'in-progress' automatically when first story starts (via quick-dev's sprint sync) # - Stories can be worked in parallel if team capacity allows # - Developer typically creates next story after previous one is 'done' to incorporate learnings # - Dev moves story to 'review', then runs code-review (fresh context, different LLM recommended) diff --git a/src/bmm-skills/4-implementation/bmad-sprint-status/SKILL.md b/src/bmm-skills/4-implementation/bmad-sprint-status/SKILL.md index 0e060a684..efc3f42ab 100644 --- a/src/bmm-skills/4-implementation/bmad-sprint-status/SKILL.md +++ b/src/bmm-skills/4-implementation/bmad-sprint-status/SKILL.md @@ -152,7 +152,7 @@ Enter corrections (e.g., "1=in-progress, 2=backlog") or "skip" to continue witho - IF any story has status "review": suggest `/bmad:bmm:workflows:code-review` - IF any story has status "in-progress" AND no stories have status "ready-for-dev": recommend staying focused on active story -- IF all epics have status "backlog" AND no stories have status "ready-for-dev": prompt `/bmad:bmm:workflows:create-story` +- IF all epics have status "backlog" AND no stories have status "ready-for-dev": recommend `bmad-quick-dev` to start the first backlog story - IF `last_updated` timestamp is more than 7 days old (or `last_updated` is missing, fall back to `generated`): warn "sprint-status.yaml may be stale" - IF any story key doesn't match an epic pattern (e.g., story "5-1-..." but no "epic-5"): warn "orphaned story detected" - IF any epic has status in-progress but has no associated stories: warn "in-progress epic has no stories" @@ -161,10 +161,10 @@ Enter corrections (e.g., "1=in-progress, 2=backlog") or "skip" to continue witho Pick the next recommended workflow using priority: When selecting "first" story: sort by epic number, then story number (e.g., 1-1 before 1-2 before 2-1) - 1. If any story status == in-progress → recommend `dev-story` for the first in-progress story + 1. If any story status == in-progress → recommend `quick-dev` to resume the first in-progress story 2. Else if any story status == review → recommend `code-review` for the first review story - 3. Else if any story status == ready-for-dev → recommend `dev-story` - 4. Else if any story status == backlog → recommend `create-story` + 3. Else if any story status == ready-for-dev → recommend `quick-dev` to start work on the first ready-for-dev story + 4. Else if any story status == backlog → recommend `quick-dev` to start the first backlog story 5. Else if any retrospective status == optional → recommend `retrospective` 6. Else → All implementation items done; congratulate the user - you both did amazing work together! Store selected recommendation as: next_story_id, next_workflow_id, next_agent (DEV) diff --git a/src/bmm-skills/module-help.csv b/src/bmm-skills/module-help.csv index aeead01e9..44a9d5c6a 100644 --- a/src/bmm-skills/module-help.csv +++ b/src/bmm-skills/module-help.csv @@ -2,7 +2,7 @@ module,skill,display-name,menu-code,description,action,args,phase,preceded-by,fo BMad Method,_meta,,,,,,,,,false,https://docs.bmad-method.org/llms.txt, BMad Method,bmad-document-project,Document Project,DP,Analyze an existing project to produce useful documentation.,,,anytime,,,false,project-knowledge,* BMad Method,bmad-generate-project-context,Generate Project Context,GPC,Scan existing codebase to generate a lean LLM-optimized project-context.md. Essential for brownfield projects.,,,anytime,,,false,output_folder,project context -BMad Method,bmad-quick-dev,Quick Dev,QQ,Unified intent-in code-out workflow: clarify plan implement review and present.,,,anytime,,,false,implementation_artifacts,spec and project implementation +BMad Method,bmad-quick-dev,Quick Dev,QQ,Official Phase 4 implementation loop: clarify intent plan implement review and present.,,,4-implementation,bmad-sprint-planning,bmad-code-review,true,implementation_artifacts,spec and project implementation BMad Method,bmad-spec,Spec,SPC,"Use to distill any intent input (brief, PRD, transcript, brain dump, design folder, mixed multi-source) into a succinct, no-fluff SPEC.md contract + companions that downstream work derives from. Locks the WHAT before the HOW. Works for software, game design, research, editorial, policy, business, anything intent-bearing. Validation mode also available.",,[path],anytime,,,false,{output_folder}/specs/spec-{slug},SPEC.md + companion files BMad Method,bmad-correct-course,Correct Course,CC,Navigate significant changes. May recommend start over update PRD redo architecture sprint planning or correct epics and stories.,,,anytime,,,false,planning_artifacts,change proposal BMad Method,bmad-agent-tech-writer,Write Document,WD,"Describe in detail what you want, and the agent will follow documentation best practices. Multi-turn conversation with subprocess for research/review.",write,,anytime,,,false,project-knowledge,document @@ -20,10 +20,7 @@ BMad Method,bmad-create-epics-and-stories,Create Epics and Stories,CE,,,,3-solut BMad Method,bmad-check-implementation-readiness,Check Implementation Readiness,IR,Ensure PRD UX Architecture and Epics Stories are aligned.,,,3-solutioning,bmad-create-epics-and-stories,,true,planning_artifacts,readiness report BMad Method,bmad-sprint-planning,Sprint Planning,SP,Kicks off implementation by producing a plan the implementation agents will follow in sequence for every story.,,,4-implementation,,,true,implementation_artifacts,sprint status BMad Method,bmad-sprint-status,Sprint Status,SS,Anytime: Summarize sprint status and route to next workflow.,,,4-implementation,bmad-sprint-planning,,false,, -BMad Method,bmad-create-story,Create Story,CS,Story cycle start: Prepare first found story in the sprint plan that is next or a specific epic/story designation.,create,,4-implementation,bmad-sprint-planning,bmad-create-story:validate,true,implementation_artifacts,story -BMad Method,bmad-create-story,Validate Story,VS,Validates story readiness and completeness before development work begins.,validate,,4-implementation,bmad-create-story:create,bmad-dev-story,false,implementation_artifacts,story validation report -BMad Method,bmad-dev-story,Dev Story,DS,Story cycle: Execute story implementation tasks and tests then CR then back to DS if fixes needed.,,,4-implementation,bmad-create-story:validate,,true,, -BMad Method,bmad-code-review,Code Review,CR,Story cycle: If issues back to DS if approved then next CS or ER if epic complete.,,,4-implementation,bmad-dev-story,,false,, +BMad Method,bmad-code-review,Code Review,CR,Ad hoc review of any code change. Optional extra layer after Quick Dev's built-in review.,,,4-implementation,bmad-quick-dev,,false,, BMad Method,bmad-checkpoint-preview,Checkpoint,CK,Guided walkthrough of a change from purpose and context into details. Use for human review of commits branches or PRs.,,,4-implementation,,,false,, -BMad Method,bmad-qa-generate-e2e-tests,QA Automation Test,QA,Generate automated API and E2E tests for implemented code. NOT for code review or story validation — use CR for that.,,,4-implementation,bmad-dev-story,,false,implementation_artifacts,test suite +BMad Method,bmad-qa-generate-e2e-tests,QA Automation Test,QA,Generate automated API and E2E tests for implemented code. NOT for code review or story validation — use CR for that.,,,4-implementation,bmad-quick-dev,,false,implementation_artifacts,test suite BMad Method,bmad-retrospective,Retrospective,ER,Optional at epic end: Review completed work lessons learned and next epic or if major issues consider CC.,,,4-implementation,bmad-code-review,,false,implementation_artifacts,retrospective