date removed from status file, status file renamed
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-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
|
||||
|
||||
---
|
||||
|
||||
@@ -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
|
||||
|
||||
|
||||
@@ -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}}
|
||||
|
||||
@@ -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">
|
||||
|
||||
@@ -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">
|
||||
|
||||
@@ -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,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:
|
||||
|
||||
@@ -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:
|
||||
|
||||
@@ -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>
|
||||
|
||||
@@ -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>
|
||||
|
||||
|
||||
@@ -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"
|
||||
|
||||
Reference in New Issue
Block a user