ros/BMAD-METHOD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

date removed from status file, status file renamed

Browse Source
This commit is contained in:
Brian Madison
2025-10-13 22:32:35 -05:00
parent 27586e6a40
commit 4b6f34dff8
39 changed files with 116 additions and 116 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
src/modules/bmm/workflows/1-analysis/brainstorm-game/instructions.md
View File

@@ -5,8 +5,8 @@
<workflow>
<step n="1" goal="Check and load workflow status file">
<action>Search {output_folder}/ for files matching pattern: project-workflow-status*.md</action>
<action>Find the most recent file (by date in filename: project-workflow-status-YYYY-MM-DD.md)</action>
<action>Search {output_folder}/ for files matching pattern: bmm-workflow-status.md</action>
<action>Find the most recent file (by date in filename: bmm-workflow-status.md)</action>
<check if="exists">
<action>Load the status file</action>
@@ -63,7 +63,7 @@ What would you like to do?</ask>
</step>
<step n="4" goal="Update status file on completion">
<action>Search {output_folder}/ for files matching pattern: project-workflow-status*.md</action>
<action>Search {output_folder}/ for files matching pattern: bmm-workflow-status.md</action>
<action>Find the most recent file (by date in filename)</action>
<check if="status file exists">

6
src/modules/bmm/workflows/1-analysis/brainstorm-project/instructions.md
View File

@@ -8,8 +8,8 @@
<workflow>
<step n="1" goal="Check and load workflow status file">
<action>Search {output_folder}/ for files matching pattern: project-workflow-status*.md</action>
<action>Find the most recent file (by date in filename: project-workflow-status-YYYY-MM-DD.md)</action>
<action>Search {output_folder}/ for files matching pattern: bmm-workflow-status.md</action>
<action>Find the most recent file (by date in filename: bmm-workflow-status.md)</action>
<check if="exists">
<action>Load the status file</action>
@@ -56,7 +56,7 @@ What would you like to do?</ask>
</step>
<step n="4" goal="Update status file on completion">
<action>Search {output_folder}/ for files matching pattern: project-workflow-status*.md</action>
<action>Search {output_folder}/ for files matching pattern: bmm-workflow-status.md</action>
<action>Find the most recent file (by date in filename)</action>
<check if="status file exists">

4
src/modules/bmm/workflows/1-analysis/document-project/instructions.md
View File

@@ -8,8 +8,8 @@
<step n="1" goal="Check and load workflow status file">
<action>Search {output_folder}/ for files matching pattern: project-workflow-status\*.md</action>
<action>Find the most recent file (by date in filename: project-workflow-status-YYYY-MM-DD.md)</action>
<action>Search {output_folder}/ for files matching pattern: bmm-workflow-status\*.md</action>
<action>Find the most recent file (by date in filename: bmm-workflow-status.md)</action>
<check if="exists">
<action>Load the status file</action>

6
src/modules/bmm/workflows/1-analysis/game-brief/instructions.md
View File

@@ -6,8 +6,8 @@
<workflow>
<step n="0" goal="Check and load workflow status file">
<action>Search {output_folder}/ for files matching pattern: project-workflow-status*.md</action>
<action>Find the most recent file (by date in filename: project-workflow-status-YYYY-MM-DD.md)</action>
<action>Search {output_folder}/ for files matching pattern: bmm-workflow-status.md</action>
<action>Find the most recent file (by date in filename: bmm-workflow-status.md)</action>
<check if="exists">
<action>Load the status file</action>
@@ -543,7 +543,7 @@ This brief will serve as the primary input for creating the Game Design Document
</step>
<step n="16" goal="Update status file on completion">
<action>Search {output_folder}/ for files matching pattern: project-workflow-status*.md</action>
<action>Search {output_folder}/ for files matching pattern: bmm-workflow-status.md</action>
<action>Find the most recent file (by date in filename)</action>
<check if="status file exists">

6
src/modules/bmm/workflows/1-analysis/product-brief/instructions.md
View File

@@ -6,8 +6,8 @@
<workflow>
<step n="0" goal="Check and load workflow status file">
<action>Search {output_folder}/ for files matching pattern: project-workflow-status*.md</action>
<action>Find the most recent file (by date in filename: project-workflow-status-YYYY-MM-DD.md)</action>
<action>Search {output_folder}/ for files matching pattern: bmm-workflow-status.md</action>
<action>Find the most recent file (by date in filename: bmm-workflow-status.md)</action>
<check if="exists">
<action>Load the status file</action>
@@ -379,7 +379,7 @@ This brief will serve as the primary input for creating the Product Requirements
</step>
<step n="16" goal="Update status file on completion">
<action>Search {output_folder}/ for files matching pattern: project-workflow-status*.md</action>
<action>Search {output_folder}/ for files matching pattern: bmm-workflow-status.md</action>
<action>Find the most recent file (by date in filename)</action>
<check if="status file exists">

2
src/modules/bmm/workflows/1-analysis/research/instructions-deep-prompt.md
View File

@@ -375,7 +375,7 @@ Select option (1-4):</ask>
</step>
<step n="FINAL" goal="Update status file on completion">
<action>Search {output_folder}/ for files matching pattern: project-workflow-status*.md</action>
<action>Search {output_folder}/ for files matching pattern: bmm-workflow-status.md</action>
<action>Find the most recent file (by date in filename)</action>
<check if="status file exists">

2
src/modules/bmm/workflows/1-analysis/research/instructions-market.md
View File

@@ -555,7 +555,7 @@ Create compelling executive summary with:
</step>
<step n="14" goal="Update status file on completion">
<action>Search {output_folder}/ for files matching pattern: project-workflow-status*.md</action>
<action>Search {output_folder}/ for files matching pattern: bmm-workflow-status.md</action>
<action>Find the most recent file (by date in filename)</action>
<check if="status file exists">

4
src/modules/bmm/workflows/1-analysis/research/instructions-router.md
View File

@@ -9,8 +9,8 @@
<workflow>
<step n="1" goal="Check and load workflow status file">
<action>Search {output_folder}/ for files matching pattern: project-workflow-status*.md</action>
<action>Find the most recent file (by date in filename: project-workflow-status-YYYY-MM-DD.md)</action>
<action>Search {output_folder}/ for files matching pattern: bmm-workflow-status.md</action>
<action>Find the most recent file (by date in filename: bmm-workflow-status.md)</action>
<check if="exists">
<action>Load the status file</action>

2
src/modules/bmm/workflows/1-analysis/research/instructions-technical.md
View File

@@ -443,7 +443,7 @@ Select option (1-5):</ask>
</step>
<step n="FINAL" goal="Update status file on completion">
<action>Search {output_folder}/ for files matching pattern: project-workflow-status*.md</action>
<action>Search {output_folder}/ for files matching pattern: bmm-workflow-status.md</action>
<action>Find the most recent file (by date in filename)</action>
<check if="status file exists">

12
src/modules/bmm/workflows/1-analysis/workflow-status/README.md
View File

@@ -72,7 +72,7 @@ The workflow builds a comprehensive plan including:
**Step 5: Create Status File**
- Create `project-workflow-status-YYYY-MM-DD.md`
- Create `bmm-workflow-status.md`
- Document complete planned workflow in "Planned Workflow Journey" table
- Set current step: "Workflow Definition Phase"
- Set next step: First item from planned workflow
@@ -95,7 +95,7 @@ The workflow builds a comprehensive plan including:
**The workflow will:**
1. Find most recent `project-workflow-status-YYYY-MM-DD.md` file
1. Find most recent `bmm-workflow-status.md` file
2. Read and parse current state:
- Current phase and progress %
- Project level and type
@@ -123,12 +123,12 @@ If in Implementation phase, shows:
**Search Pattern:**
```
{output_folder}/project-workflow-status*.md
{output_folder}/bmm-workflow-status.md
```
**Versioning:**
- Files are named: `project-workflow-status-YYYY-MM-DD.md`
- Files are named: `bmm-workflow-status.md`
- Workflow finds most recent by date
- Old files can be archived
@@ -286,7 +286,7 @@ Next Step: plan-project (PM agent)
Ready to create your workflow status file?
This will create: project-workflow-status-2025-10-12.md
This will create: bmm-workflow-status.md
The status file will document:
- Your complete planned workflow (phases and steps)
@@ -297,7 +297,7 @@ Create status file? (y/n): y
✅ Status file created!
File: project-workflow-status-2025-10-12.md
File: bmm-workflow-status.md
To proceed with your first step:

14
src/modules/bmm/workflows/1-analysis/workflow-status/instructions.md
View File

@@ -9,11 +9,11 @@
<step n="1" goal="Check for existing workflow status file">
<action>Search {output_folder}/ for files matching pattern: project-workflow-status\*.md</action>
<action>Search {output_folder}/ for files matching pattern: bmm-workflow-status\*.md</action>
<action>Use glob or list_files to find all matching files</action>
<check if="files found">
<action>Find the most recent file (by date in filename: project-workflow-status-YYYY-MM-DD.md)</action>
<action>Find the most recent file (by date in filename: bmm-workflow-status.md)</action>
<action>Set status_file_found = true</action>
<action>Set status_file_path = most recent file path</action>
<action>Go to Step 2 (Read existing status)</action>
@@ -519,7 +519,7 @@ Based on your responses, here's your complete workflow journey:
<ask>**Ready to create your workflow status file?**
This will create: `project-workflow-status-{{today_date}}.md`
This will create: `bmm-workflow-status.md`
The status file will document:
@@ -530,7 +530,7 @@ The status file will document:
Create status file? (y/n)</ask>
<check if='confirm == "y"'>
<action>Create project-workflow-status-{{today}}.md file</action>
<action>Create bmm-workflow-status.md file</action>
<action>Set current_phase = "Workflow Definition"</action>
<action>Set next_action = planned_workflow[0].step</action>
<action>Set next_agent = planned_workflow[0].agent</action>
@@ -538,7 +538,7 @@ Create status file? (y/n)</ask>
<output>**✅ Status file created!**
File: `project-workflow-status-{{today}}.md`
File: `bmm-workflow-status.md`
**To proceed with your first step:**
@@ -587,8 +587,8 @@ Your choice (1-5):</ask>
This will:
- Archive current status: `project-workflow-status-{{old_date}}.md` → `archive/`
- Create new status: `project-workflow-status-{{today}}.md`
- Archive current status: `bmm-workflow-status.md` → `archive/`
- Create new status: `bmm-workflow-status.md`
- Start fresh assessment
Continue? (y/n)</ask>

2
src/modules/bmm/workflows/1-analysis/workflow-status/workflow.yaml
View File

@@ -16,7 +16,7 @@ instructions: "{installed_path}/instructions.md"
# Variables and inputs
variables:
status_file_pattern: "project-workflow-status*.md" # Searches for versioned files
status_file_pattern: "bmm-workflow-status.md" # Searches for versioned files
check_existing_status: true # Always check for existing status file
display_menu: true # Display agent menu after status check
suggest_next_action: true # Suggest next action based on current state

10
src/modules/bmm/workflows/2-plan/README.md
View File

@@ -8,7 +8,7 @@ This scale-adaptive workflow represents the cornerstone of BMM v6's intelligent
The workflow's routing intelligence analyzes project characteristics through multi-dimensional assessment: project type (game, web, mobile, backend), context (greenfield vs. brownfield), scope indicators, and complexity signals. Based on this analysis, it classifies projects into five levels with distinct artifact requirements. Level 0 produces only tech specs for single atomic changes. Levels 1-2 generate focused PRDs with embedded tech specs. Levels 3-4 create comprehensive PRDs with separate epics that hand off to the architect-driven solutioning workflow. This classification isn't merely about document generation—it fundamentally changes how requirements are structured, validated, and communicated to downstream consumers.
Critical to v6's flow improvement is this workflow's integration with the project-workflow-status.md tracking document, which maintains project state across sessions, tracks which agents participate in each phase, and provides continuity for multi-session planning efforts. The workflow can resume from any point, intelligently detecting existing artifacts and determining next steps without redundant work. For game projects, it routes to specialized GDD generation with genre-specific templates. For UX-heavy projects, it can generate standalone UX specifications or AI frontend prompts from existing specs.
Critical to v6's flow improvement is this workflow's integration with the bmm-workflow-status.md tracking document, which maintains project state across sessions, tracks which agents participate in each phase, and provides continuity for multi-session planning efforts. The workflow can resume from any point, intelligently detecting existing artifacts and determining next steps without redundant work. For game projects, it routes to specialized GDD generation with genre-specific templates. For UX-heavy projects, it can generate standalone UX specifications or AI frontend prompts from existing specs.
## Key Features
@@ -123,7 +123,7 @@ plan-project/
### Generated Files
- **Primary output**: PRD.md (except Level 0), tech-spec.md, project-workflow-status.md
- **Primary output**: PRD.md (except Level 0), tech-spec.md, bmm-workflow-status.md
- **Supporting files**: epics.md (Level 3-4), PRD-validation-report.md (if validation run)
### Output Structure by Level
@@ -185,7 +185,7 @@ plan-project/
**Issue**: Workflow creates wrong level of documentation
- **Solution**: Review project assessment and restart with correct scope classification
- **Check**: Verify the project-workflow-status.md reflects actual project complexity
- **Check**: Verify the bmm-workflow-status.md reflects actual project complexity
**Issue**: Missing input documents cause incomplete planning
@@ -194,7 +194,7 @@ plan-project/
**Issue**: Continuation from previous session fails
- **Solution**: Check for existing project-workflow-status.md and ensure output folder is correct
- **Solution**: Check for existing bmm-workflow-status.md and ensure output folder is correct
- **Check**: Verify previous session completed at a valid checkpoint
## Customization
@@ -220,7 +220,7 @@ For issues or questions:
- Review the workflow creation guide at `/bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
- Validate output using `checklist.md`
- Consult project assessment in `project-workflow-status.md`
- Consult project assessment in `bmm-workflow-status.md`
- Check continuation status in existing output documents
---

4
src/modules/bmm/workflows/2-plan/gdd/instructions-gdd.md
View File

@@ -12,7 +12,7 @@
<step n="1" goal="Load context and determine game type">
<action>Load project-workflow-status.md</action>
<action>Load bmm-workflow-status.md</action>
<action>Confirm project_type == "game"</action>
<check if="continuation_mode == true">
@@ -439,7 +439,7 @@ Since this is a Level {{project_level}} game project, you need solutioning for p
- [ ] **Run solutioning workflow** (REQUIRED)
- Command: `workflow solution-architecture`
- Input: GDD.md, project-workflow-status.md
- Input: GDD.md, bmm-workflow-status.md
- Output: solution-architecture.md with engine/platform specifics
- Note: Registry.csv will provide engine-specific guidance

8
src/modules/bmm/workflows/2-plan/instructions-router.md
View File

@@ -3,13 +3,13 @@
<workflow>
<critical>This workflow requires a workflow status file to exist</critical>
<critical>ALWAYS check for existing project-workflow-status.md first</critical>
<critical>ALWAYS check for existing bmm-workflow-status.md first</critical>
<critical>If no status file exists, direct user to run workflow-status first</critical>
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
<step n="1" goal="Check for existing workflow status file - REQUIRED">
<action>Check if any project-workflow-status\*.md files exist in {output_folder}/</action>
<action>Check if any bmm-workflow-status\*.md files exist in {output_folder}/</action>
<check if="not exists">
<output>**⚠️ No Workflow Status File Found**
@@ -35,7 +35,7 @@ Or tell me: "run workflow-status"
</check>
<check if="exists">
<action>Find the most recent project-workflow-status-YYYY-MM-DD.md file</action>
<action>Find the most recent bmm-workflow-status.md file</action>
<action>Load the status file</action>
<action>Extract key information:</action>
@@ -95,7 +95,7 @@ After updating your plan, return here if needed.
- Level 3-4: Check for PRD.md, epics.md
<check if="outputs exist">
<ask>Found existing workflow status file: project-workflow-status-{{file_date}}.md (Level {{project_level}})
<ask>Found existing workflow status file: bmm-workflow-status.md (Level {{project_level}})
**Existing documents detected:**
{{list_existing_docs}}

2
src/modules/bmm/workflows/2-plan/prd/instructions-lg.md
View File

@@ -12,7 +12,7 @@
<step n="1" goal="Load context and handle continuation">
<action>Load project-workflow-status.md</action>
<action>Load bmm-workflow-status.md</action>
<action>Confirm Level 3-4 - Full product or platform</action>
<check if="continuation_mode == true">

2
src/modules/bmm/workflows/2-plan/prd/instructions-med.md
View File

@@ -12,7 +12,7 @@
<step n="1" goal="Load context and handle continuation">
<action>Load project-workflow-status.md</action>
<action>Load bmm-workflow-status.md</action>
<action>Confirm Level 1-2 - Feature or small system</action>
<check if="continuation_mode == true">

6
src/modules/bmm/workflows/2-plan/prd/workflow.yaml
View File

@@ -19,11 +19,11 @@ instructions_lg: "{installed_path}/instructions-lg.md" # Level 3-4
# Templates
prd_template: "{installed_path}/prd-template.md"
status_template: "{project-root}/bmad/bmm/workflows/_shared/project-workflow-status-template.md"
status_template: "{project-root}/bmad/bmm/workflows/_shared/bmm-workflow-status-template.md"
epics_template: "{installed_path}/epics-template.md"
# Output configuration
status_file: "{output_folder}/project-workflow-status.md"
status_file: "{output_folder}/bmm-workflow-status.md"
default_output_file: "{output_folder}/PRD.md"
epics_output_file: "{output_folder}/epics.md"
validation_output_file: "{output_folder}/PRD-validation-report.md"
@@ -74,7 +74,7 @@ web_bundle:
- "bmad/bmm/workflows/2-plan/prd/instructions-med.md"
- "bmad/bmm/workflows/2-plan/prd/instructions-lg.md"
- "bmad/bmm/workflows/2-plan/prd/prd-template.md"
- "bmad/bmm/workflows/_shared/project-workflow-status-template.md"
- "bmad/bmm/workflows/_shared/bmm-workflow-status-template.md"
- "bmad/bmm/workflows/2-plan/prd/epics-template.md"
# Scale parameters - adaptive by project level
scale_parameters:

10
src/modules/bmm/workflows/2-plan/tech-spec/instructions-level0-story.md
View File

@@ -10,7 +10,7 @@
<step n="1" goal="Load tech spec and extract the change">
<action>Read the completed tech-spec.md file from {output_folder}/tech-spec.md</action>
<action>Load project-workflow-status.md from {output_folder}/project-workflow-status.md</action>
<action>Load bmm-workflow-status.md from {output_folder}/bmm-workflow-status.md</action>
<action>Extract dev_story_location from config (where stories are stored)</action>
<action>Extract the problem statement from "Technical Approach" section</action>
<action>Extract the scope from "Source Tree Structure" section</action>
@@ -98,9 +98,9 @@
</step>
<step n="4" goal="Update project-workflow-status and initialize Phase 4">
<step n="4" goal="Update bmm-workflow-status and initialize Phase 4">
<action>Open {output_folder}/project-workflow-status.md</action>
<action>Open {output_folder}/bmm-workflow-status.md</action>
<action>Update "Workflow Status Tracker" section:</action>
@@ -173,7 +173,7 @@ Initialize empty table:
- **{{date}}**: Level 0 tech-spec and story generation completed. Skipping Phase 3 (solutioning) - moving directly to Phase 4 (implementation). Single story (story-{slug}.md) drafted and ready for review.
```
<action>Save project-workflow-status.md</action>
<action>Save bmm-workflow-status.md</action>
</step>
@@ -206,7 +206,7 @@ Initialize empty table:
**Progress Tracking:**
- All decisions logged in: `project-workflow-status.md`
- All decisions logged in: `bmm-workflow-status.md`
- Next action clearly identified
<ask>Ready to proceed? Choose your path:

