Merge pull request #2008 from bmad-code-org/feat-validation-pass-2
fix(skills): validation pass 2 — path, variable, and sequence fixes
This commit is contained in:
Alex Verkhovsky
GitHub
commit
4404b4bc9a
|
|
@ -3,4 +3,4 @@ name: bmad-create-product-brief
|
||||||
description: 'Create product brief through collaborative discovery. Use when the user says "lets create a product brief" or "help me create a project brief"'
|
description: 'Create product brief through collaborative discovery. Use when the user says "lets create a product brief" or "help me create a project brief"'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -12,9 +12,9 @@ Now that you know what the brief is about, fan out subagents in parallel to gath
|
||||||
|
|
||||||
**Launch in parallel:**
|
**Launch in parallel:**
|
||||||
|
|
||||||
1. **Artifact Analyzer** (`agents/artifact-analyzer.md`) — Scans `{planning_artifacts}` and `{project_knowledge}` for relevant documents. Also scans any specific paths the user provided. Returns structured synthesis of what it found.
|
1. **Artifact Analyzer** (`../agents/artifact-analyzer.md`) — Scans `{planning_artifacts}` and `{project_knowledge}` for relevant documents. Also scans any specific paths the user provided. Returns structured synthesis of what it found.
|
||||||
|
|
||||||
2. **Web Researcher** (`agents/web-researcher.md`) — Searches for competitive landscape, market context, trends, and relevant industry data. Returns structured findings scoped to the product domain.
|
2. **Web Researcher** (`../agents/web-researcher.md`) — Searches for competitive landscape, market context, trends, and relevant industry data. Returns structured findings scoped to the product domain.
|
||||||
|
|
||||||
### Graceful Degradation
|
### Graceful Degradation
|
||||||
|
|
||||||
|
|
@ -38,20 +38,20 @@ Once subagent results return (or inline scanning completes):
|
||||||
- Highlight anything surprising or worth discussing
|
- Highlight anything surprising or worth discussing
|
||||||
- Share the gaps you've identified
|
- Share the gaps you've identified
|
||||||
- Ask: "Anything else you'd like to add, or shall we move on to filling in the details?"
|
- Ask: "Anything else you'd like to add, or shall we move on to filling in the details?"
|
||||||
- Route to `prompts/guided-elicitation.md`
|
- Route to `guided-elicitation.md`
|
||||||
|
|
||||||
**Yolo mode:**
|
**Yolo mode:**
|
||||||
- Absorb all findings silently
|
- Absorb all findings silently
|
||||||
- Skip directly to `prompts/draft-and-review.md` — you have enough to draft
|
- Skip directly to `draft-and-review.md` — you have enough to draft
|
||||||
- The user will refine later
|
- The user will refine later
|
||||||
|
|
||||||
**Headless mode:**
|
**Headless mode:**
|
||||||
- Absorb all findings
|
- Absorb all findings
|
||||||
- Skip directly to `prompts/draft-and-review.md`
|
- Skip directly to `draft-and-review.md`
|
||||||
- No interaction
|
- No interaction
|
||||||
|
|
||||||
## Stage Complete
|
## Stage Complete
|
||||||
|
|
||||||
This stage is complete when subagent results (or inline scanning fallback) have returned and findings are merged with user context. Route per mode:
|
This stage is complete when subagent results (or inline scanning fallback) have returned and findings are merged with user context. Route per mode:
|
||||||
- **Guided** → `prompts/guided-elicitation.md`
|
- **Guided** → `guided-elicitation.md`
|
||||||
- **Yolo / Headless** → `prompts/draft-and-review.md`
|
- **Yolo / Headless** → `draft-and-review.md`
|
||||||
|
|
|
||||||
|
|
@ -8,7 +8,7 @@
|
||||||
|
|
||||||
## Step 1: Draft the Executive Brief
|
## Step 1: Draft the Executive Brief
|
||||||
|
|
||||||
Use `resources/brief-template.md` as a guide — adapt structure to fit the product's story.
|
Use `../resources/brief-template.md` as a guide — adapt structure to fit the product's story.
|
||||||
|
|
||||||
**Writing principles:**
|
**Writing principles:**
|
||||||
- **Executive audience** — persuasive, clear, concise. 1-2 pages.
|
- **Executive audience** — persuasive, clear, concise. 1-2 pages.
|
||||||
|
|
@ -36,9 +36,9 @@ Before showing the draft to the user, run it through multiple review lenses in p
|
||||||
|
|
||||||
**Launch in parallel:**
|
**Launch in parallel:**
|
||||||
|
|
||||||
1. **Skeptic Reviewer** (`agents/skeptic-reviewer.md`) — "What's missing? What assumptions are untested? What could go wrong? Where is the brief vague or hand-wavy?"
|
1. **Skeptic Reviewer** (`../agents/skeptic-reviewer.md`) — "What's missing? What assumptions are untested? What could go wrong? Where is the brief vague or hand-wavy?"
|
||||||
|
|
||||||
2. **Opportunity Reviewer** (`agents/opportunity-reviewer.md`) — "What adjacent value propositions are being missed? What market angles or partnerships could strengthen this? What's underemphasized?"
|
2. **Opportunity Reviewer** (`../agents/opportunity-reviewer.md`) — "What adjacent value propositions are being missed? What market angles or partnerships could strengthen this? What's underemphasized?"
|
||||||
|
|
||||||
3. **Contextual Reviewer** — You (the main agent) pick the most useful third lens based on THIS specific product. Choose the lens that addresses the SINGLE BIGGEST RISK that the skeptic and opportunity reviewers won't naturally catch. Examples:
|
3. **Contextual Reviewer** — You (the main agent) pick the most useful third lens based on THIS specific product. Choose the lens that addresses the SINGLE BIGGEST RISK that the skeptic and opportunity reviewers won't naturally catch. Examples:
|
||||||
- For healthtech: "Regulatory and compliance risk reviewer"
|
- For healthtech: "Regulatory and compliance risk reviewer"
|
||||||
|
|
@ -65,7 +65,7 @@ After all reviews complete:
|
||||||
|
|
||||||
## Step 4: Present to User
|
## Step 4: Present to User
|
||||||
|
|
||||||
**Headless mode:** Skip to `prompts/finalize.md` — no user interaction. Save the improved draft directly.
|
**Headless mode:** Skip to `finalize.md` — no user interaction. Save the improved draft directly.
|
||||||
|
|
||||||
**Yolo and Guided modes:**
|
**Yolo and Guided modes:**
|
||||||
|
|
||||||
|
|
@ -83,4 +83,4 @@ Present reviewer findings with brief rationale, then offer: "Want me to dig into
|
||||||
|
|
||||||
## Stage Complete
|
## Stage Complete
|
||||||
|
|
||||||
This stage is complete when: (a) the draft has been reviewed by all three lenses and improvements integrated, AND either (autonomous) save and route directly, or (guided/yolo) the user is satisfied. Route to `prompts/finalize.md`.
|
This stage is complete when: (a) the draft has been reviewed by all three lenses and improvements integrated, AND either (autonomous) save and route directly, or (guided/yolo) the user is satisfied. Route to `finalize.md`.
|
||||||
|
|
|
||||||
|
|
@ -72,4 +72,4 @@ purpose: "Token-efficient context for downstream PRD creation"
|
||||||
|
|
||||||
## Stage Complete
|
## Stage Complete
|
||||||
|
|
||||||
This is the terminal stage. After delivering the completion message and file paths, the workflow is done. If the user requests further revisions, loop back to `prompts/draft-and-review.md`. Otherwise, exit.
|
This is the terminal stage. After delivering the completion message and file paths, the workflow is done. If the user requests further revisions, loop back to `draft-and-review.md`. Otherwise, exit.
|
||||||
|
|
|
||||||
|
|
@ -5,7 +5,7 @@
|
||||||
|
|
||||||
**Goal:** Fill the gaps in what you know. By now you have the user's brain dump, artifact analysis, and web research. This stage is about smart, targeted questioning — not rote section-by-section interrogation.
|
**Goal:** Fill the gaps in what you know. By now you have the user's brain dump, artifact analysis, and web research. This stage is about smart, targeted questioning — not rote section-by-section interrogation.
|
||||||
|
|
||||||
**Skip this stage entirely in Yolo and Autonomous modes** — go directly to `prompts/draft-and-review.md`.
|
**Skip this stage entirely in Yolo and Autonomous modes** — go directly to `draft-and-review.md`.
|
||||||
|
|
||||||
## Approach
|
## Approach
|
||||||
|
|
||||||
|
|
@ -67,4 +67,4 @@ If the user is providing complete, confident answers and you have solid coverage
|
||||||
|
|
||||||
## Stage Complete
|
## Stage Complete
|
||||||
|
|
||||||
This stage is complete when sufficient substance exists to draft a compelling brief and the user confirms readiness. Route to `prompts/draft-and-review.md`.
|
This stage is complete when sufficient substance exists to draft a compelling brief and the user confirms readiness. Route to `draft-and-review.md`.
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-domain-research
|
||||||
description: 'Conduct domain and industry research. Use when the user says "lets create a research report on [domain or industry]"'
|
description: 'Conduct domain and industry research. Use when the user says "lets create a research report on [domain or industry]"'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-market-research
|
||||||
description: 'Conduct market research on competition and customers. Use when the user says "create a market research report about [business idea]".'
|
description: 'Conduct market research on competition and customers. Use when the user says "create a market research report about [business idea]".'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-technical-research
|
||||||
description: 'Conduct technical research on technologies and architecture. Use when the user says "create a technical research report on [topic]".'
|
description: 'Conduct technical research on technologies and architecture. Use when the user says "create a technical research report on [topic]".'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-create-ux-design
|
||||||
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: '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"'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-edit-prd
|
||||||
description: 'Edit an existing PRD. Use when the user says "edit this PRD".'
|
description: 'Edit an existing PRD. Use when the user says "edit this PRD".'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -1,9 +1,5 @@
|
||||||
---
|
---
|
||||||
name: 'step-e-01-discovery'
|
|
||||||
description: 'Discovery & Understanding - Understand what user wants to edit and detect PRD format'
|
|
||||||
|
|
||||||
# File references (ONLY variables used in this step)
|
# File references (ONLY variables used in this step)
|
||||||
altStepFile: './step-e-01b-legacy-conversion.md'
|
|
||||||
prdPurpose: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/data/prd-purpose.md'
|
prdPurpose: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/data/prd-purpose.md'
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
@ -188,7 +184,7 @@ Display: "**Edit Requirements Understood**
|
||||||
|
|
||||||
**Proceeding to deep review and analysis...**"
|
**Proceeding to deep review and analysis...**"
|
||||||
|
|
||||||
Read fully and follow: next step (step-e-02-review.md)
|
Read fully and follow: `./step-e-02-review.md`
|
||||||
|
|
||||||
**IF PRD is Legacy (Non-Standard) AND no validation report:**
|
**IF PRD is Legacy (Non-Standard) AND no validation report:**
|
||||||
|
|
||||||
|
|
@ -215,7 +211,7 @@ Present MENU OPTIONS below for user selection
|
||||||
|
|
||||||
#### Menu Handling Logic:
|
#### Menu Handling Logic:
|
||||||
|
|
||||||
- IF C (Convert): Read fully and follow: {altStepFile} (step-e-01b-legacy-conversion.md)
|
- IF C (Convert): Read fully and follow: `./step-e-01b-legacy-conversion.md`
|
||||||
- IF E (Edit As-Is): Display "Proceeding with edits..." then load next step
|
- IF E (Edit As-Is): Display "Proceeding with edits..." then load next step
|
||||||
- IF X (Exit): Display summary and exit
|
- IF X (Exit): Display summary and exit
|
||||||
- IF Any other: help user, then redisplay menu
|
- IF Any other: help user, then redisplay menu
|
||||||
|
|
|
||||||
|
|
@ -1,9 +1,5 @@
|
||||||
---
|
---
|
||||||
name: 'step-e-01b-legacy-conversion'
|
|
||||||
description: 'Legacy PRD Conversion Assessment - Analyze legacy PRD and propose conversion strategy'
|
|
||||||
|
|
||||||
# File references (ONLY variables used in this step)
|
# File references (ONLY variables used in this step)
|
||||||
nextStepFile: './step-e-02-review.md'
|
|
||||||
prdFile: '{prd_file_path}'
|
prdFile: '{prd_file_path}'
|
||||||
prdPurpose: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/data/prd-purpose.md'
|
prdPurpose: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/data/prd-purpose.md'
|
||||||
---
|
---
|
||||||
|
|
@ -182,7 +178,7 @@ Edit goals: {summary}
|
||||||
|
|
||||||
**Proceeding to deep review...**"
|
**Proceeding to deep review...**"
|
||||||
|
|
||||||
Read fully and follow: {nextStepFile} (step-e-02-review.md)
|
Read fully and follow: `./step-e-02-review.md`
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,9 +1,5 @@
|
||||||
---
|
---
|
||||||
name: 'step-e-02-review'
|
|
||||||
description: 'Deep Review & Analysis - Thoroughly review existing PRD and prepare detailed change plan'
|
|
||||||
|
|
||||||
# File references (ONLY variables used in this step)
|
# File references (ONLY variables used in this step)
|
||||||
nextStepFile: './step-e-03-edit.md'
|
|
||||||
prdFile: '{prd_file_path}'
|
prdFile: '{prd_file_path}'
|
||||||
validationReport: '{validation_report_path}' # If provided
|
validationReport: '{validation_report_path}' # If provided
|
||||||
prdPurpose: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/data/prd-purpose.md'
|
prdPurpose: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/data/prd-purpose.md'
|
||||||
|
|
@ -204,7 +200,7 @@ Display: "**Change Plan Approved**
|
||||||
|
|
||||||
**Proceeding to edit step...**"
|
**Proceeding to edit step...**"
|
||||||
|
|
||||||
Read fully and follow: {nextStepFile} (step-e-03-edit.md)
|
Read fully and follow: `./step-e-03-edit.md`
|
||||||
|
|
||||||
### 7. Present MENU OPTIONS (If User Wants Discussion)
|
### 7. Present MENU OPTIONS (If User Wants Discussion)
|
||||||
|
|
||||||
|
|
@ -221,7 +217,7 @@ Read fully and follow: {nextStepFile} (step-e-03-edit.md)
|
||||||
|
|
||||||
- IF A: Invoke the `bmad-advanced-elicitation` skill, then return to discussion
|
- IF A: Invoke the `bmad-advanced-elicitation` skill, then return to discussion
|
||||||
- IF P: Invoke the `bmad-party-mode` skill, then return to discussion
|
- IF P: Invoke the `bmad-party-mode` skill, then return to discussion
|
||||||
- IF C: Document approval, then load {nextStepFile}
|
- IF C: Document approval, then load step-e-03-edit.md
|
||||||
- IF Any other: discuss, then redisplay menu
|
- IF Any other: discuss, then redisplay menu
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
|
||||||
|
|
@ -1,9 +1,5 @@
|
||||||
---
|
---
|
||||||
name: 'step-e-03-edit'
|
|
||||||
description: 'Edit & Update - Apply changes to PRD following approved change plan'
|
|
||||||
|
|
||||||
# File references (ONLY variables used in this step)
|
# File references (ONLY variables used in this step)
|
||||||
nextStepFile: './step-e-04-complete.md'
|
|
||||||
prdFile: '{prd_file_path}'
|
prdFile: '{prd_file_path}'
|
||||||
prdPurpose: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/data/prd-purpose.md'
|
prdPurpose: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/data/prd-purpose.md'
|
||||||
---
|
---
|
||||||
|
|
@ -211,7 +207,7 @@ Display:
|
||||||
|
|
||||||
### 8. Present MENU OPTIONS
|
### 8. Present MENU OPTIONS
|
||||||
|
|
||||||
**[V] Run Validation** - Execute full validation workflow (steps-v/step-v-01-discovery.md)
|
**[V] Run Validation** - Execute full validation workflow (./steps-v/step-v-01-discovery.md)
|
||||||
**[S] Summary Only** - End with summary of changes (no validation)
|
**[S] Summary Only** - End with summary of changes (no validation)
|
||||||
**[A] Adjust** - Make additional edits
|
**[A] Adjust** - Make additional edits
|
||||||
**[X] Exit** - Exit edit workflow
|
**[X] Exit** - Exit edit workflow
|
||||||
|
|
@ -223,7 +219,7 @@ Display:
|
||||||
|
|
||||||
#### Menu Handling Logic:
|
#### Menu Handling Logic:
|
||||||
|
|
||||||
- IF V (Validate): Display "Starting validation workflow..." then read fully and follow: steps-v/step-v-01-discovery.md
|
- IF V (Validate): Display "Starting validation workflow..." then read fully and follow: `./steps-v/step-v-01-discovery.md`
|
||||||
- IF S (Summary): Present edit summary and exit
|
- IF S (Summary): Present edit summary and exit
|
||||||
- IF A (Adjust): Accept additional requirements, loop back to editing
|
- IF A (Adjust): Accept additional requirements, loop back to editing
|
||||||
- IF X (Exit): Display summary and exit
|
- IF X (Exit): Display summary and exit
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
---
|
---
|
||||||
name: 'step-e-04-complete'
|
|
||||||
description: 'Complete & Validate - Present options for next steps including full validation'
|
|
||||||
|
|
||||||
# File references (ONLY variables used in this step)
|
# File references (ONLY variables used in this step)
|
||||||
prdFile: '{prd_file_path}'
|
prdFile: '{prd_file_path}'
|
||||||
validationWorkflow: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-01-discovery.md'
|
validationWorkflow: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-01-discovery.md'
|
||||||
|
|
@ -127,7 +124,7 @@ Display:
|
||||||
- Display: "**Additional Edits**"
|
- Display: "**Additional Edits**"
|
||||||
- Ask: "What additional edits would you like to make?"
|
- Ask: "What additional edits would you like to make?"
|
||||||
- Accept input, then display: "**Returning to edit step...**"
|
- Accept input, then display: "**Returning to edit step...**"
|
||||||
- Read fully and follow: step-e-03-edit.md again
|
- Read fully and follow: `./step-e-03-edit.md` again
|
||||||
|
|
||||||
- **IF S (Summary):**
|
- **IF S (Summary):**
|
||||||
- Display detailed summary including:
|
- Display detailed summary including:
|
||||||
|
|
|
||||||
|
|
@ -1,6 +1,5 @@
|
||||||
---
|
---
|
||||||
main_config: '{project-root}/_bmad/bmm/config.yaml'
|
main_config: '{project-root}/_bmad/bmm/config.yaml'
|
||||||
editWorkflow: './steps-e/step-e-01-discovery.md'
|
|
||||||
---
|
---
|
||||||
|
|
||||||
# PRD Edit Workflow
|
# PRD Edit Workflow
|
||||||
|
|
@ -61,4 +60,4 @@ Load and read full config from {main_config} and resolve:
|
||||||
|
|
||||||
Prompt for PRD path: "Which PRD would you like to edit? Please provide the path to the PRD.md file."
|
Prompt for PRD path: "Which PRD would you like to edit? Please provide the path to the PRD.md file."
|
||||||
|
|
||||||
Then read fully and follow: `{editWorkflow}` (steps-e/step-e-01-discovery.md)
|
Then read fully and follow: `./steps-e/step-e-01-discovery.md`
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-validate-prd
|
||||||
description: 'Validate a PRD against standards. Use when the user says "validate this PRD" or "run PRD validation"'
|
description: 'Validate a PRD against standards. Use when the user says "validate this PRD" or "run PRD validation"'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
---
|
---
|
||||||
name: 'step-v-01-discovery'
|
|
||||||
description: 'Document Discovery & Confirmation - Handle fresh context validation, confirm PRD path, discover input documents'
|
|
||||||
|
|
||||||
# File references (ONLY variables used in this step)
|
# File references (ONLY variables used in this step)
|
||||||
nextStepFile: './step-v-02-format-detection.md'
|
nextStepFile: './step-v-02-format-detection.md'
|
||||||
prdPurpose: '../data/prd-purpose.md'
|
prdPurpose: '../data/prd-purpose.md'
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
---
|
---
|
||||||
name: 'step-v-02-format-detection'
|
|
||||||
description: 'Format Detection & Structure Analysis - Classify PRD format and route appropriately'
|
|
||||||
|
|
||||||
# File references (ONLY variables used in this step)
|
# File references (ONLY variables used in this step)
|
||||||
nextStepFile: './step-v-03-density-validation.md'
|
nextStepFile: './step-v-03-density-validation.md'
|
||||||
altStepFile: './step-v-02b-parity-check.md'
|
altStepFile: './step-v-02b-parity-check.md'
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
---
|
---
|
||||||
name: 'step-v-02b-parity-check'
|
|
||||||
description: 'Document Parity Check - Analyze non-standard PRD and identify gaps to achieve BMAD PRD parity'
|
|
||||||
|
|
||||||
# File references (ONLY variables used in this step)
|
# File references (ONLY variables used in this step)
|
||||||
nextStepFile: './step-v-03-density-validation.md'
|
nextStepFile: './step-v-03-density-validation.md'
|
||||||
prdFile: '{prd_file_path}'
|
prdFile: '{prd_file_path}'
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
---
|
---
|
||||||
name: 'step-v-03-density-validation'
|
|
||||||
description: 'Information Density Check - Scan for anti-patterns that violate information density principles'
|
|
||||||
|
|
||||||
# File references (ONLY variables used in this step)
|
# File references (ONLY variables used in this step)
|
||||||
nextStepFile: './step-v-04-brief-coverage-validation.md'
|
nextStepFile: './step-v-04-brief-coverage-validation.md'
|
||||||
prdFile: '{prd_file_path}'
|
prdFile: '{prd_file_path}'
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
---
|
---
|
||||||
name: 'step-v-04-brief-coverage-validation'
|
|
||||||
description: 'Product Brief Coverage Check - Validate PRD covers all content from Product Brief (if used as input)'
|
|
||||||
|
|
||||||
# File references (ONLY variables used in this step)
|
# File references (ONLY variables used in this step)
|
||||||
nextStepFile: './step-v-05-measurability-validation.md'
|
nextStepFile: './step-v-05-measurability-validation.md'
|
||||||
prdFile: '{prd_file_path}'
|
prdFile: '{prd_file_path}'
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
---
|
---
|
||||||
name: 'step-v-05-measurability-validation'
|
|
||||||
description: 'Measurability Validation - Validate that all requirements (FRs and NFRs) are measurable and testable'
|
|
||||||
|
|
||||||
# File references (ONLY variables used in this step)
|
# File references (ONLY variables used in this step)
|
||||||
nextStepFile: './step-v-06-traceability-validation.md'
|
nextStepFile: './step-v-06-traceability-validation.md'
|
||||||
prdFile: '{prd_file_path}'
|
prdFile: '{prd_file_path}'
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
---
|
---
|
||||||
name: 'step-v-06-traceability-validation'
|
|
||||||
description: 'Traceability Validation - Validate the traceability chain from vision → success → journeys → FRs is intact'
|
|
||||||
|
|
||||||
# File references (ONLY variables used in this step)
|
# File references (ONLY variables used in this step)
|
||||||
nextStepFile: './step-v-07-implementation-leakage-validation.md'
|
nextStepFile: './step-v-07-implementation-leakage-validation.md'
|
||||||
prdFile: '{prd_file_path}'
|
prdFile: '{prd_file_path}'
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
---
|
---
|
||||||
name: 'step-v-07-implementation-leakage-validation'
|
|
||||||
description: 'Implementation Leakage Check - Ensure FRs and NFRs don\'t include implementation details'
|
|
||||||
|
|
||||||
# File references (ONLY variables used in this step)
|
# File references (ONLY variables used in this step)
|
||||||
nextStepFile: './step-v-08-domain-compliance-validation.md'
|
nextStepFile: './step-v-08-domain-compliance-validation.md'
|
||||||
prdFile: '{prd_file_path}'
|
prdFile: '{prd_file_path}'
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
---
|
---
|
||||||
name: 'step-v-08-domain-compliance-validation'
|
|
||||||
description: 'Domain Compliance Validation - Validate domain-specific requirements are present for high-complexity domains'
|
|
||||||
|
|
||||||
# File references (ONLY variables used in this step)
|
# File references (ONLY variables used in this step)
|
||||||
nextStepFile: './step-v-09-project-type-validation.md'
|
nextStepFile: './step-v-09-project-type-validation.md'
|
||||||
prdFile: '{prd_file_path}'
|
prdFile: '{prd_file_path}'
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
---
|
---
|
||||||
name: 'step-v-09-project-type-validation'
|
|
||||||
description: 'Project-Type Compliance Validation - Validate project-type specific requirements are properly documented'
|
|
||||||
|
|
||||||
# File references (ONLY variables used in this step)
|
# File references (ONLY variables used in this step)
|
||||||
nextStepFile: './step-v-10-smart-validation.md'
|
nextStepFile: './step-v-10-smart-validation.md'
|
||||||
prdFile: '{prd_file_path}'
|
prdFile: '{prd_file_path}'
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
---
|
---
|
||||||
name: 'step-v-10-smart-validation'
|
|
||||||
description: 'SMART Requirements Validation - Validate Functional Requirements meet SMART quality criteria'
|
|
||||||
|
|
||||||
# File references (ONLY variables used in this step)
|
# File references (ONLY variables used in this step)
|
||||||
nextStepFile: './step-v-11-holistic-quality-validation.md'
|
nextStepFile: './step-v-11-holistic-quality-validation.md'
|
||||||
prdFile: '{prd_file_path}'
|
prdFile: '{prd_file_path}'
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
---
|
---
|
||||||
name: 'step-v-11-holistic-quality-validation'
|
|
||||||
description: 'Holistic Quality Assessment - Assess PRD as cohesive, compelling document - is it a good PRD?'
|
|
||||||
|
|
||||||
# File references (ONLY variables used in this step)
|
# File references (ONLY variables used in this step)
|
||||||
nextStepFile: './step-v-12-completeness-validation.md'
|
nextStepFile: './step-v-12-completeness-validation.md'
|
||||||
prdFile: '{prd_file_path}'
|
prdFile: '{prd_file_path}'
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
---
|
---
|
||||||
name: 'step-v-12-completeness-validation'
|
|
||||||
description: 'Completeness Check - Final comprehensive completeness check before report generation'
|
|
||||||
|
|
||||||
# File references (ONLY variables used in this step)
|
# File references (ONLY variables used in this step)
|
||||||
nextStepFile: './step-v-13-report-complete.md'
|
nextStepFile: './step-v-13-report-complete.md'
|
||||||
prdFile: '{prd_file_path}'
|
prdFile: '{prd_file_path}'
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
---
|
---
|
||||||
name: 'step-v-13-report-complete'
|
|
||||||
description: 'Validation Report Complete - Finalize report, summarize findings, present to user, offer next steps'
|
|
||||||
|
|
||||||
# File references (ONLY variables used in this step)
|
# File references (ONLY variables used in this step)
|
||||||
validationReportPath: '{validation_report_path}'
|
validationReportPath: '{validation_report_path}'
|
||||||
prdFile: '{prd_file_path}'
|
prdFile: '{prd_file_path}'
|
||||||
|
|
@ -180,9 +177,9 @@ Display:
|
||||||
- After review, return to menu
|
- After review, return to menu
|
||||||
|
|
||||||
- **IF E (Use Edit Workflow):**
|
- **IF E (Use Edit Workflow):**
|
||||||
- Explain: "The Edit workflow (steps-e/) can use this validation report to systematically address issues. Edit mode will guide you through discovering what to edit, reviewing the PRD, and applying targeted improvements."
|
- Explain: "The Edit workflow can use this validation report to systematically address issues. Edit mode will guide you through discovering what to edit, reviewing the PRD, and applying targeted improvements."
|
||||||
- Offer: "Would you like to launch Edit mode now? It will help you fix validation findings systematically."
|
- Offer: "Would you like to launch Edit mode now? It will help you fix validation findings systematically."
|
||||||
- If yes: Read fully and follow: steps-e/step-e-01-discovery.md
|
- If yes: Invoke the `bmad-edit-prd` skill, passing the validation report path as context
|
||||||
- If no: Return to menu
|
- If no: Return to menu
|
||||||
|
|
||||||
- **IF F (Fix Simpler Items):**
|
- **IF F (Fix Simpler Items):**
|
||||||
|
|
|
||||||
|
|
@ -182,7 +182,7 @@ Display:
|
||||||
- **IF E (Use Edit Workflow):**
|
- **IF E (Use Edit Workflow):**
|
||||||
- Explain: "The Edit workflow (steps-e/) can use this validation report to systematically address issues. Edit mode will guide you through discovering what to edit, reviewing the PRD, and applying targeted improvements."
|
- Explain: "The Edit workflow (steps-e/) can use this validation report to systematically address issues. Edit mode will guide you through discovering what to edit, reviewing the PRD, and applying targeted improvements."
|
||||||
- Offer: "Would you like to launch Edit mode now? It will help you fix validation findings systematically."
|
- Offer: "Would you like to launch Edit mode now? It will help you fix validation findings systematically."
|
||||||
- If yes: Read fully and follow: steps-e/step-e-01-discovery.md
|
- If yes: Read fully and follow: `./steps-e/step-e-01-discovery.md`
|
||||||
- If no: Return to menu
|
- If no: Return to menu
|
||||||
|
|
||||||
- **IF F (Fix Simpler Items):**
|
- **IF F (Fix Simpler Items):**
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-check-implementation-readiness
|
||||||
description: 'Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".'
|
description: 'Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-create-architecture
|
||||||
description: 'Create architecture solution design decisions for AI agent consistency. Use when the user says "lets create architecture" or "create technical architecture" or "create a solution design"'
|
description: 'Create architecture solution design decisions for AI agent consistency. Use when the user says "lets create architecture" or "create technical architecture" or "create a solution design"'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-create-epics-and-stories
|
||||||
description: 'Break requirements into epics and user stories. Use when the user says "create the epics and stories list"'
|
description: 'Break requirements into epics and user stories. Use when the user says "create the epics and stories list"'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-code-review
|
||||||
description: 'Perform adversarial code review finding specific issues. Use when the user says "run code review" or "review this code"'
|
description: 'Perform adversarial code review finding specific issues. Use when the user says "run code review" or "review this code"'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-correct-course
|
||||||
description: 'Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change"'
|
description: 'Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change"'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-create-story
|
||||||
description: 'Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]"'
|
description: 'Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]"'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -344,7 +344,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
|
||||||
</step>
|
</step>
|
||||||
|
|
||||||
<step n="6" goal="Update sprint status and finalize">
|
<step n="6" goal="Update sprint status and finalize">
|
||||||
<action>Validate the newly created story file {story_file} against `./checklist.md` and apply any required fixes before finalizing</action>
|
<action>Validate the newly created story file {default_output_file} against `./checklist.md` and apply any required fixes before finalizing</action>
|
||||||
<action>Save story document unconditionally</action>
|
<action>Save story document unconditionally</action>
|
||||||
|
|
||||||
<!-- Update sprint status -->
|
<!-- Update sprint status -->
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-dev-story
|
||||||
description: 'Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"'
|
description: 'Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-retrospective
|
||||||
description: 'Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"'
|
description: 'Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-sprint-planning
|
||||||
description: 'Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan"'
|
description: 'Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan"'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-sprint-status
|
||||||
description: 'Summarize sprint status and surface risks. Use when the user says "check sprint status" or "show sprint status"'
|
description: 'Summarize sprint status and surface risks. Use when the user says "check sprint status" or "show sprint status"'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-document-project
|
||||||
description: 'Document brownfield projects for AI context. Use when the user says "document this project" or "generate project docs"'
|
description: 'Document brownfield projects for AI context. Use when the user says "document this project" or "generate project docs"'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-generate-project-context
|
||||||
description: 'Create project-context.md with AI rules. Use when the user says "generate project context" or "create project context"'
|
description: 'Create project-context.md with AI rules. Use when the user says "generate project context" or "create project context"'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -123,7 +123,7 @@ Based on discovery, create or update the context document:
|
||||||
|
|
||||||
#### A. Fresh Document Setup (if no existing context)
|
#### A. Fresh Document Setup (if no existing context)
|
||||||
|
|
||||||
Copy template from `./project-context-template.md` to `{output_folder}/project-context.md`
|
Copy template from `../project-context-template.md` to `{output_folder}/project-context.md`
|
||||||
Initialize frontmatter fields.
|
Initialize frontmatter fields.
|
||||||
|
|
||||||
#### B. Existing Document Update
|
#### B. Existing Document Update
|
||||||
|
|
@ -160,6 +160,8 @@ Ready to create/update your project context. This will help AI agents implement
|
||||||
|
|
||||||
[C] Continue to context generation"
|
[C] Continue to context generation"
|
||||||
|
|
||||||
|
**HALT — wait for user selection before proceeding.**
|
||||||
|
|
||||||
## SUCCESS METRICS:
|
## SUCCESS METRICS:
|
||||||
|
|
||||||
✅ Existing project context properly detected and handled
|
✅ Existing project context properly detected and handled
|
||||||
|
|
|
||||||
|
|
@ -264,6 +264,8 @@ After each category, show the generated rules and present choices:
|
||||||
[P] Party Mode - Review from different implementation perspectives
|
[P] Party Mode - Review from different implementation perspectives
|
||||||
[C] Continue - Save these rules and move to next category"
|
[C] Continue - Save these rules and move to next category"
|
||||||
|
|
||||||
|
**HALT — wait for user selection before proceeding.**
|
||||||
|
|
||||||
### 10. Handle Menu Selection
|
### 10. Handle Menu Selection
|
||||||
|
|
||||||
#### If 'A' (Advanced Elicitation):
|
#### If 'A' (Advanced Elicitation):
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ 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 end to end automated tests for existing features. Use when the user says "create qa automated tests for [feature]"'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
|
|
||||||
**Goal:** Generate automated API and E2E tests for implemented code.
|
**Goal:** Generate automated API and E2E tests for implemented code.
|
||||||
|
|
||||||
**Your Role:** You are a QA automation engineer. You generate tests ONLY — no code review or story validation (use Code Review `CR` for that).
|
**Your Role:** You are a QA automation engineer. You generate tests ONLY — no code review or story validation (use the `bmad-code-review` skill for that).
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-quick-dev-new-preview
|
||||||
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: '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.'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-quick-dev
|
||||||
description: 'Implement a Quick Tech Spec for small changes or features. Use when the user provides a quick tech spec and says "implement this quick spec" or "proceed with implementation of [quick tech spec]"'
|
description: 'Implement a Quick Tech Spec for small changes or features. Use when the user provides a quick tech spec and says "implement this quick spec" or "proceed with implementation of [quick tech spec]"'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-quick-spec
|
||||||
description: 'Very quick process to create implementation-ready quick specs for small changes or features. Use when the user says "create a quick spec" or "generate a quick tech spec"'
|
description: 'Very quick process to create implementation-ready quick specs for small changes or features. Use when the user says "create a quick spec" or "generate a quick tech spec"'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -1,6 +1,6 @@
|
||||||
---
|
---
|
||||||
name: bmad-advanced-elicitation
|
name: bmad-advanced-elicitation
|
||||||
description: 'Push the LLM to reconsider refine and improve its recent output.'
|
description: 'Push the LLM to reconsider, refine, and improve its recent output.'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -96,9 +96,9 @@ x. Proceed / No Further Actions
|
||||||
**Case x (Proceed):**
|
**Case x (Proceed):**
|
||||||
|
|
||||||
- Complete elicitation and proceed
|
- Complete elicitation and proceed
|
||||||
- Return the fully enhanced content back to create-doc.md
|
- Return the fully enhanced content back to the invoking skill
|
||||||
- The enhanced content becomes the final version for that section
|
- The enhanced content becomes the final version for that section
|
||||||
- Signal completion back to create-doc.md to continue with next section
|
- Signal completion back to the invoking skill to continue with next section
|
||||||
|
|
||||||
**Case a (List All):**
|
**Case a (List All):**
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-brainstorming
|
||||||
description: 'Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods. Use when the user says help me brainstorm or help me ideate.'
|
description: 'Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods. Use when the user says help me brainstorm or help me ideate.'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -48,6 +48,8 @@ If existing session files are found:
|
||||||
**[2]** Start a new session
|
**[2]** Start a new session
|
||||||
**[3]** See all existing sessions"
|
**[3]** See all existing sessions"
|
||||||
|
|
||||||
|
**HALT — wait for user selection before proceeding.**
|
||||||
|
|
||||||
- If user selects **[1]** (continue): Set `{brainstorming_session_output_file}` to that file path and load `./step-01b-continue.md`
|
- If user selects **[1]** (continue): Set `{brainstorming_session_output_file}` to that file path and load `./step-01b-continue.md`
|
||||||
- If user selects **[2]** (new): Generate new filename with current date/time and proceed to step 3
|
- If user selects **[2]** (new): Generate new filename with current date/time and proceed to step 3
|
||||||
- If user selects **[3]** (see all): List all session filenames and ask which to continue or if new
|
- If user selects **[3]** (see all): List all session filenames and ask which to continue or if new
|
||||||
|
|
@ -155,6 +157,8 @@ When user selects approach, append the session overview content directly to `{br
|
||||||
|
|
||||||
Which approach appeals to you most? (Enter 1-4)"
|
Which approach appeals to you most? (Enter 1-4)"
|
||||||
|
|
||||||
|
**HALT — wait for user selection before proceeding.**
|
||||||
|
|
||||||
### 4. Handle User Selection and Initial Document Append
|
### 4. Handle User Selection and Initial Document Append
|
||||||
|
|
||||||
#### When user selects approach number:
|
#### When user selects approach number:
|
||||||
|
|
|
||||||
|
|
@ -63,7 +63,9 @@ Based on session analysis, provide appropriate options:
|
||||||
**Options:**
|
**Options:**
|
||||||
[1] Review Results - Go through your documented ideas and insights
|
[1] Review Results - Go through your documented ideas and insights
|
||||||
[2] Start New Session - Begin brainstorming on a new topic
|
[2] Start New Session - Begin brainstorming on a new topic
|
||||||
[3) Extend Session - Add more techniques or explore new angles"
|
[3] Extend Session - Add more techniques or explore new angles"
|
||||||
|
|
||||||
|
**HALT — wait for user selection before proceeding.**
|
||||||
|
|
||||||
**If Session In Progress:**
|
**If Session In Progress:**
|
||||||
"Let's continue where we left off!
|
"Let's continue where we left off!
|
||||||
|
|
|
||||||
|
|
@ -40,7 +40,7 @@ Load techniques from CSV on-demand:
|
||||||
|
|
||||||
**Load CSV and parse:**
|
**Load CSV and parse:**
|
||||||
|
|
||||||
- Read `brain-methods.csv`
|
- Read `../brain-methods.csv`
|
||||||
- Parse: category, technique_name, description, facilitation_prompts, best_for, energy_level, typical_duration
|
- Parse: category, technique_name, description, facilitation_prompts, best_for, energy_level, typical_duration
|
||||||
- Organize by categories for browsing
|
- Organize by categories for browsing
|
||||||
|
|
||||||
|
|
@ -87,6 +87,8 @@ Show available categories with brief descriptions:
|
||||||
|
|
||||||
**Which category interests you most? Enter 1-7, or tell me what type of thinking you're drawn to.**"
|
**Which category interests you most? Enter 1-7, or tell me what type of thinking you're drawn to.**"
|
||||||
|
|
||||||
|
**HALT — wait for user selection before proceeding.**
|
||||||
|
|
||||||
### 3. Handle Category Selection
|
### 3. Handle Category Selection
|
||||||
|
|
||||||
After user selects category:
|
After user selects category:
|
||||||
|
|
@ -154,6 +156,8 @@ This combination will take approximately [total_time] and focus on [expected out
|
||||||
[C] Continue - Begin technique execution
|
[C] Continue - Begin technique execution
|
||||||
[Back] - Modify technique selection"
|
[Back] - Modify technique selection"
|
||||||
|
|
||||||
|
**HALT — wait for user selection before proceeding.**
|
||||||
|
|
||||||
### 6. Update Frontmatter and Continue
|
### 6. Update Frontmatter and Continue
|
||||||
|
|
||||||
If user confirms:
|
If user confirms:
|
||||||
|
|
|
||||||
|
|
@ -47,7 +47,7 @@ Load techniques from CSV for analysis:
|
||||||
|
|
||||||
**Load CSV and parse:**
|
**Load CSV and parse:**
|
||||||
|
|
||||||
- Read `brain-methods.csv`
|
- Read `../brain-methods.csv`
|
||||||
- Parse: category, technique_name, description, facilitation_prompts, best_for, energy_level, typical_duration
|
- Parse: category, technique_name, description, facilitation_prompts, best_for, energy_level, typical_duration
|
||||||
|
|
||||||
### 2. Context Analysis for Technique Matching
|
### 2. Context Analysis for Technique Matching
|
||||||
|
|
@ -152,6 +152,8 @@ Provide deeper insight into each recommended technique:
|
||||||
[Details] - Tell me more about any specific technique
|
[Details] - Tell me more about any specific technique
|
||||||
[Back] - Return to approach selection
|
[Back] - Return to approach selection
|
||||||
|
|
||||||
|
**HALT — wait for user selection before proceeding.**
|
||||||
|
|
||||||
### 6. Handle User Response
|
### 6. Handle User Response
|
||||||
|
|
||||||
#### If [C] Continue:
|
#### If [C] Continue:
|
||||||
|
|
|
||||||
|
|
@ -47,7 +47,7 @@ Create anticipation for serendipitous technique discovery:
|
||||||
|
|
||||||
**Load CSV and parse:**
|
**Load CSV and parse:**
|
||||||
|
|
||||||
- Read `brain-methods.csv`
|
- Read `../brain-methods.csv`
|
||||||
- Parse: category, technique_name, description, facilitation_prompts, best_for, energy_level, typical_duration
|
- Parse: category, technique_name, description, facilitation_prompts, best_for, energy_level, typical_duration
|
||||||
- Prepare for intelligent random selection
|
- Prepare for intelligent random selection
|
||||||
|
|
||||||
|
|
@ -124,6 +124,8 @@ You're about to experience brainstorming in a completely new way. These unexpect
|
||||||
[Details] - Tell me more about any specific technique
|
[Details] - Tell me more about any specific technique
|
||||||
[Back] - Return to approach selection
|
[Back] - Return to approach selection
|
||||||
|
|
||||||
|
**HALT — wait for user selection before proceeding.**
|
||||||
|
|
||||||
### 5. Handle User Response
|
### 5. Handle User Response
|
||||||
|
|
||||||
#### If [C] Continue:
|
#### If [C] Continue:
|
||||||
|
|
|
||||||
|
|
@ -66,7 +66,7 @@ Explain the value of systematic creative progression:
|
||||||
|
|
||||||
**Load CSV and parse:**
|
**Load CSV and parse:**
|
||||||
|
|
||||||
- Read `brain-methods.csv`
|
- Read `../brain-methods.csv`
|
||||||
- Parse: category, technique_name, description, facilitation_prompts, best_for, energy_level, typical_duration
|
- Parse: category, technique_name, description, facilitation_prompts, best_for, energy_level, typical_duration
|
||||||
- Map techniques to each phase of the creative journey
|
- Map techniques to each phase of the creative journey
|
||||||
|
|
||||||
|
|
@ -176,6 +176,8 @@ Show the full progressive flow with timing and transitions:
|
||||||
[Details] - Tell me more about any specific phase or technique
|
[Details] - Tell me more about any specific phase or technique
|
||||||
[Back] - Return to approach selection
|
[Back] - Return to approach selection
|
||||||
|
|
||||||
|
**HALT — wait for user selection before proceeding.**
|
||||||
|
|
||||||
### 4. Handle Customization Requests
|
### 4. Handle Customization Requests
|
||||||
|
|
||||||
If user wants customization:
|
If user wants customization:
|
||||||
|
|
|
||||||
|
|
@ -290,6 +290,8 @@ After final technique element:
|
||||||
[B] **Take a quick break** - Pause and return with fresh energy
|
[B] **Take a quick break** - Pause and return with fresh energy
|
||||||
[C] **Move to organization** - Only when you feel we've thoroughly explored
|
[C] **Move to organization** - Only when you feel we've thoroughly explored
|
||||||
|
|
||||||
|
**HALT — wait for user selection before proceeding.**
|
||||||
|
|
||||||
**Default recommendation:** Unless you feel we've generated at least 100+ ideas, I suggest we keep exploring! The best insights often come after the obvious ideas are exhausted.
|
**Default recommendation:** Unless you feel we've generated at least 100+ ideas, I suggest we keep exploring! The best insights often come after the obvious ideas are exhausted.
|
||||||
|
|
||||||
### 8. Handle Menu Selection
|
### 8. Handle Menu Selection
|
||||||
|
|
|
||||||
|
|
@ -249,6 +249,8 @@ Provide final session wrap-up and forward guidance:
|
||||||
**Ready to complete your session documentation?**
|
**Ready to complete your session documentation?**
|
||||||
[C] Complete - Generate final brainstorming session document
|
[C] Complete - Generate final brainstorming session document
|
||||||
|
|
||||||
|
**HALT — wait for user selection before proceeding.**
|
||||||
|
|
||||||
### 8. Handle Completion Selection
|
### 8. Handle Completion Selection
|
||||||
|
|
||||||
#### If [C] Complete:
|
#### If [C] Complete:
|
||||||
|
|
|
||||||
|
|
@ -48,6 +48,6 @@ All steps MUST reference `{brainstorming_session_output_file}` instead of the fu
|
||||||
|
|
||||||
## EXECUTION
|
## EXECUTION
|
||||||
|
|
||||||
Read fully and follow: `steps/step-01-session-setup.md` to begin the workflow.
|
Read fully and follow: `./steps/step-01-session-setup.md` to begin the workflow.
|
||||||
|
|
||||||
**Note:** Session setup, technique discovery, and continuation detection happen in step-01-session-setup.md.
|
**Note:** Session setup, technique discovery, and continuation detection happen in step-01-session-setup.md.
|
||||||
|
|
|
||||||
|
|
@ -4,7 +4,7 @@ Act as an information extraction and compression specialist. Your sole purpose i
|
||||||
|
|
||||||
You receive: source document file paths, an optional downstream_consumer context, and a splitting decision.
|
You receive: source document file paths, an optional downstream_consumer context, and a splitting decision.
|
||||||
|
|
||||||
You must load and apply `resources/compression-rules.md` before producing output. Reference `resources/distillate-format-reference.md` for the expected output format.
|
You must load and apply `../resources/compression-rules.md` before producing output. Reference `../resources/distillate-format-reference.md` for the expected output format.
|
||||||
|
|
||||||
## Compression Process
|
## Compression Process
|
||||||
|
|
||||||
|
|
@ -31,7 +31,7 @@ Treat this as entity extraction — pull out every distinct piece of information
|
||||||
|
|
||||||
### Step 3: Deduplicate
|
### Step 3: Deduplicate
|
||||||
|
|
||||||
Apply the deduplication rules from `resources/compression-rules.md`.
|
Apply the deduplication rules from `../resources/compression-rules.md`.
|
||||||
|
|
||||||
### Step 4: Filter (only if downstream_consumer is specified)
|
### Step 4: Filter (only if downstream_consumer is specified)
|
||||||
|
|
||||||
|
|
@ -58,7 +58,7 @@ Common groupings (use what fits, omit what doesn't, add what's needed):
|
||||||
|
|
||||||
### Step 6: Compress Language
|
### Step 6: Compress Language
|
||||||
|
|
||||||
For each item, apply the compression rules from `resources/compression-rules.md`:
|
For each item, apply the compression rules from `../resources/compression-rules.md`:
|
||||||
- Strip prose transitions and connective tissue
|
- Strip prose transitions and connective tissue
|
||||||
- Remove hedging and rhetoric
|
- Remove hedging and rhetoric
|
||||||
- Remove explanations of common knowledge
|
- Remove explanations of common knowledge
|
||||||
|
|
@ -80,7 +80,7 @@ Do NOT include frontmatter — the calling skill handles that.
|
||||||
|
|
||||||
## Semantic Splitting
|
## Semantic Splitting
|
||||||
|
|
||||||
If the splitting decision indicates splitting is needed, load `resources/splitting-strategy.md` and follow it.
|
If the splitting decision indicates splitting is needed, load `../resources/splitting-strategy.md` and follow it.
|
||||||
|
|
||||||
When splitting:
|
When splitting:
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-editorial-review-prose
|
||||||
description: 'Clinical copy-editor that reviews text for communication issues. Use when user says review for prose or improve the prose'
|
description: 'Clinical copy-editor that reviews text for communication issues. Use when user says review for prose or improve the prose'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-editorial-review-structure
|
||||||
description: 'Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension. Use when user requests structural review or editorial review of structure'
|
description: 'Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension. Use when user requests structural review or editorial review of structure'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-help
|
||||||
description: 'Analyzes what is done and the users query and offers advice on what to do next. Use if user says what should I do next or what do I do now'
|
description: 'Analyzes what is done and the users query and offers advice on what to do next. Use if user says what should I do next or what do I do now'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-index-docs
|
||||||
description: 'Generates or updates an index.md to reference all docs in the folder. Use if user requests to create or update an index of all files in a specific folder'
|
description: 'Generates or updates an index.md to reference all docs in the folder. Use if user requests to create or update an index of all files in a specific folder'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-party-mode
|
||||||
description: 'Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations. Use when user requests party mode.'
|
description: 'Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations. Use when user requests party mode.'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-review-adversarial-general
|
||||||
description: 'Perform a Cynical Review and produce a findings report. Use when the user requests a critical review of something'
|
description: 'Perform a Cynical Review and produce a findings report. Use when the user requests a critical review of something'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -1,6 +1,6 @@
|
||||||
---
|
---
|
||||||
name: bmad-review-edge-case-hunter
|
name: bmad-review-edge-case-hunter
|
||||||
description: 'Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven.'
|
description: 'Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven. Use when you need exhaustive edge-case analysis of code, specs, or diffs.'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-shard-doc
|
||||||
description: 'Splits large markdown documents into smaller, organized files based on level 2 (default) sections. Use if the user says perform shard document'
|
description: 'Splits large markdown documents into smaller, organized files based on level 2 (default) sections. Use if the user says perform shard document'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -3,4 +3,4 @@ name: bmad-create-prd
|
||||||
description: 'Create a PRD from scratch. Use when the user says "lets create a product requirements document" or "I want to create a new PRD"'
|
description: 'Create a PRD from scratch. Use when the user says "lets create a product requirements document" or "I want to create a new PRD"'
|
||||||
---
|
---
|
||||||
|
|
||||||
Follow the instructions in [workflow.md](workflow.md).
|
Follow the instructions in ./workflow.md.
|
||||||
|
|
|
||||||
|
|
@ -118,7 +118,7 @@ If no findings are generated, the skill passes validation.
|
||||||
- CORRECT: `./steps/step-01-init.md` (from workflow.md at skill root to a step)
|
- CORRECT: `./steps/step-01-init.md` (from workflow.md at skill root to a step)
|
||||||
- CORRECT: `./template.md` (from workflow.md to a sibling)
|
- CORRECT: `./template.md` (from workflow.md to a sibling)
|
||||||
- CORRECT: `../template.md` (from steps/step-01.md to a skill-root file)
|
- CORRECT: `../template.md` (from steps/step-01.md to a skill-root file)
|
||||||
- CORRECT: `[workflow.md](workflow.md)` (markdown link to sibling — bare relative)
|
- CORRECT: `workflow.md` (bare relative filename for sibling)
|
||||||
- CORRECT: `./step-02-plan.md` (from steps/step-01.md to a sibling step)
|
- CORRECT: `./step-02-plan.md` (from steps/step-01.md to a sibling step)
|
||||||
- WRONG: `./steps/step-02-plan.md` (from a file already inside steps/ — resolves to steps/steps/)
|
- WRONG: `./steps/step-02-plan.md` (from a file already inside steps/ — resolves to steps/steps/)
|
||||||
- WRONG: `{installed_path}/template.md`
|
- WRONG: `{installed_path}/template.md`
|
||||||
|
|
@ -274,9 +274,9 @@ If no findings are generated, the skill passes validation.
|
||||||
|
|
||||||
- **Severity:** HIGH
|
- **Severity:** HIGH
|
||||||
- **Applies to:** all files
|
- **Applies to:** all files
|
||||||
- **Rule:** When a skill references another skill via `skill:skill-name`, the surrounding instruction must use the word "invoke" (e.g., `Invoke skill:bmad-party-mode`). Phrases like "Read fully and follow", "Execute", "Run", "Load", "Open", or "Follow" are invalid — they imply file-level operations on a document, not skill invocation. A skill is a unit that is invoked, not a file that is read.
|
- **Rule:** When a skill references another skill by name, the surrounding instruction must use the word "invoke". The canonical form is `Invoke the \`skill-name\` skill`. Phrases like "Read fully and follow", "Execute", "Run", "Load", "Open", or "Follow" are invalid — they imply file-level operations on a document, not skill invocation. A skill is a unit that is invoked, not a file that is read.
|
||||||
- **Detection:** Find all `skill:` references in body text and frontmatter. Check the surrounding instruction text (same sentence or directive) for file-oriented verbs: "read", "follow", "load", "execute", "run", "open". Flag any that do not use "invoke" (or a close synonym like "activate" or "launch").
|
- **Detection:** Find all references to other skills by name (typically backtick-quoted skill names like \`bmad-foo\`). Check the surrounding instruction text (same sentence or directive) for file-oriented verbs: "read", "follow", "load", "execute", "run", "open". Flag any that do not use "invoke" (or a close synonym like "activate" or "launch").
|
||||||
- **Fix:** Replace the instruction with `Invoke skill:skill-name` or `Invoke the \`skill-name\` skill`. Remove any "read fully and follow" or similar file-oriented phrasing.
|
- **Fix:** Replace the instruction with `Invoke the \`skill-name\` skill`. Remove any "read fully and follow" or similar file-oriented phrasing. Do NOT add a `skill:` prefix to the name — use natural language.
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue