refactor: inline all frontmatter refs, use canonical skill invocation
- Remove all file/task reference variables from step frontmatter - Inline paths directly where used in body text - Use canonical "invoke the skill" phrasing for skill references Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Alex Verkhovsky
parent
3290caccf8
commit
8f2350546a
|
|
@ -1,11 +1,6 @@
|
|||
---
|
||||
name: 'step-01-validate-prerequisites'
|
||||
description: 'Validate required documents exist and extract all requirements for epic and story creation'
|
||||
|
||||
# File References
|
||||
nextStepFile: './step-02-design-epics.md'
|
||||
outputFile: '{planning_artifacts}/epics.md'
|
||||
epicsTemplate: '../templates/epics-template.md'
|
||||
---
|
||||
|
||||
# Step 1: Validate Prerequisites and Extract Requirements
|
||||
|
|
@ -42,7 +37,7 @@ To validate that all required input documents exist and extract all requirements
|
|||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Extract requirements systematically from all documents
|
||||
- 💾 Populate {outputFile} with extracted requirements
|
||||
- 💾 Populate {planning_artifacts}/epics.md with extracted requirements
|
||||
- 📖 Update frontmatter with extraction progress
|
||||
- 🚫 FORBIDDEN to load next step until user selects 'C' and requirements are extracted
|
||||
|
||||
|
|
@ -79,7 +74,7 @@ Search for required documents using these patterns (sharded means a large docume
|
|||
1. `{planning_artifacts}/*ux*.md` (whole document)
|
||||
2. `{planning_artifacts}/*ux*/index.md` (sharded version)
|
||||
|
||||
Before proceeding, Ask the user if there are any other documents to include for analysis, and if anything found should be excluded. Wait for user confirmation. Once confirmed, create the {outputFile} from the {epicsTemplate} and in the front matter list the files in the array of `inputDocuments: []`.
|
||||
Before proceeding, Ask the user if there are any other documents to include for analysis, and if anything found should be excluded. Wait for user confirmation. Once confirmed, create the {planning_artifacts}/epics.md from the ../templates/epics-template.md and in the front matter list the files in the array of `inputDocuments: []`.
|
||||
|
||||
### 3. Extract Functional Requirements (FRs)
|
||||
|
||||
|
|
@ -170,9 +165,9 @@ UX-DR2: [Actionable UX design requirement with clear implementation scope]
|
|||
|
||||
### 7. Load and Initialize Template
|
||||
|
||||
Load {epicsTemplate} and initialize {outputFile}:
|
||||
Load ../templates/epics-template.md and initialize {planning_artifacts}/epics.md:
|
||||
|
||||
1. Copy the entire template to {outputFile}
|
||||
1. Copy the entire template to {planning_artifacts}/epics.md
|
||||
2. Replace {{project_name}} with the actual project name
|
||||
3. Replace placeholder sections with extracted requirements:
|
||||
- {{fr_list}} → extracted FRs
|
||||
|
|
@ -216,7 +211,7 @@ Update the requirements based on user feedback until confirmation is received.
|
|||
|
||||
## CONTENT TO SAVE TO DOCUMENT:
|
||||
|
||||
After extraction and confirmation, update {outputFile} with:
|
||||
After extraction and confirmation, update {planning_artifacts}/epics.md with:
|
||||
|
||||
- Complete FR list in {{fr_list}} section
|
||||
- Complete NFR list in {{nfr_list}} section
|
||||
|
|
@ -235,12 +230,12 @@ Display: `**Confirm the Requirements are complete and correct to [C] continue:**
|
|||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF C: Save all to {outputFile}, update frontmatter, then read fully and follow: {nextStepFile}
|
||||
- IF C: Save all to {planning_artifacts}/epics.md, update frontmatter, then read fully and follow: ./step-02-design-epics.md
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#10-present-menu-options)
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN C is selected and all requirements are saved to document and frontmatter is updated, will you then read fully and follow: {nextStepFile} to begin epic design step.
|
||||
ONLY WHEN C is selected and all requirements are saved to document and frontmatter is updated, will you then read fully and follow: ./step-02-design-epics.md to begin epic design step.
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,14 +1,6 @@
|
|||
---
|
||||
name: 'step-02-design-epics'
|
||||
description: 'Design and approve the epics_list that will organize all requirements into user-value-focused epics'
|
||||
|
||||
# File References
|
||||
nextStepFile: './step-03-create-stories.md'
|
||||
outputFile: '{planning_artifacts}/epics.md'
|
||||
|
||||
# Task References
|
||||
advancedElicitationTask: 'skill:bmad-advanced-elicitation'
|
||||
partyModeWorkflow: 'skill:bmad-party-mode'
|
||||
---
|
||||
|
||||
# Step 2: Design Epic List
|
||||
|
|
@ -46,7 +38,7 @@ To design and get approval for the epics_list that will organize all requirement
|
|||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Design epics collaboratively based on extracted requirements
|
||||
- 💾 Update {{epics_list}} in {outputFile}
|
||||
- 💾 Update {{epics_list}} in {planning_artifacts}/epics.md
|
||||
- 📖 Document the FR coverage mapping
|
||||
- 🚫 FORBIDDEN to load next step until user approves epics_list
|
||||
|
||||
|
|
@ -54,7 +46,7 @@ To design and get approval for the epics_list that will organize all requirement
|
|||
|
||||
### 1. Review Extracted Requirements
|
||||
|
||||
Load {outputFile} and review:
|
||||
Load {planning_artifacts}/epics.md and review:
|
||||
|
||||
- **Functional Requirements:** Count and review FRs from Step 1
|
||||
- **Non-Functional Requirements:** Review NFRs that need to be addressed
|
||||
|
|
@ -174,7 +166,7 @@ If user wants changes:
|
|||
|
||||
## CONTENT TO UPDATE IN DOCUMENT:
|
||||
|
||||
After approval, update {outputFile}:
|
||||
After approval, update {planning_artifacts}/epics.md:
|
||||
|
||||
1. Replace {{epics_list}} placeholder with the approved epic list
|
||||
2. Replace {{requirements_coverage_map}} with the coverage map
|
||||
|
|
@ -186,9 +178,9 @@ Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Cont
|
|||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF A: Read fully and follow: {advancedElicitationTask}
|
||||
- IF P: Read fully and follow: {partyModeWorkflow}
|
||||
- IF C: Save approved epics_list to {outputFile}, update frontmatter, then read fully and follow: {nextStepFile}
|
||||
- IF A: Invoke the `bmad-advanced-elicitation` skill
|
||||
- IF P: Invoke the `bmad-party-mode` skill
|
||||
- IF C: Save approved epics_list to {planning_artifacts}/epics.md, update frontmatter, then read fully and follow: ./step-03-create-stories.md
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#8-present-menu-options)
|
||||
|
||||
#### EXECUTION RULES:
|
||||
|
|
@ -200,7 +192,7 @@ Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Cont
|
|||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN C is selected and the approved epics_list is saved to document, will you then read fully and follow: {nextStepFile} to begin story creation step.
|
||||
ONLY WHEN C is selected and the approved epics_list is saved to document, will you then read fully and follow: ./step-03-create-stories.md to begin story creation step.
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,14 +1,6 @@
|
|||
---
|
||||
name: 'step-03-create-stories'
|
||||
description: 'Generate all epics with their stories following the template structure'
|
||||
|
||||
# File References
|
||||
nextStepFile: './step-04-final-validation.md'
|
||||
outputFile: '{planning_artifacts}/epics.md'
|
||||
|
||||
# Task References
|
||||
advancedElicitationTask: 'skill:bmad-advanced-elicitation'
|
||||
partyModeWorkflow: 'skill:bmad-party-mode'
|
||||
---
|
||||
|
||||
# Step 3: Generate Epics and Stories
|
||||
|
|
@ -46,7 +38,7 @@ To generate all epics with their stories based on the approved epics_list, follo
|
|||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Generate stories collaboratively with user input
|
||||
- 💾 Append epics and stories to {outputFile} following template
|
||||
- 💾 Append epics and stories to {planning_artifacts}/epics.md following template
|
||||
- 📖 Process epics one at a time in sequence
|
||||
- 🚫 FORBIDDEN to skip any epic or rush through stories
|
||||
|
||||
|
|
@ -54,7 +46,7 @@ To generate all epics with their stories based on the approved epics_list, follo
|
|||
|
||||
### 1. Load Approved Epic Structure
|
||||
|
||||
Load {outputFile} and review:
|
||||
Load {planning_artifacts}/epics.md and review:
|
||||
|
||||
- Approved epics_list from Step 2
|
||||
- FR coverage map
|
||||
|
|
@ -178,7 +170,7 @@ After writing each story:
|
|||
|
||||
When story is approved:
|
||||
|
||||
- Append it to {outputFile} following template structure
|
||||
- Append it to {planning_artifacts}/epics.md following template structure
|
||||
- Use correct numbering (Epic N, Story M)
|
||||
- Maintain proper markdown formatting
|
||||
|
||||
|
|
@ -207,7 +199,7 @@ After all epics and stories are generated:
|
|||
|
||||
## TEMPLATE STRUCTURE COMPLIANCE:
|
||||
|
||||
The final {outputFile} must follow this structure exactly:
|
||||
The final {planning_artifacts}/epics.md must follow this structure exactly:
|
||||
|
||||
1. **Overview** section with project name
|
||||
2. **Requirements Inventory** with all three subsections populated
|
||||
|
|
@ -227,9 +219,9 @@ Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Cont
|
|||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF A: Read fully and follow: {advancedElicitationTask}
|
||||
- IF P: Read fully and follow: {partyModeWorkflow}
|
||||
- IF C: Save content to {outputFile}, update frontmatter, then read fully and follow: {nextStepFile}
|
||||
- IF A: Invoke the `bmad-advanced-elicitation` skill
|
||||
- IF P: Invoke the `bmad-party-mode` skill
|
||||
- IF C: Save content to {planning_artifacts}/epics.md, update frontmatter, then read fully and follow: ./step-04-final-validation.md
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-final-menu-options)
|
||||
|
||||
#### EXECUTION RULES:
|
||||
|
|
@ -241,7 +233,7 @@ Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Cont
|
|||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN [C continue option] is selected and [all epics and stories saved to document following the template structure exactly], will you then read fully and follow: `{nextStepFile}` to begin final validation phase.
|
||||
ONLY WHEN [C continue option] is selected and [all epics and stories saved to document following the template structure exactly], will you then read fully and follow: `./step-04-final-validation.md` to begin final validation phase.
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,9 +1,6 @@
|
|||
---
|
||||
name: 'step-04-final-validation'
|
||||
description: 'Validate complete coverage of all requirements and ensure implementation readiness'
|
||||
|
||||
# File References
|
||||
outputFile: '{planning_artifacts}/epics.md'
|
||||
---
|
||||
|
||||
# Step 4: Final Validation
|
||||
|
|
|
|||
Loading…
Reference in New Issue