10
src/modules/bmm/workflows/2-plan/tech-spec/instructions-level1-stories.md
View File

@@ -11,7 +11,7 @@
<step n="1" goal="Load tech spec and extract implementation tasks">
<action>Read the completed tech-spec.md file from {output_folder}/tech-spec.md</action>
<action>Load project-workflow-status.md from {output_folder}/project-workflow-status.md</action>
<action>Load bmm-workflow-status.md from {output_folder}/bmm-workflow-status.md</action>
<action>Extract dev_story_location from config (where stories are stored)</action>
<action>Identify all implementation tasks from the "Implementation Guide" section</action>
<action>Identify the overall feature goal from "Technical Approach" section</action>
@@ -228,9 +228,9 @@ Epic: Icon Reliability
</step>
<step n="6" goal="Update project-workflow-status and populate backlog for Phase 4">
<step n="6" goal="Update bmm-workflow-status and populate backlog for Phase 4">
<action>Open {output_folder}/project-workflow-status.md</action>
<action>Open {output_folder}/bmm-workflow-status.md</action>
<action>Update "Workflow Status Tracker" section:</action>
@@ -314,7 +314,7 @@ Initialize empty table:
- **{{date}}**: Level 1 tech-spec and epic/stories generation completed. {{story_count}} stories created. Skipping Phase 3 (solutioning) - moving directly to Phase 4 (implementation). Story backlog populated. First story (story-{epic_slug}-1.md) drafted and ready for review.
```
<action>Save project-workflow-status.md</action>
<action>Save bmm-workflow-status.md</action>
</step>
@@ -366,7 +366,7 @@ d. Run dev-story workflow to implement story 1
**Progress Tracking:**
- All decisions logged in: `project-workflow-status.md`
- All decisions logged in: `bmm-workflow-status.md`
- Next action clearly identified
<ask>Ready to proceed? Choose your path:

10
src/modules/bmm/workflows/2-plan/tech-spec/instructions-sm.md
View File

@@ -11,7 +11,7 @@
<step n="1" goal="Confirm project scope and update tracking">
<action>Load project-workflow-status.md from {output_folder}/project-workflow-status.md</action>
<action>Load bmm-workflow-status.md from {output_folder}/bmm-workflow-status.md</action>
<action>Update Workflow Status Tracker:</action>
<check if="project_level == 0">
@@ -21,7 +21,7 @@
<action>Set current_workflow = "tech-spec (Level 1 - generating tech spec)"</action>
</check>
<action>Set progress_percentage = 20%</action>
<action>Save project-workflow-status.md</action>
<action>Save bmm-workflow-status.md</action>
<check if="project_level == 0">
<action>Confirm Level 0 - Single atomic change</action>
@@ -40,9 +40,9 @@
<critical>Generate tech-spec.md - this is the TECHNICAL SOURCE OF TRUTH</critical>
<critical>ALL TECHNICAL DECISIONS MUST BE DEFINITIVE - NO AMBIGUITY ALLOWED</critical>
<action>Update progress in project-workflow-status.md:</action>
<action>Update progress in bmm-workflow-status.md:</action>
<action>Set progress_percentage = 40%</action>
<action>Save project-workflow-status.md</action>
<action>Save bmm-workflow-status.md</action>
<action>Initialize tech-spec.md using tech_spec_template from workflow.yaml</action>
@@ -108,7 +108,7 @@ Run cohesion validation? (y/n)</ask>
<step n="4" goal="Generate user stories based on project level">
<action>Load project-workflow-status.md to determine project_level</action>
<action>Load bmm-workflow-status.md to determine project_level</action>
<check if="project_level == 0">
<action>Invoke instructions-level0-story.md to generate single user story</action>

2
src/modules/bmm/workflows/2-plan/ux/instructions-ux.md
View File

@@ -38,7 +38,7 @@ If no: We'll gather basic requirements to create the UX spec
- epics.md or epic-stories.md (helps understand feature grouping)
- tech-spec.md (understand technical constraints)
- solution-architecture.md (if Level 3-4 project)
- project-workflow-status.md (understand project level and scope)
- bmm-workflow-status.md (understand project level and scope)
</check>

6
src/modules/bmm/workflows/2-plan/workflow.yaml
View File

@@ -27,7 +27,7 @@ workflow_ux: "{installed_path}/ux/workflow.yaml"
# Templates - Load these only when the instructions request loading them
prd_template: "{installed_path}/prd/prd-template.md"
status_template: "{project-root}/bmad/bmm/workflows/_shared/project-workflow-status-template.md"
status_template: "{project-root}/bmad/bmm/workflows/_shared/bmm-workflow-status-template.md"
epics_template: "{installed_path}/prd/epics-template.md"
tech_spec_template: "{installed_path}/tech-spec/tech-spec-template.md"
ux_spec_template: "{installed_path}/ux/ux-spec-template.md"
@@ -39,7 +39,7 @@ narrative_template: "{installed_path}/narrative/narrative-template.md"
instructions: "{installed_path}/instructions-router.md"
# Output configuration
status_file: "{output_folder}/project-workflow-status.md"
status_file: "{output_folder}/bmm-workflow-status.md"
default_output_file: "{output_folder}/PRD.md"
gdd_output_file: "{output_folder}/GDD.md"
epics_output_file: "{output_folder}/epics.md"
@@ -83,7 +83,7 @@ web_bundle:
instructions_narrative: "bmad/bmm/workflows/2-plan/narrative/instructions-narrative.md"
# Templates - Load these only when the instructions request loading them
prd_template: "{installed_path}/prd/prd-template.md"
status_template: "bmad/bmm/workflows/_shared/project-workflow-status-template.md"
status_template: "bmad/bmm/workflows/_shared/bmm-workflow-status-template.md"
epics_template: "{installed_path}/prd/epics-template.md"
tech_spec_template: "{installed_path}/tech-spec/tech-spec-template.md"
ux_spec_template: "{installed_path}/ux/ux-spec-template.md"

16
src/modules/bmm/workflows/3-solutioning/README.md
View File

@@ -24,12 +24,12 @@ This workflow generates comprehensive, scale-adaptive solution architecture docu
Run this workflow **AFTER** completing:
| Prerequisite | Required For | Location |
| -------------------------- | ----------------------------- | ---------------------------------- |
| **plan-project workflow** | All projects | `/docs/project-workflow-status.md` |
| **PRD with epics/stories** | Level 1+ projects | `/docs/PRD.md` |
| **GDD (for games)** | Game projects | `/docs/GDD.md` or `/docs/PRD.md` |
| **UX Specification** | UI projects (web/mobile/game) | `/docs/ux-specification.md` |
| Prerequisite | Required For | Location |
| -------------------------- | ----------------------------- | -------------------------------- |
| **plan-project workflow** | All projects | `/docs/bmm-workflow-status.md` |
| **PRD with epics/stories** | Level 1+ projects | `/docs/PRD.md` |
| **GDD (for games)** | Game projects | `/docs/GDD.md` or `/docs/PRD.md` |
| **UX Specification** | UI projects (web/mobile/game) | `/docs/ux-specification.md` |
---
@@ -41,7 +41,7 @@ workflow solution-architecture
**The workflow will:**
1. Load `project-workflow-status.md` (from plan-project)
1. Load `bmm-workflow-status.md` (from plan-project)
2. Check prerequisites (PRD/GDD, UX spec if needed)
3. Read requirements (PRD for apps, GDD for games)
4. Ask architecture pattern questions
@@ -110,7 +110,7 @@ Each row maps to:
### Step 0: Prerequisites and Scale Check
Load `project-workflow-status.md`:
Load `bmm-workflow-status.md`:
- Extract: `project_level` (0-4), `project_type` (web/game/mobile/etc.), `field_type` (greenfield/brownfield)
- Validate: PRD exists, UX spec exists (if UI project)

2
src/modules/bmm/workflows/3-solutioning/checklist.md
View File

@@ -86,7 +86,7 @@ Use this checklist during workflow execution and review.
- [ ] Tech-spec generated for each epic
- [ ] Saved as tech-spec-epic-{{N}}.md
- [ ] project-workflow-status.md updated
- [ ] bmm-workflow-status.md updated
### Step 10: Polyrepo Strategy (Optional)

14
src/modules/bmm/workflows/3-solutioning/instructions.md
View File

@@ -7,8 +7,8 @@ This workflow generates scale-adaptive solution architecture documentation that
<step n="0" goal="Load project analysis, validate prerequisites, and scale assessment">
<action>
1. Search {output_folder}/ for files matching pattern: project-workflow-status*.md
Find the most recent file (by date in filename: project-workflow-status-YYYY-MM-DD.md)
1. Search {output_folder}/ for files matching pattern: bmm-workflow-status.md
Find the most recent file (by date in filename: bmm-workflow-status.md)
2. Check if status file exists:
<check if="exists">
@@ -624,7 +624,7 @@ For each epic in PRD:
<template-output>tech_specs</template-output>
<action>
Update project-workflow-status.md workflow status:
Update bmm-workflow-status.md workflow status:
- [x] Solution architecture generated
- [x] Cohesion check passed
- [x] Tech specs generated for all epics
@@ -697,9 +697,9 @@ For each story in sequence:
- story_title: Story title from PRD/epics
- story_file: "story-{{epic_num}}.{{story_num}}.md"
4. Update project-workflow-status.md with backlog population:
4. Update bmm-workflow-status.md with backlog population:
Open {output_folder}/project-workflow-status.md
Open {output_folder}/bmm-workflow-status.md
In "### Implementation Progress (Phase 4 Only)" section:
@@ -761,7 +761,7 @@ Add entries for all generated tech specs
8. Add to Decision Log:
- **{{date}}**: Phase 3 (Solutioning) complete. Architecture and tech specs generated. Populated story backlog with {{total_story_count}} stories. Ready for Phase 4 (Implementation). Next: SM drafts story 1.1.
9. Save project-workflow-status.md
9. Save bmm-workflow-status.md
</action>
<ask>
@@ -792,7 +792,7 @@ Would you like to proceed with story drafting now? (y/n)
<step n="12" goal="Update status file on completion">
<action>
Search {output_folder}/ for files matching pattern: project-workflow-status*.md
Search {output_folder}/ for files matching pattern: bmm-workflow-status.md
Find the most recent file (by date in filename)
</action>

6
src/modules/bmm/workflows/3-solutioning/tech-spec/instructions.md
View File

@@ -8,8 +8,8 @@
<workflow>
<step n="1" goal="Check and load workflow status file">
<action>Search {output_folder}/ for files matching pattern: project-workflow-status*.md</action>
<action>Find the most recent file (by date in filename: project-workflow-status-YYYY-MM-DD.md)</action>
<action>Search {output_folder}/ for files matching pattern: bmm-workflow-status.md</action>
<action>Find the most recent file (by date in filename: bmm-workflow-status.md)</action>
<check if="exists">
<action>Load the status file</action>
@@ -125,7 +125,7 @@ What would you like to do?</ask>
</step>
<step n="10" goal="Update status file on completion">
<action>Search {output_folder}/ for files matching pattern: project-workflow-status*.md</action>
<action>Search {output_folder}/ for files matching pattern: bmm-workflow-status.md</action>
<action>Find the most recent file (by date in filename)</action>
<check if="status file exists">

4
src/modules/bmm/workflows/3-solutioning/workflow.yaml
View File

@@ -16,8 +16,8 @@ inputs:
default: "{output_folder}/PRD.md"
required: true
- name: project_workflow_analysis_path
description: "Path to project-workflow-status.md from plan-project workflow"
default: "{output_folder}/project-workflow-status.md"
description: "Path to bmm-workflow-status.md from plan-project workflow"
default: "{output_folder}/bmm-workflow-status.md"
required: true
- name: project_level
description: "Project level (0-4) from analysis file"

4
src/modules/bmm/workflows/4-implementation/create-story/instructions.md
View File

@@ -28,7 +28,7 @@
</step>
<step n="2.5" goal="Check status file TODO section for story to draft">
<action>Read {output_folder}/project-workflow-status.md (if exists)</action>
<action>Read {output_folder}/bmm-workflow-status.md (if exists)</action>
<action>Navigate to "### Implementation Progress (Phase 4 Only)" section</action>
<action>Find "#### TODO (Needs Drafting)" section</action>
@@ -121,7 +121,7 @@
</step>
<step n="9" goal="Update status file on completion">
<action>Search {output_folder}/ for files matching pattern: project-workflow-status*.md</action>
<action>Search {output_folder}/ for files matching pattern: bmm-workflow-status.md</action>
<action>Find the most recent file (by date in filename)</action>
<check if="status file exists">

4
src/modules/bmm/workflows/4-implementation/dev-story/instructions.md
View File

@@ -12,7 +12,7 @@
<workflow>
<step n="1" goal="Load story from status file IN PROGRESS section">
<action>Read {output_folder}/project-workflow-status.md (if exists)</action>
<action>Read {output_folder}/bmm-workflow-status.md (if exists)</action>
<action>Navigate to "### Implementation Progress (Phase 4 Only)" section</action>
<action>Find "#### IN PROGRESS (Approved for Development)" section</action>
@@ -109,7 +109,7 @@
</step>
<step n="8" goal="Update status file on completion">
<action>Search {output_folder}/ for files matching pattern: project-workflow-status*.md</action>
<action>Search {output_folder}/ for files matching pattern: bmm-workflow-status.md</action>
<action>Find the most recent file (by date in filename)</action>
<check if="status file exists">

6
src/modules/bmm/workflows/4-implementation/retrospective/instructions.md
View File

@@ -16,8 +16,8 @@ FACILITATION NOTES:
<workflow>
<step n="1" goal="Check and load workflow status file">
<action>Search {output_folder}/ for files matching pattern: project-workflow-status*.md</action>
<action>Find the most recent file (by date in filename: project-workflow-status-YYYY-MM-DD.md)</action>
<action>Search {output_folder}/ for files matching pattern: bmm-workflow-status.md</action>
<action>Find the most recent file (by date in filename: bmm-workflow-status.md)</action>
<check if="exists">
<action>Load the status file</action>
@@ -399,7 +399,7 @@ See you at sprint planning once prep work is done!"
</step>
<step n="9" goal="Update status file on completion">
<action>Search {output_folder}/ for files matching pattern: project-workflow-status*.md</action>
<action>Search {output_folder}/ for files matching pattern: bmm-workflow-status.md</action>
<action>Find the most recent file (by date in filename)</action>
<check if="status file exists">

6
src/modules/bmm/workflows/4-implementation/review-story/instructions.md
View File

@@ -11,8 +11,8 @@
<workflow>
<step n="1" goal="Check and load workflow status file">
<action>Search {output_folder}/ for files matching pattern: project-workflow-status*.md</action>
<action>Find the most recent file (by date in filename: project-workflow-status-YYYY-MM-DD.md)</action>
<action>Search {output_folder}/ for files matching pattern: bmm-workflow-status.md</action>
<action>Find the most recent file (by date in filename: bmm-workflow-status.md)</action>
<check if="exists">
<action>Load the status file</action>
@@ -200,7 +200,7 @@ What would you like to do?</ask>
</step>
<step n="10" goal="Update status file on completion">
<action>Search {output_folder}/ for files matching pattern: project-workflow-status*.md</action>
<action>Search {output_folder}/ for files matching pattern: bmm-workflow-status.md</action>
<action>Find the most recent file (by date in filename)</action>
<check if="status file exists">

6
src/modules/bmm/workflows/4-implementation/story-approved/instructions.md
View File

@@ -8,7 +8,7 @@
<step n="1" goal="Read status file and identify the IN PROGRESS story">
<action>Read {output_folder}/project-workflow-status.md</action>
<action>Read {output_folder}/bmm-workflow-status.md</action>
<action>Navigate to "### Implementation Progress (Phase 4 Only)" section</action>
<action>Find "#### IN PROGRESS (Approved for Development)" section</action>
@@ -62,7 +62,7 @@ Find "## Dev Agent Record" section and add:
<step n="3" goal="Move story IN PROGRESS → DONE, advance the queue">
<action>Open {output_folder}/project-workflow-status.md</action>
<action>Open {output_folder}/bmm-workflow-status.md</action>
<action>Update "#### DONE (Completed Stories)" section:</action>
@@ -207,7 +207,7 @@ If BACKLOG had 1 story and is now empty:
```
</check>
<action>Save project-workflow-status.md</action>
<action>Save bmm-workflow-status.md</action>
</step>

