bmad-method 6.11.1-next.0 → 6.11.1-next.2

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "6.11.1-next.0",
+  "version": "6.11.1-next.2",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",

package/src/bmm-skills/agents/bmad-agent-analyst/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-agent-analyst
-description: Strategic business analyst and requirements expert. Use when the user asks to talk to Mary or requests the business analyst.
+description: Business analyst for market research, competitive analysis, and requirements. Use when the user asks to talk to Mary or requests the business analyst
 ---
 
 # Mary — Business Analyst

package/src/bmm-skills/agents/bmad-agent-architect/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-agent-architect
-description: System architect and technical design leader. Use when the user asks to talk to Winston or requests the architect.
+description: System architect and technical design leader. Use when the user asks to talk to Winston or requests the architect
 ---
 
 # Winston — System Architect

package/src/bmm-skills/agents/bmad-agent-dev/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-agent-dev
-description: Senior software engineer for story execution and code implementation. Use when the user asks to talk to Amelia or requests the developer agent.
+description: Senior software engineer who implements stories and code changes. Use when the user asks to talk to Amelia or requests the developer agent
 ---
 
 # Amelia — Senior Software Engineer

package/src/bmm-skills/agents/bmad-agent-pm/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-agent-pm
-description: Product manager for PRD creation and requirements discovery. Use when the user asks to talk to John or requests the product manager.
+description: Product manager for PRD creation and requirements discovery. Use when the user asks to talk to John or requests the product manager
 ---
 
 # John — Product Manager

package/src/bmm-skills/agents/bmad-agent-ux-designer/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-agent-ux-designer
-description: UX designer and UI specialist. Use when the user asks to talk to Sally or requests the UX designer.
+description: UX designer and UI specialist. Use when the user asks to talk to Sally or requests the UX designer
 ---
 
 # Sally — UX Designer

package/src/bmm-skills/module-help.csv

@@ -1,19 +1,19 @@
 module,skill,display-name,menu-code,description,action,args,phase,preceded-by,followed-by,required,output-location,outputs
 BMad Method,_meta,,,,,,,,,false,https://docs.bmad-method.org/llms.txt,
 BMad Method,bmad-project-context,Project Context,PC,"Set up or refresh a repo's agent instructions so AI agents work well in it: verified commands, policy, conventions that differ from defaults, and known pitfalls. Setup, refresh, record, and audit — replaces document-project and generate-project-context.",,,anytime,,,false,repo root,AGENTS.md managed block
