central source of trust for workflow status, current, and next story or epic
This commit is contained in:
Brian Madison
@@ -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-analysis.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 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.
|
||||
|
||||
## Key Features
|
||||
|
||||
@@ -104,7 +104,7 @@ plan-project/
|
||||
|
||||
### Generated Files
|
||||
|
||||
- **Primary output**: PRD.md (except Level 0), tech-spec.md, project-workflow-analysis.md
|
||||
- **Primary output**: PRD.md (except Level 0), tech-spec.md, project-workflow-status.md
|
||||
- **Supporting files**: epics.md (Level 3-4), PRD-validation-report.md (if validation run)
|
||||
|
||||
### Output Structure by Level
|
||||
@@ -166,7 +166,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-analysis.md reflects actual project complexity
|
||||
- **Check**: Verify the project-workflow-status.md reflects actual project complexity
|
||||
|
||||
**Issue**: Missing input documents cause incomplete planning
|
||||
|
||||
@@ -175,7 +175,7 @@ plan-project/
|
||||
|
||||
**Issue**: Continuation from previous session fails
|
||||
|
||||
- **Solution**: Check for existing project-workflow-analysis.md and ensure output folder is correct
|
||||
- **Solution**: Check for existing project-workflow-status.md and ensure output folder is correct
|
||||
- **Check**: Verify previous session completed at a valid checkpoint
|
||||
|
||||
## Customization
|
||||
@@ -201,7 +201,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-analysis.md`
|
||||
- Consult project assessment in `project-workflow-status.md`
|
||||
- Check continuation status in existing output documents
|
||||
|
||||
---
|
||||
|
||||
@@ -12,7 +12,7 @@
|
||||
|
||||
<step n="1" goal="Load context and determine game type">
|
||||
|
||||
<action>Load project-workflow-analysis.md</action>
|
||||
<action>Load project-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-analysis.md
|
||||
- Input: GDD.md, project-workflow-status.md
|
||||
- Output: solution-architecture.md with engine/platform specifics
|
||||
- Note: Registry.csv will provide engine-specific guidance
|
||||
|
||||
|
||||
@@ -3,36 +3,60 @@
|
||||
<workflow>
|
||||
|
||||
<critical>This is the INITIAL ASSESSMENT phase - determines which instruction set to load</critical>
|
||||
<critical>ALWAYS check for existing project-workflow-analysis.md first</critical>
|
||||
<critical>ALWAYS check for existing project-workflow-status.md 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 analysis or perform new assessment">
|
||||
<step n="1" goal="Check for existing workflow status or create new versioned file">
|
||||
|
||||
<action>Check if {output_folder}/project-workflow-analysis.md exists</action>
|
||||
<action>Check if any project-workflow-status\*.md files exist in {output_folder}/</action>
|
||||
|
||||
<check if="exists">
|
||||
<action>Load the analysis file</action>
|
||||
<action>Check for existing workflow outputs based on level in analysis:</action>
|
||||
<action>Find the most recent project-workflow-status-YYYY-MM-DD.md file</action>
|
||||
<action>Load the status file</action>
|
||||
<action>Check for existing workflow outputs based on level in status file:</action>
|
||||
|
||||
- Level 0: Check for tech-spec.md
|
||||
- Level 1-2: Check for PRD.md, epic-stories.md, tech-spec.md
|
||||
- Level 3-4: Check for PRD.md, epics.md
|
||||
|
||||
<ask>Previous analysis found (Level {{project_level}}).
|
||||
<ask>Found existing workflow status file: project-workflow-status-{{file_date}}.md (Level {{project_level}})
|
||||
|
||||
**Existing documents detected:**
|
||||
{{list_existing_docs}}
|
||||
|
||||
Options:
|
||||
|
||||
1. Continue where left off with existing documents
|
||||
2. Start fresh assessment (will archive existing work)
|
||||
3. Review and modify previous analysis
|
||||
1. Continue with this workflow (will update existing status file)
|
||||
2. Start new workflow (will create new dated status file: project-workflow-status-{{today}}.md)
|
||||
3. Review and modify previous status
|
||||
4. I'm working on something else (ignore this file)
|
||||
|
||||
</ask>
|
||||
|
||||
<check if='option == "1"'>
|
||||
<action>Set status_file_path = existing file path</action>
|
||||
<action>Set continuation_mode = true</action>
|
||||
</check>
|
||||
|
||||
<check if='option == "2"'>
|
||||
<action>Set status_file_path = "{output_folder}/project-workflow-status-{{today}}.md"</action>
|
||||
<action>Archive old status file to: "{output_folder}/archive/project-workflow-status-{{old_date}}.md"</action>
|
||||
<action>Set continuation_mode = false</action>
|
||||
<action>Proceed to new assessment</action>
|
||||
</check>
|
||||
|
||||
<check if='option == "4"'>
|
||||
<action>Do not use status file for this session</action>
|
||||
<action>Proceed with user's requested workflow</action>
|
||||
<action>Exit router (user is not using BMM planning workflow)</action>
|
||||
</check>
|
||||
|
||||
</check>
|
||||
|
||||
<check if="not exists or starting fresh">
|
||||
<check if="not exists">
|
||||
<action>Create new versioned status file</action>
|
||||
<action>Set status_file_path = "{output_folder}/project-workflow-status-{{today}}.md"</action>
|
||||
<action>Set start_date = {{today}}</action>
|
||||
<action>Proceed to assessment</action>
|
||||
</check>
|
||||
|
||||
@@ -204,58 +228,60 @@ Examples:
|
||||
|
||||
</step>
|
||||
|
||||
<step n="5" goal="Create workflow analysis document">
|
||||
<step n="5" goal="Create workflow status document">
|
||||
|
||||
<action>Initialize analysis using analysis_template from workflow.yaml</action>
|
||||
<action>Initialize status file using status_template from workflow.yaml</action>
|
||||
<action>Write to versioned file path: {{status_file_path}}</action>
|
||||
<action>Set start_date = {{today}} in template variables</action>
|
||||
|
||||
<critical>Capture any technical preferences mentioned during assessment</critical>
|
||||
<critical>Initialize Workflow Status Tracker with current state</critical>
|
||||
|
||||
Generate comprehensive analysis with all assessment data.
|
||||
Generate comprehensive status document with all assessment data.
|
||||
|
||||
<template-output file="project-workflow-analysis.md">project_type</template-output>
|
||||
<template-output file="project-workflow-analysis.md">project_level</template-output>
|
||||
<template-output file="project-workflow-analysis.md">instruction_set</template-output>
|
||||
<template-output file="project-workflow-analysis.md">scope_description</template-output>
|
||||
<template-output file="project-workflow-analysis.md">story_count</template-output>
|
||||
<template-output file="project-workflow-analysis.md">epic_count</template-output>
|
||||
<template-output file="project-workflow-analysis.md">timeline</template-output>
|
||||
<template-output file="project-workflow-analysis.md">field_type</template-output>
|
||||
<template-output file="project-workflow-analysis.md">existing_docs</template-output>
|
||||
<template-output file="project-workflow-analysis.md">team_size</template-output>
|
||||
<template-output file="project-workflow-analysis.md">deployment_intent</template-output>
|
||||
<template-output file="project-workflow-analysis.md">expected_outputs</template-output>
|
||||
<template-output file="project-workflow-analysis.md">workflow_steps</template-output>
|
||||
<template-output file="project-workflow-analysis.md">next_steps</template-output>
|
||||
<template-output file="project-workflow-analysis.md">special_notes</template-output>
|
||||
<template-output file="project-workflow-analysis.md">technical_preferences</template-output>
|
||||
<template-output file="{{status_file_path}}">project_type</template-output>
|
||||
<template-output file="project-workflow-status.md">project_level</template-output>
|
||||
<template-output file="project-workflow-status.md">instruction_set</template-output>
|
||||
<template-output file="project-workflow-status.md">scope_description</template-output>
|
||||
<template-output file="project-workflow-status.md">story_count</template-output>
|
||||
<template-output file="project-workflow-status.md">epic_count</template-output>
|
||||
<template-output file="project-workflow-status.md">timeline</template-output>
|
||||
<template-output file="project-workflow-status.md">field_type</template-output>
|
||||
<template-output file="project-workflow-status.md">existing_docs</template-output>
|
||||
<template-output file="project-workflow-status.md">team_size</template-output>
|
||||
<template-output file="project-workflow-status.md">deployment_intent</template-output>
|
||||
<template-output file="project-workflow-status.md">expected_outputs</template-output>
|
||||
<template-output file="project-workflow-status.md">workflow_steps</template-output>
|
||||
<template-output file="project-workflow-status.md">next_steps</template-output>
|
||||
<template-output file="project-workflow-status.md">special_notes</template-output>
|
||||
<template-output file="project-workflow-status.md">technical_preferences</template-output>
|
||||
|
||||
<action>Initialize Workflow Status Tracker section:</action>
|
||||
|
||||
<template-output file="project-workflow-analysis.md">current_phase</template-output>
|
||||
<template-output file="project-workflow-status.md">current_phase</template-output>
|
||||
Set to: "2-Plan"
|
||||
|
||||
<template-output file="project-workflow-analysis.md">current_workflow</template-output>
|
||||
<template-output file="project-workflow-status.md">current_workflow</template-output>
|
||||
<check if="Level 0">Set to: "tech-spec (Level 0 - starting)"</check>
|
||||
<check if="Level 1">Set to: "tech-spec (Level 1 - starting)"</check>
|
||||
<check if="Level 2+">Set to: "PRD (Level {{project_level}} - starting)"</check>
|
||||
|
||||
<template-output file="project-workflow-analysis.md">progress_percentage</template-output>
|
||||
<template-output file="project-workflow-status.md">progress_percentage</template-output>
|
||||
Set to: 10% (assessment complete)
|
||||
|
||||
<template-output file="project-workflow-analysis.md">artifacts_table</template-output>
|
||||
<template-output file="project-workflow-status.md">artifacts_table</template-output>
|
||||
Initialize with:
|
||||
|
||||
```
|
||||
| project-workflow-analysis.md | Complete | {output_folder}/project-workflow-analysis.md | {{date}} |
|
||||
| project-workflow-status.md | Complete | {output_folder}/project-workflow-status.md | {{date}} |
|
||||
```
|
||||
|
||||
<template-output file="project-workflow-analysis.md">next_action</template-output>
|
||||
<template-output file="project-workflow-status.md">next_action</template-output>
|
||||
<check if="Level 0">Set to: "Generate technical specification and single user story"</check>
|
||||
<check if="Level 1">Set to: "Generate technical specification and epic/stories (2-3 stories)"</check>
|
||||
<check if="Level 2+">Set to: "Generate PRD and epic breakdown"</check>
|
||||
|
||||
<template-output file="project-workflow-analysis.md">decisions_log</template-output>
|
||||
<template-output file="project-workflow-status.md">decisions_log</template-output>
|
||||
Add first entry:
|
||||
|
||||
```
|
||||
|
||||
@@ -12,7 +12,7 @@
|
||||
|
||||
<step n="1" goal="Load context and handle continuation">
|
||||
|
||||
<action>Load project-workflow-analysis.md</action>
|
||||
<action>Load project-workflow-status.md</action>
|
||||
<action>Confirm Level 3-4 - Full product or platform</action>
|
||||
|
||||
<check if="continuation_mode == true">
|
||||
|
||||
@@ -12,7 +12,7 @@
|
||||
|
||||
<step n="1" goal="Load context and handle continuation">
|
||||
|
||||
<action>Load project-workflow-analysis.md</action>
|
||||
<action>Load project-workflow-status.md</action>
|
||||
<action>Confirm Level 1-2 - Feature or small system</action>
|
||||
|
||||
<check if="continuation_mode == true">
|
||||
|
||||
@@ -19,11 +19,11 @@ instructions_lg: "{installed_path}/instructions-lg.md" # Level 3-4
|
||||
|
||||
# Templates
|
||||
prd_template: "{installed_path}/prd-template.md"
|
||||
analysis_template: "{project-root}/bmad/bmm/workflows/_shared/project-workflow-analysis-template.md"
|
||||
status_template: "{project-root}/bmad/bmm/workflows/_shared/project-workflow-status-template.md"
|
||||
epics_template: "{installed_path}/epics-template.md"
|
||||
|
||||
# Output configuration
|
||||
analysis_file: "{output_folder}/project-workflow-analysis.md"
|
||||
status_file: "{output_folder}/project-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-analysis-template.md"
|
||||
- "bmad/bmm/workflows/_shared/project-workflow-status-template.md"
|
||||
- "bmad/bmm/workflows/2-plan/prd/epics-template.md"
|
||||
# Scale parameters - adaptive by project level
|
||||
scale_parameters:
|
||||
|
||||
@@ -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-analysis.md from {output_folder}/project-workflow-analysis.md</action>
|
||||
<action>Load project-workflow-status.md from {output_folder}/project-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>
|
||||
@@ -100,7 +100,7 @@
|
||||
|
||||
<step n="4" goal="Update project-workflow-analysis with progress">
|
||||
|
||||
<action>Open {output_folder}/project-workflow-analysis.md</action>
|
||||
<action>Open {output_folder}/project-workflow-status.md</action>
|
||||
<action>Update "Workflow Status Tracker" section</action>
|
||||
|
||||
<action>Set current_phase = "2-Plan"</action>
|
||||
@@ -130,7 +130,7 @@
|
||||
- **{{date}}**: Level 0 tech-spec and story generation completed. Story: story-{slug}.md ready for context generation.
|
||||
```
|
||||
|
||||
<action>Save project-workflow-analysis.md</action>
|
||||
<action>Save project-workflow-status.md</action>
|
||||
|
||||
</step>
|
||||
|
||||
@@ -163,7 +163,7 @@
|
||||
|
||||
**Progress Tracking:**
|
||||
|
||||
- All decisions logged in: `project-workflow-analysis.md`
|
||||
- All decisions logged in: `project-workflow-status.md`
|
||||
- Next action clearly identified
|
||||
|
||||
<ask>Ready to proceed? Choose your path:
|
||||
|
||||
@@ -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-analysis.md from {output_folder}/project-workflow-analysis.md</action>
|
||||
<action>Load project-workflow-status.md from {output_folder}/project-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>
|
||||
@@ -230,7 +230,7 @@ Epic: Icon Reliability
|
||||
|
||||
<step n="6" goal="Update project-workflow-analysis with progress">
|
||||
|
||||
<action>Open {output_folder}/project-workflow-analysis.md</action>
|
||||
<action>Open {output_folder}/project-workflow-status.md</action>
|
||||
<action>Update "Workflow Status Tracker" section</action>
|
||||
|
||||
<action>Set current_phase = "2-Plan"</action>
|
||||
@@ -265,7 +265,7 @@ Epic: Icon Reliability
|
||||
- **{{date}}**: Level 1 tech-spec and epic/stories generation completed. {{story_count}} stories created. Ready for implementation of story-{epic_slug}-1.md.
|
||||
```
|
||||
|
||||
<action>Save project-workflow-analysis.md</action>
|
||||
<action>Save project-workflow-status.md</action>
|
||||
|
||||
</step>
|
||||
|
||||
@@ -317,7 +317,7 @@ d. Run dev-story workflow to implement story 1
|
||||
|
||||
**Progress Tracking:**
|
||||
|
||||
- All decisions logged in: `project-workflow-analysis.md`
|
||||
- All decisions logged in: `project-workflow-status.md`
|
||||
- Next action clearly identified
|
||||
|
||||
<ask>Ready to proceed? Choose your path:
|
||||
|
||||
@@ -11,7 +11,7 @@
|
||||
|
||||
<step n="1" goal="Confirm project scope and update tracking">
|
||||
|
||||
<action>Load project-workflow-analysis.md from {output_folder}/project-workflow-analysis.md</action>
|
||||
<action>Load project-workflow-status.md from {output_folder}/project-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-analysis.md</action>
|
||||
<action>Save project-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-analysis.md:</action>
|
||||
<action>Update progress in project-workflow-status.md:</action>
|
||||
<action>Set progress_percentage = 40%</action>
|
||||
<action>Save project-workflow-analysis.md</action>
|
||||
<action>Save project-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-analysis.md to determine project_level</action>
|
||||
<action>Load project-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>
|
||||
|
||||
@@ -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-analysis.md (understand project level and scope)
|
||||
- project-workflow-status.md (understand project level and scope)
|
||||
|
||||
</check>
|
||||
|
||||
|
||||
@@ -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"
|
||||
analysis_template: "{project-root}/bmad/bmm/workflows/_shared/project-workflow-analysis-template.md"
|
||||
status_template: "{project-root}/bmad/bmm/workflows/_shared/project-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
|
||||
analysis_file: "{output_folder}/project-workflow-analysis.md"
|
||||
status_file: "{output_folder}/project-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"
|
||||
analysis_template: "bmad/bmm/workflows/_shared/project-workflow-analysis-template.md"
|
||||
status_template: "bmad/bmm/workflows/_shared/project-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"
|
||||
|
||||
Reference in New Issue
Block a user