2
src/modules/bmm/workflows/4-implementation/story-approved/workflow.yaml
View File

@@ -17,7 +17,7 @@ instructions: "{installed_path}/instructions.md"
# Variables and inputs
variables:
story_dir: "{config_source}:dev_story_location" # Directory where stories are stored
status_file: "{output_folder}/project-workflow-status.md" # Status file to update
status_file: "{output_folder}/bmm-workflow-status.md" # Status file to update
auto_update_status: true # Always update status file
# Output configuration - no output file, just status updates

6
src/modules/bmm/workflows/4-implementation/story-context/instructions.md
View File

@@ -8,8 +8,8 @@
<workflow>
<step n="1" goal="Check and load workflow status file">
<action>Search {output_folder}/ for files matching pattern: project-workflow-status*.md</action>
<action>Find the most recent file (by date in filename: project-workflow-status-YYYY-MM-DD.md)</action>
<action>Search {output_folder}/ for files matching pattern: bmm-workflow-status.md</action>
<action>Find the most recent file (by date in filename: bmm-workflow-status.md)</action>
<check if="exists">
<action>Load the status file</action>
@@ -146,7 +146,7 @@ What would you like to do?</ask>
</step>
<step n="9" goal="Update status file on completion">
<action>Search {output_folder}/ for files matching pattern: project-workflow-status*.md</action>
<action>Search {output_folder}/ for files matching pattern: bmm-workflow-status.md</action>
<action>Find the most recent file (by date in filename)</action>
<check if="status file exists">