-BMad Method,bmad-build,Build,BD,Official Phase 4 implementation loop: clarify intent plan implement review and present.,,,ship,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-brainstorming,Brainstorm Project,BP,Expert guided facilitation through a single or multiple techniques.,,,plan,,,false,{output_folder}/brainstorming,brainstorming session
-BMad Method,bmad-product-brief,Create Brief,CB,An expert guided experience to nail down your product idea in a brief. a gentler approach than PRFAQ when you are already sure of your concept and nothing will sway you.,,-A,plan,,,false,planning_artifacts,product brief
-BMad Method,bmad-prfaq,PRFAQ Challenge,WB,Working Backwards guided experience to forge and stress-test your product concept to ensure you have a great product that users will love and need through the PRFAQ gauntlet to determine feasibility and alignment with user needs. alternative to product brief.,,-H,plan,,,false,planning_artifacts,prfaq document
-BMad Method,bmad-prd,Create Edit and Review PRD,PRD,"Facilitated PRD workflow — create a new PRD via coached discovery, update an existing one against a change signal, or validate a finished PRD against a checklist with an HTML findings report.",,,2-planning,bmad-product-brief,,true,planning_artifacts,prd
-BMad Method,bmad-ux,Create UX,CU,"Guidance through realizing the plan for your UX, strongly recommended if a UI is a primary piece of the proposed project.",,,2-planning,bmad-prd,,false,planning_artifacts,ux design
-BMad Method,bmad-architecture,Architecture,CA,Offer once requirements exist (a PRD or spec; plus UX if present) and the user is ready to move from what to how. Also offer any time independently-built parts risk diverging. Produces the architecture spine: the invariants that keep features epics and stories consistent. Comes before epics and stories and scales from a quick spine to a full architecture (brownfield: ratifies the existing codebase).,,,plan,,,true,planning_artifacts,architecture
-BMad Method,bmad-create-epics-and-stories,Create Epics and Stories,CE,,,,plan,bmad-architecture,,true,planning_artifacts,epics and stories
-BMad Method,bmad-sprint-planning,Sprint Planning,SP,Readiness gate then tracking: verifies the planning is implementable (PASS/CONCERNS/FAIL) and produces the sprint status the implementation agents follow for every story.,,,plan,,,true,implementation_artifacts,sprint status
-BMad Method,bmad-sprint-planning,Sprint Status,SS,Anytime: summarize sprint status with risks open action items and the next recommended action; can also validate or repair the tracking file.,status,,anytime,,,false,,status summary
-BMad Method,bmad-code-review,Code Review,CR,Ad hoc review of any code change. Optional extra layer after Build's built-in review.,,,ship,bmad-build,,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.,,,ship,,,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.,,,ship,bmad-build,,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.,,,ship,bmad-code-review,,false,implementation_artifacts,retrospective
+BMad Method,bmad-build,Build,BD,"The standard implementation flow: clarify intent, plan, implement, review, and present.",,,ship,bmad-sprint-planning,bmad-code-review,true,implementation_artifacts,spec and project implementation
+BMad Method,bmad-spec,Spec,SPC,"Condense any input (brief, PRD, transcript, brain dump, design folder, or several sources at once) into a short SPEC.md plus supporting files that later work builds from. Pins down what to build before deciding how. Works for software, game design, research, editorial, policy, business — anything with an intent behind it. Can also validate an existing spec.",,[path],anytime,,,false,{output_folder}/specs/spec-{slug},SPEC.md + companion files
+BMad Method,bmad-correct-course,Correct Course,CC,"Assess a significant mid-sprint change. May recommend starting over, updating the PRD, redoing architecture or sprint planning, or correcting epics and stories.",,,anytime,,,false,planning_artifacts,change proposal
+BMad Method,bmad-brainstorming,Brainstorm Project,BP,Guided idea-generation session using one or more brainstorming techniques.,,,plan,,,false,{output_folder}/brainstorming,brainstorming session
+BMad Method,bmad-product-brief,Create Brief,CB,A guided conversation that captures your product idea in a brief. A gentler alternative to the PRFAQ when you are already committed to your concept.,,-A,plan,,,false,planning_artifacts,product brief
+BMad Method,bmad-prfaq,PRFAQ Challenge,WB,"Amazon's Working Backwards method: write the press release for the finished product first, then answer hard customer and stakeholder questions to test whether the concept holds up. An alternative to the product brief.",,-H,plan,,,false,planning_artifacts,prfaq document
+BMad Method,bmad-prd,Create Edit and Review PRD,PRD,"Create a new PRD through guided discovery, update an existing one when plans change, or validate a finished PRD against a checklist with an HTML findings report.",,,2-planning,bmad-product-brief,,true,planning_artifacts,prd
+BMad Method,bmad-ux,Create UX,CU,"Capture UX decisions into design and experience documents. Strongly recommended when a UI is a major part of the project.",,,2-planning,bmad-prd,,false,planning_artifacts,ux design
+BMad Method,bmad-architecture,Architecture,CA,"Offer once requirements exist (a PRD or spec, plus UX if present) and the user is ready to decide how to build. Also offer any time separately built parts risk becoming inconsistent. Records the architecture decisions that keep features, epics, and stories consistent. Comes before epics and stories; scales from a few key decisions to a full architecture, and can document the conventions of an existing codebase.",,,plan,,,true,planning_artifacts,architecture
+BMad Method,bmad-create-epics-and-stories,Create Epics and Stories,CE,Break the PRD and architecture into epics and user stories with acceptance criteria.,,,plan,bmad-architecture,,true,planning_artifacts,epics and stories
+BMad Method,bmad-sprint-planning,Sprint Planning,SP,"Checks the planning is complete enough to implement (PASS/CONCERNS/FAIL), then generates the sprint status file that implementation agents follow for every story.",,,plan,,,true,implementation_artifacts,sprint status
+BMad Method,bmad-sprint-planning,Sprint Status,SS,"Summarize sprint progress at any time: risks, open action items, and the recommended next action. Can also validate or repair the tracking file.",status,,anytime,,,false,,status summary
+BMad Method,bmad-code-review,Code Review,CR,Ad hoc review of any code change. An optional extra check after Build's built-in review.,,,ship,bmad-build,,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.",,,ship,,,false,,
+BMad Method,bmad-qa-generate-e2e-tests,QA Automation Test,QA,Generate automated API and end-to-end tests for implemented code. Not for code review or story validation — use Code Review for that.,,,ship,bmad-build,,false,implementation_artifacts,test suite
+BMad Method,bmad-retrospective,Retrospective,ER,"Optional at the end of an epic: review the completed work and lessons learned, and look ahead to the next epic. If major issues surfaced, consider Correct Course.",,,ship,bmad-code-review,,false,implementation_artifacts,retrospective

package/src/bmm-skills/module.yaml

@@ -1,6 +1,6 @@
 code: bmm
 name: "BMad Method"
-description: "Agile Ai Driven Development"
+description: "Agile AI-driven development"
 default_selected: true # This module will be selected by default for new installations
 
 # Variables from Core Config inserted:

package/src/bmm-skills/plan/bmad-architecture/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-architecture
-description: 'Produce the architecture: a lean spine of invariants that keeps everything built from it consistent, projected into whatever format the work needs. Use when the user says "create the architecture", "create technical architecture", "architecture spine", or "create a solution design".'
+description: 'Work out and record the architecture decisions that keep separately built parts of a system consistent, in a short architecture document. Creates, updates, or validates one; works from a spec, a raw idea, or an existing codebase. Use when the user says "create the architecture", "create technical architecture", "architecture spine", or "create a solution design"'
 ---
 # BMad Architecture
 

package/src/bmm-skills/plan/bmad-prd/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-prd
-description: Create, update, or validate a PRD. Use when the user wants help producing, editing, or validating a PRD.
+description: Create, update, or validate a PRD. Use when the user wants help producing, editing, or validating a PRD
 ---
 # BMad PRD
 

package/src/bmm-skills/plan/bmad-prfaq/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-prfaq
-description: Working Backwards PRFAQ challenge that stress-tests a product concept customer-first. Use when the user requests to 'create a PRFAQ', 'work backwards', or 'run the PRFAQ challenge'.
+description: "Test a product concept with Amazon's Working Backwards method: write the press release for the finished product first, then answer hard customer and stakeholder questions, ending in a complete PRFAQ document. Use when the user requests to 'create a PRFAQ', 'work backwards', or 'run the PRFAQ challenge'"
 ---
 
 # Working Backwards: The PRFAQ Challenge

package/src/bmm-skills/plan/bmad-prfaq/bmad-manifest.json

@@ -4,7 +4,7 @@
     {
       "name": "working-backwards",
       "menu-code": "WB",
-      "description": "Produces battle-tested PRFAQ document and optional LLM distillate for PRD input.",
+      "description": "Produces a PRFAQ document and an optional condensed version for use as PRD input.",
       "supports-headless": true,
       "phase-name": "plan",
       "preceded-by": ["brainstorming", "perform-research"],

package/src/bmm-skills/plan/bmad-product-brief/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-product-brief
-description: Create, update, or validate a product brief. Use when the user wants help producing, editing, or validating a brief.
+description: Create, update, or validate a product brief. Use when the user wants help producing, editing, or validating a brief
 ---
 
 # Overview

package/src/bmm-skills/plan/bmad-project-context/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-project-context
-description: 'Set up, refresh, or audit a repository''s agent instructions (the AGENTS.md block) so AI agents work well in that repo. Also records observed agent mistakes as pitfall lines. Must be invoked by name.'
+description: 'Set up, refresh, or audit a repository''s agent instructions (the AGENTS.md block) so AI agents work well in that repo. Also records observed agent mistakes as pitfalls. Must be invoked by name'
 ---
 
 # Overview
@@ -72,7 +72,7 @@ Never commit.
 ### 6. Close
 
 - What went in, and what was left out and why.
-- Why, in the user's terms, from `best-practices.md` — why it is small, why what the repo already states stays out, why a pitfall line stays until its cause is gone.
+- Why, in the user's terms, from `best-practices.md` — why it is small, why what the repo already states stays out, why a pitfall stays until its cause is gone.
 - How it loads, and that other harness files can point at it.
 - Maintenance: re-run after significant change, `record` the moment an agent gets something wrong, prefer a check over a new line.
 - Rules repeating across their projects, or personal rather than the team's, belong in their global agent config.
@@ -91,7 +91,7 @@ If the target has a `project-context.md` from the retired skills, commonly under
 
 ## Record
 
-Capture one observed agent mistake as it happens — the only admissible source for a pitfall line.
+Capture one observed agent mistake as it happens — the only admissible source for a pitfall.
 
 Take the task, the mistake, the correction, and its evidence. Check the block for a line already covering it. One occurrence is noted; a recurring or costly mistake earns a line now — an exact invocation under **Running and verifying** when it is a command error, otherwise a pitfall. Write it and show the diff. If it is mechanically preventable, propose the hook, lint rule, or CI check instead.
 
@@ -99,7 +99,7 @@ Take the task, the mistake, the correction, and its evidence. Check the block fo
 
 Re-check every caveat, path-check every file, follow every pointer, and ask of every line whether removing it would change agent behavior. Check for contradictions with other instruction files.
 
-Failing lines move behind an observable trigger, get fixed, or are deleted — confirm deletions first. **A policy or pitfall line goes only when the thing it guards is gone or the user retires it; nothing failing lately is not grounds.** Audit ends smaller or equal.
+Failing lines move behind an observable trigger, get fixed, or are deleted — confirm deletions first. **A policy or pitfall goes only when the thing it guards is gone or the user retires it; nothing failing lately is not grounds.** Audit ends smaller or equal.
 
 ## Children
 

package/src/bmm-skills/plan/bmad-project-context/references/best-practices.md

@@ -32,7 +32,7 @@ Prefer prohibitions to advice, and name the permitted alternative in the same li
 
 ## Retire
 
-A policy or pitfall line goes only when the thing it guards is gone, or the user retires it. Nothing failing lately is not evidence — a working rule erases its own evidence.
+A policy or pitfall goes only when the thing it guards is gone, or the user retires it. Nothing failing lately is not evidence — a working rule erases its own evidence.
 
 Every other line faces one question at each write: would removing it change agent behavior? If no, cut it.
 

package/src/bmm-skills/plan/bmad-spec/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-spec
-description: Distill any intent input into the SPEC kernel + companions — the canonical, preservation-validated machine contract for downstream work. Use when the user says "create a spec", "distill this into a spec", "validate this spec", "update the spec", or "break this into stories".
+description: 'Condense any input — an idea, brief, PRD, transcript, or mixed notes — into a short spec: SPEC.md plus supporting files that downstream skills build from. Also updates and validates existing specs, and can break a spec into stories. Use when the user says "create a spec", "distill this into a spec", "validate this spec", "update the spec", or "break this into stories"'
 ---
 
 # BMad Spec

package/src/bmm-skills/plan/bmad-sprint-planning/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-sprint-planning
-description: 'Gate planning readiness, generate sprint status tracking from epics, summarize sprint progress, and validate or repair the tracking file. Use when the user says "run sprint planning", "generate sprint plan", "check implementation readiness", "show sprint status", "validate sprint status", or "fix sprint status"'
+description: 'Check that planning is complete enough to implement, then generate the sprint status file from the epics. Can also summarize sprint progress and validate or repair the tracking file. Use when the user says "run sprint planning", "generate sprint plan", "check implementation readiness", "show sprint status", "validate sprint status", or "fix sprint status"'
 ---
 
 # Overview

package/src/bmm-skills/plan/bmad-ux/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-ux
-description: Plan UX patterns and design specifications. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"
+description: 'Capture the user''s UX vision in two documents: DESIGN.md for how the product looks and EXPERIENCE.md for how it behaves. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"'
 ---
 # BMad UX
 

package/src/bmm-skills/ship/bmad-build/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-build
-description: 'Implements any user intent, requirement, story, bug fix or change request by producing clean working code artifacts that follow the project''s existing architecture, patterns and conventions. Use when the user wants to build, fix, tweak, refactor, add or modify any code, component or feature.'
+description: 'Implement any requirement, story, bug fix, or change request as working code that follows the project''s existing architecture, patterns, and conventions. Use when the user wants to build, fix, tweak, refactor, add, or modify any code, component, or feature'
 ---
 
 Run the following command exactly once without changing the current working directory. Replace `{project-root}` with the absolute path to the project root and `{skill-root}` with the absolute path to this skill's directory:

package/src/bmm-skills/ship/bmad-build-auto/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-build-auto
-description: 'One iteration of an unattended development loop. Use when invoked by name.'
+description: 'One iteration of an unattended development loop. Use when invoked by name'
 ---
 
 Run the following command exactly once without changing the current working directory. Replace `{project-root}` with the absolute path to the project root and `{skill-root}` with the absolute path to this skill's directory:

package/src/bmm-skills/ship/bmad-checkpoint-preview/SKILL.md

@@ -1,6 +1,6 @@
 ---
 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".'
+description: 'Walk the user through reviewing a change: what it is for, what to look at closely, and how to test it. Use when the user says "checkpoint", "human review", or "walk me through this change"'
 ---
 
 # Checkpoint Review Workflow

package/src/bmm-skills/ship/bmad-code-review/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-code-review
-description: 'Adversarial code review using parallel review layers and structured triage. Use when the user says "run code review" or "review this code"'
+description: 'Review code changes with several independent reviewers in parallel, then triage and present the findings. Use when the user says "run code review" or "review this code"'
 ---
 
 # Code Review Workflow

package/src/bmm-skills/ship/bmad-correct-course/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-correct-course
-description: 'Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change"'
+description: 'Assess the impact of a significant change during sprint execution across the PRD, epics, architecture, and UX documents, and produce a sprint change proposal. Use when the user says "correct course" or "propose sprint change"'
 ---
 
 # Correct Course - Sprint Change Management Workflow

package/src/bmm-skills/ship/bmad-qa-generate-e2e-tests/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-qa-generate-e2e-tests
-description: 'Generate end to end automated tests for existing features. Use when the user says "create qa automated tests for [feature]"'
+description: 'Generate automated API and end-to-end tests for implemented features. Use when the user says "create qa automated tests for [feature]"'
 ---
 
 # QA Generate E2E Tests Workflow

package/src/bmm-skills/ship/bmad-retrospective/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-retrospective
-description: 'Evidence-based epic retrospective — collect what the epic produced, verify findings against sources, render an acceptance verdict. Use when the user says "run a retrospective" or "lets retro the epic [epic]". Supports -H/--headless.'
+description: 'Review a completed epic against the evidence it left behind — spec, stories, diffs, commits, sprint status — and produce a retrospective with sourced findings, action items, and an acceptance decision. Use when the user says "run a retrospective" or "lets retro the epic [epic]". Supports -H/--headless'
 ---
 
 # Retrospective

package/src/bmm-skills/v6-shims/bmad-create-architecture/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-create-architecture
-description: 'Deprecated — forwards to bmad-architecture (create intent).'
+description: 'Deprecated — forwards to bmad-architecture (create intent)'
 ---
 
 # DEPRECATED — forwards to bmad-architecture (create intent)

package/src/bmm-skills/v6-shims/bmad-create-prd/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-create-prd
-description: 'Deprecated — forwards to bmad-prd (create intent).'
+description: 'Deprecated — forwards to bmad-prd (create intent)'
 ---
 
 # DEPRECATED — forwards to bmad-prd (create intent)

package/src/bmm-skills/v6-shims/bmad-create-story/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-create-story
-description: "Deprecated: `bmad-build` is now the official implementation method. Only use this when explicitly invoked by name."
+description: "Deprecated: `bmad-build` is now the official implementation method. Only use this when explicitly invoked by name"
 ---
 
 # Create Story Workflow

package/src/bmm-skills/v6-shims/bmad-dev-auto/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-dev-auto
-description: "Deprecated: forwards to bmad-build-auto. Do not use unless invoked by name."
+description: "Deprecated: forwards to bmad-build-auto. Do not use unless invoked by name"
 ---
 
 # Deprecated Build Auto Alias

package/src/bmm-skills/v6-shims/bmad-dev-story/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-dev-story
-description: "Deprecated: `bmad-build` is now the official implementation method. Only use this when explicitly invoked by name."
+description: "Deprecated: `bmad-build` is now the official implementation method. Only use this when explicitly invoked by name"
 ---
 
 # Dev Story Workflow

package/src/bmm-skills/v6-shims/bmad-domain-research/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-domain-research
-description: 'Deprecated — forwards to bmad-deep-recon (domain type).'
+description: 'Deprecated — forwards to bmad-deep-recon (domain type)'
 ---
 
 # DEPRECATED — forwards to bmad-deep-recon (domain type)

package/src/bmm-skills/v6-shims/bmad-edit-prd/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-edit-prd
-description: 'Deprecated — forwards to bmad-prd (update intent).'
+description: 'Deprecated — forwards to bmad-prd (update intent)'
 ---
 
 # DEPRECATED — forwards to bmad-prd (update intent)

package/src/bmm-skills/v6-shims/bmad-market-research/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-market-research
-description: 'Deprecated — forwards to bmad-deep-recon (market type).'
+description: 'Deprecated — forwards to bmad-deep-recon (market type)'
 ---
 
 # DEPRECATED — forwards to bmad-deep-recon (market type)

package/src/bmm-skills/v6-shims/bmad-quick-dev/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-quick-dev
-description: "Deprecated: forwards to bmad-build. Do not use unless invoked by name."
+description: "Deprecated: forwards to bmad-build. Do not use unless invoked by name"
 ---
 
 # Deprecated Build Alias

package/src/bmm-skills/v6-shims/bmad-sprint-status/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-sprint-status
-description: 'Deprecated — forwards to bmad-sprint-planning (status view).'
+description: 'Deprecated — forwards to bmad-sprint-planning (status view)'
 ---
 
 # DEPRECATED — forwards to bmad-sprint-planning (status view)

package/src/bmm-skills/v6-shims/bmad-technical-research/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-technical-research
-description: 'Deprecated — forwards to bmad-deep-recon (technical type).'
+description: 'Deprecated — forwards to bmad-deep-recon (technical type)'
 ---
 
 # DEPRECATED — forwards to bmad-deep-recon (technical type)

package/src/bmm-skills/v6-shims/bmad-validate-prd/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-validate-prd
-description: 'Deprecated — forwards to bmad-prd (validate intent).'
+description: 'Deprecated — forwards to bmad-prd (validate intent)'
 ---
 
 # DEPRECATED — forwards to bmad-prd (validate intent)

package/src/core-skills/bmad-advanced-elicitation/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-advanced-elicitation
-description: 'Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.'
+description: 'Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team'
 ---
 
 # Advanced Elicitation

package/src/core-skills/bmad-brainstorming/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-brainstorming
-description: Facilitate a brainstorming session using diverse creative techniques. Use when the user says 'help me brainstorm' or 'help me ideate'.
+description: Facilitate a brainstorming session using diverse creative techniques. Use when the user says 'help me brainstorm' or 'help me ideate'
 ---
 
 # BMad Brainstorming

package/src/core-skills/bmad-customize/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-customize
-description: Authors and updates customization overrides for installed BMad skills. Use when the user says 'customize bmad', 'override a skill', 'change agent behavior', or 'customize a workflow'.
+description: Authors and updates customization overrides for installed BMad skills. Use when the user says 'customize bmad', 'override a skill', 'change agent behavior', or 'customize a workflow'
 ---
 
 # BMad Customize

package/src/core-skills/bmad-deep-recon/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-deep-recon
-description: 'Decision-grade research, three ways: draft a deep-research prompt for the user to run in their own tool (ChatGPT, Gemini, Grok, Perplexity, …), process a finished research report — file it, distill a succinct cited summary with metadata that downstream skills consume without reprocessing — or run the research here through web fan-out. Shipped type packs: market, domain, technical, competitive, user-voice, academic-lit — plus a select shape for choose-between decisions and custom types via overrides. Use when the user says "deep recon", "research this", "draft a research prompt", "process this research report", "market research", "domain research", "technical research", "competitor research", "literature review", or "help me choose between".'
+description: 'Research a topic to support a decision, three ways: draft a research prompt for the user to run in their own tool (ChatGPT, Gemini, Grok, Perplexity, …), turn a finished research report into a short summary with cited sources that other skills can use directly, or run the research here with parallel web searches. Built-in research types: market, domain, technical, competitive, user-voice, academic-lit; also supports choosing between candidates, and custom types via overrides. Use when the user says "deep recon", "research this", "draft a research prompt", "process this research report", "market research", "domain research", "technical research", "competitor research", "literature review", or "help me choose between"'
 ---
 
 # BMad Deep Recon

package/src/core-skills/bmad-forge-idea/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-forge-idea
-description: Pressure-test an idea through persona-driven interrogation until it hardens, proves out, or dies cheaply. Use when the user says 'forge an idea', 'pressure-test this idea', 'stress-test my thinking', or 'harden this idea'.
+description: Test a half-formed idea in a questioning conversation, with different personas probing its weak points, until the user can act on it or drop it with confidence. Optionally writes a short brief for planning skills to build on. Use when the user says 'forge an idea', 'pressure-test this idea', 'stress-test my thinking', or 'harden this idea'
 ---
 
 # BMad Forge Idea

package/src/core-skills/bmad-help/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-help
-description: 'Analyzes current state and user query to answer BMad questions or recommend the next skill(s) to use. Use when user asks for help, bmad help, what to do next, or what to start with in BMad.'
+description: 'Analyzes current state and user query to answer BMad questions or recommend the next skill(s) to use. Use when user asks for help, bmad help, what to do next, or what to start with in BMad'
 ---
 
 # BMad Help
@@ -50,9 +50,11 @@ module,skill,display-name,menu-code,description,action,args,phase,preceded-by,fo
 - A phase with no required items is entirely optional — recommend it but be clear about what's actually required next
 
 **Completion detection**:
-- Search resolved output paths for `outputs` patterns
-- Fuzzy-match found files to catalog rows
-- User may also state completion explicitly, or it may be evident from the current conversation
+- Search resolved output paths for `outputs` patterns and fuzzy-match found files to catalog rows
+- Treat a matching output as evidence that the skill started, not that it completed
+- Inspect matched artifacts for explicit completion evidence, such as final status or finalization markers; a draft or incomplete marker means the skill is still in progress
+- Honor completion stated by the user or established in the current conversation
+- When completion cannot be determined reliably, say so and ask the user; do not recommend advancing based on file presence alone
 
 **Descriptions carry routing context** — some contain cycle info and alternate paths (e.g., "back to DS if fixes needed"). Read them as navigation hints, not just display text.
 

package/src/core-skills/bmad-party-mode/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-party-mode
-description: 'Orchestrates lively group discussions between installed BMAD agents or custom personas, and helps author custom parties. Use when the user requests party mode, a roundtable, or multiple agent perspectives — or wants to create/configure a party, define personas, or build an AI focus-group panel.'
+description: 'Orchestrates lively group discussions between installed BMAD agents or custom personas, and helps author custom parties. Use when the user requests party mode, a roundtable, or multiple agent perspectives — or wants to create/configure a party, define personas, or build an AI focus-group panel'
 ---
 
 # Party Mode

package/src/core-skills/bmad-review/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-review
-description: 'Multi-lens review over any diff, doc, spec, or artifact — whichever installed lenses fit the content, run singly or together. Shipped lenses include adversarial, edge-case, verification-gap, structure, and prose. Use when the user says "review this", "critical review", "editorial review", "hunt edge cases", "review the structure", or "review the prose".'
+description: 'Review any diff, document, spec, or other artifact with one or more installed review methods (lenses) — shipped ones cover adversarial critique, edge cases, verification gaps, document structure, and prose. Runs whichever fit the content, or exactly the ones asked for. Use when the user says "review this", "critical review", "editorial review", "hunt edge cases", "review the structure", or "review the prose"'
 ---
 
 # BMad Review

package/src/core-skills/module-help.csv

@@ -5,6 +5,6 @@ Core,bmad-party-mode,Party Mode,PM,Orchestrate multi-agent discussions when you
 Core,bmad-help,BMad Help,BH,,,,anytime,,,false,,
 Core,bmad-customize,BMad Customize,BC,"Use when you want to change how an agent or workflow behaves — add persistent facts, swap templates, insert activation hooks, or customize menus. Scans what's customizable, picks the right scope (agent vs workflow), writes the override to _bmad/custom/, and verifies the merge. No TOML hand-authoring required.",,,anytime,,,false,{project-root}/_bmad/custom,TOML override files
 Core,bmad-advanced-elicitation,Advanced Elicitation,AE,"Use at any checkpoint to push a just-produced draft, section, or plan past its first version — pick from a menu of elicitation methods (pre-mortem, first principles, red team, socratic) and apply the improvements.",,,anytime,,,false,,
-Core,bmad-review,Review,RV,"Use to review anything before it ships — a diff, branch, or uncommitted changes; a PRD, spec, story, or architecture doc; any prose document. Runs whichever installed lenses fit the content and reports findings in one shape: shipped lenses cover adversarial critique, edge cases, verification gaps, document structure (cuts, merges, moves), and prose copy-edit, and installs may add more. Reach for it to tighten a bloated or LLM-slop draft, pressure-test a plan before building, or check a change is adequately tested. Run every applicable lens or name the ones you want. Code Review in other modules calls it automatically.",,[path],anytime,,,false,,findings JSON array + markdown report
-Core,bmad-forge-idea,Forge Idea,FI,"Use to pressure-test and harden an idea — software, business, creative, research, or life — until it proves out, hardens into something buildable, or dies cheaply. Persona-driven interrogation; optional handoff to bmad-spec or bmad-build.",,,anytime,,,false,{output_folder}/forge,refined-idea brief (optional)
-Core,bmad-deep-recon,Deep Recon,RS,Decision-grade research three ways: draft a deep-research prompt for your own AI tool then process the returned report into a downstream-ready cited summary — or run the research directly via web fan-out. Types: market domain technical competitive user-voice academic-lit plus a select shape for choose-between decisions; claim verification and refresh lifecycle. Custom types via overrides.,,[type],anytime,,,false,{planning_artifacts}/research,research report/summary + optional html briefing
+Core,bmad-review,Review,RV,"Review anything before it ships: a diff, branch, or uncommitted changes; a PRD, spec, story, or architecture document; any prose. Applies whichever installed review methods (lenses) fit the content — shipped ones cover adversarial critique, edge cases, verification gaps, document structure, and prose editing — or exactly the ones you name. Code Review in other modules calls it automatically.",,[path],anytime,,,false,,findings JSON array + markdown report
+Core,bmad-forge-idea,Forge Idea,FI,"Test an idea — software, business, creative, research, or personal — through probing questions from different personas until you can act on it or drop it with confidence. Can hand the result to bmad-spec or bmad-build.",,,anytime,,,false,{output_folder}/forge,refined-idea brief (optional)
+Core,bmad-deep-recon,Deep Recon,RS,"Research a topic to support a decision: draft a research prompt for your own AI tool and turn the returned report into a summary with cited sources, or run the research directly here with web searches. Types: market, domain, technical, competitive, user-voice, academic-lit, plus choosing between candidates; custom types via overrides.",,[type],anytime,,,false,{planning_artifacts}/research,research report/summary + optional html briefing

package/src/core-skills/v6-shims/bmad-editorial-review/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-editorial-review
-description: 'Deprecated — forwards to bmad-review.'
+description: 'Deprecated — forwards to bmad-review'
 ---
 
 Merged into `bmad-review`. Invoke the `bmad-review` skill on the same content with the `structure` and `prose` lenses — both, structure first, so prose runs on top of the structure findings — unless the caller asked for a structure-only or prose-only review, in which case pass only that lens. Pass through any `also_consider` areas, and forward this skill's resolved `[workflow]` fields as pre-resolved values — but only those that resolved to something, since an empty value here means no legacy override exists and bmad-review's own default should stand: `reader_type`, `style_guide`, `review_guidance`, `output_preferences`, `persistent_facts`, `activation_steps_prepend`, `activation_steps_append`, `on_complete`, and `review_output_path` as the report path. Present the findings in the legacy shape: the two-pass findings table `| Pass | Original Text | Revised Text | Changes |` with the purpose/audience read above it and, when the structure pass ran, the reduction summary below it — and no other lens's output.

package/src/core-skills/v6-shims/bmad-editorial-review-prose/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-editorial-review-prose
-description: 'Deprecated — forwards to bmad-review.'
+description: 'Deprecated — forwards to bmad-review'
 ---
 
 Merged into `bmad-review`. Invoke the `bmad-review` skill on the same content with only the `prose` lens, passing through the same inputs and any `also_consider` areas. Present the findings in the legacy shape: a three-column markdown table `| Original Text | Revised Text | Changes |` — no Pass column, no preamble above the table. If no issues are found, output exactly: `No editorial issues identified`.

package/src/core-skills/v6-shims/bmad-editorial-review-structure/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-editorial-review-structure
-description: 'Deprecated — forwards to bmad-review.'
+description: 'Deprecated — forwards to bmad-review'
 ---
 
 Merged into `bmad-review`. Invoke the `bmad-review` skill on the same content with only the `structure` lens, passing through the same inputs and any `also_consider` areas. Present the findings in the legacy report shape: a `## Document Summary` block (purpose, audience, reader type, structure model, current length), a `## Recommendations` list of numbered `[CUT/MERGE/MOVE/CONDENSE/QUESTION/PRESERVE]` entries each with rationale and word impact, and a closing `## Summary` (total recommendations, estimated reduction) — not the findings table. If no structural issues are found, output exactly: `No substantive changes recommended`.

package/src/core-skills/v6-shims/bmad-review-adversarial-general/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-review-adversarial-general
-description: 'Deprecated — forwards to bmad-review.'
+description: 'Deprecated — forwards to bmad-review'
 ---
 
 Merged into `bmad-review`. Invoke the `bmad-review` skill on the same content with only the `adversarial` lens, passing through any `also_consider` areas. Present the findings as a Markdown list — descriptions only, no severity, priority, or ranking; no JSON block.

package/src/core-skills/v6-shims/bmad-review-edge-case-hunter/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-review-edge-case-hunter
-description: 'Deprecated — forwards to bmad-review.'
+description: 'Deprecated — forwards to bmad-review'
 ---
 
 Merged into `bmad-review`. Invoke the `bmad-review` skill on the same content with only the `edge-case-hunter` lens, passing through any `also_consider` areas. Output ONLY the raw findings JSON array in the legacy shape: the four standard fields (plus `kind`/`confidence` on deletion findings), no `lens` field, no markdown wrapping, no extra text. `[]` is valid when nothing is found.

package/src/core-skills/v6-shims/bmad-review-verification-gap/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-review-verification-gap
-description: 'Deprecated — forwards to bmad-review.'
+description: 'Deprecated — forwards to bmad-review'
 ---
 
 Merged into `bmad-review`. Invoke the `bmad-review` skill on the same content with only the `verification-gap` lens. Present the markdown rendering only (no JSON block), listing any `gap_shape: "other"` findings under an `## Other findings` heading. When there are no findings at all, output exactly this single line: `No verification gaps found.`