6
src/modules/bmm/workflows/4-implementation/story-ready/instructions.md
View File

@@ -8,7 +8,7 @@
<step n="1" goal="Read status file and identify the TODO story">
<action>Read {output_folder}/project-workflow-status.md</action>
<action>Read {output_folder}/bmm-workflow-status.md</action>
<action>Navigate to "### Implementation Progress (Phase 4 Only)" section</action>
<action>Find "#### TODO (Needs Drafting)" section</action>
@@ -39,7 +39,7 @@
<step n="3" goal="Move story from TODO → IN PROGRESS in status file">
<action>Open {output_folder}/project-workflow-status.md</action>
<action>Open {output_folder}/bmm-workflow-status.md</action>
<action>Update "#### TODO (Needs Drafting)" section:</action>
@@ -120,7 +120,7 @@ If BACKLOG had 1 story and is now empty:
**Agent to load:** bmad/bmm/agents/sm.md (for story-context) OR bmad/bmm/agents/dev.md (for dev-story)
```
<action>Save project-workflow-status.md</action>
<action>Save bmm-workflow-status.md</action>
</step>

2
src/modules/bmm/workflows/4-implementation/story-ready/workflow.yaml
View File

@@ -17,7 +17,7 @@ instructions: "{installed_path}/instructions.md"
# Variables and inputs
variables:
story_dir: "{config_source}:dev_story_location" # Directory where stories are stored
status_file: "{output_folder}/project-workflow-status.md" # Status file to update
status_file: "{output_folder}/bmm-workflow-status.md" # Status file to update
auto_update_status: true # Always update status file
# Output configuration - no output file, just status updates

8
src/modules/bmm/workflows/README.md
View File

@@ -153,7 +153,7 @@ plan-project
│ ├─→ Level 0 → tech-spec workflow
│ ├─→ Level 1-2 → PRD + embedded tech-spec
│ └─→ Level 3-4 → PRD + epics → Solutioning
└─→ Generate project-workflow-status.md (tracking doc)
└─→ Generate bmm-workflow-status.md (tracking doc)
```
### Key Outputs
@@ -165,7 +165,7 @@ plan-project
- **story-{slug}.md**: Single user story (Level 0)
- **story-{slug}-1.md, story-{slug}-2.md, story-{slug}-3.md**: User stories (Level 1)
- **GDD.md**: Game Design Document (game projects)
- **project-workflow-status-YYYY-MM-DD.md**: Versioned workflow state tracking with story backlog
- **bmm-workflow-status.md**: Versioned workflow state tracking with story backlog
## Phase 3: Solutioning (Levels 3-4 Only)
@@ -198,7 +198,7 @@ The core development cycle that transforms requirements into working software.
### The Story State Machine
Phase 4 uses a 4-state lifecycle to manage story progression, tracked in `project-workflow-status.md`:
Phase 4 uses a 4-state lifecycle to manage story progression, tracked in `bmm-workflow-status.md`:
```
BACKLOG → TODO → IN PROGRESS → DONE
@@ -364,7 +364,7 @@ plan-project (Phase 2)
### Tracking Documents
- **project-workflow-status-YYYY-MM-DD.md**: Versioned workflow state tracking with 4-section story backlog
- **bmm-workflow-status.md**: Versioned workflow state tracking with 4-section story backlog
- **BACKLOG**: Ordered list of stories to be drafted
- **TODO**: Single story ready for drafting (or drafted, awaiting approval)
- **IN PROGRESS**: Single story approved for development

4
src/modules/bmm/workflows/_shared/project-workflow-status-template.md → src/modules/bmm/workflows/_shared/bmm-workflow-status-template.md
View File

@@ -3,7 +3,7 @@
**Project:** {{project_name}}
**Created:** {{start_date}}
**Last Updated:** {{last_updated}}
**Status File:** `project-workflow-status-{{start_date}}.md`
**Status File:** `bmm-workflow-status.md`
---
@@ -333,6 +333,6 @@ BACKLOG → TODO → IN PROGRESS → DONE
_This file serves as the **single source of truth** for project workflow status, epic/story tracking, and next actions. All BMM agents and workflows reference this document for coordination._
_Template Location: `bmad/bmm/workflows/_shared/project-workflow-status-template.md`_
_Template Location: `bmad/bmm/workflows/_shared/bmm-workflow-status-template.md`_
_File Created: {{start_date}}_