bmad-method 6.0.0-alpha.0 → 6.0.0-alpha.1

package/src/modules/bmm/workflows/{2-plan → 2-plan-workflows}/narrative/instructions-narrative.md

@@ -2,11 +2,30 @@
 
 <workflow>
 
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
+<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already completed the GDD workflow</critical>
+<critical>Communicate all responses in {communication_language}</critical>
 <critical>This workflow creates detailed narrative content for story-driven games</critical>
 <critical>Uses narrative_template for output</critical>
 <critical>If users mention gameplay mechanics, note them but keep focus on narrative</critical>
+<critical>Facilitate good brainstorming techniques throughout with the user, pushing them to come up with much of the narrative you will help weave together. The goal is for the user to feel that they crafted the narrative and story arc unless they push you to do it all or indicate YOLO</critical>
+
+<step n="0" goal="Check for workflow status">
+
+<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
+  <param>mode: init-check</param>
+</invoke-workflow>
+
+<check if="status_exists == true">
+  <action>Store {{status_file_path}} for later updates</action>
+  <action>Set tracking_mode = true</action>
+</check>
+
+<check if="status_exists == false">
+  <action>Set tracking_mode = false</action>
+  <output>Note: Running without workflow tracking. Run `workflow-init` to enable progress tracking.</output>
+</check>
+</step>
 
 <step n="1" goal="Load GDD context and assess narrative complexity">
 
@@ -26,7 +45,7 @@ Your game type ({{game_type}}) suggests **{{suggested_complexity}}**. Confirm or
 
 <action>Set narrative_complexity</action>
 
-<check>If complexity == "Light":</check>
+<check if="complexity == Light">
 <ask>Light narrative games usually don't need a full Narrative Design Document. Are you sure you want to continue?
 
 - GDD story sections may be sufficient
@@ -37,6 +56,8 @@ Your choice:</ask>
 
 <action>Load narrative_template from workflow.yaml</action>
 
+</check>
+
 </step>
 
 <step n="2" goal="Define narrative premise and themes">
@@ -102,7 +123,7 @@ For 3-Act:
 Describe each act/section for your game:</ask>
 
 <template-output>act_breakdown</template-output>
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -121,7 +142,7 @@ Format:
 Your story beats:</ask>
 
 <template-output>story_beats</template-output>
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 <ask>Describe the pacing and flow of your narrative.
 
@@ -154,7 +175,7 @@ For each protagonist include:
 Your protagonist(s):</ask>
 
 <template-output>protagonists</template-output>
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -192,7 +213,7 @@ For each character include:
 Your supporting characters:</ask>
 
 <template-output>supporting_characters</template-output>
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -240,7 +261,7 @@ Your world:</ask>
 Your history:</ask>
 
 <template-output>history_backstory</template-output>
-<elicit-required/>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -304,8 +325,8 @@ Your key conversations:</ask>
 
 <template-output>key_conversations</template-output>
 
-<check>If game has branching dialogue:</check>
-<ask>Describe your branching dialogue system.
+<check if="game has branching dialogue">
+  <ask>Describe your branching dialogue system.
 
 - How many branches/paths?
 - What determines branches? (stats, choices, flags)
@@ -315,6 +336,7 @@ Your key conversations:</ask>
 Your branching system:</ask>
 
 <template-output>branching_dialogue</template-output>
+</check>
 
 </step>
 
@@ -397,8 +419,8 @@ Your optional content:</ask>
 
 <template-output>optional_content</template-output>
 
-<check>If multiple endings:</check>
-<ask>Describe your ending structure.
+<check if="multiple endings">
+  <ask>Describe your ending structure.
 
 - How many endings?
 - What determines ending? (choices, stats, completion)
@@ -408,6 +430,7 @@ Your optional content:</ask>
 Your endings:</ask>
 
 <template-output>multiple_endings</template-output>
+</check>
 
 </step>
 
@@ -503,7 +526,9 @@ Your references:</ask>
 
 <template-output>references</template-output>
 
-<ask>Narrative Design complete! Next steps:
+<ask>**✅ Narrative Design Complete, {user_name}!**
+
+Next steps:
 
 1. Proceed to solutioning (technical architecture)
 2. Create detailed script/screenplay (outside workflow)
@@ -514,4 +539,19 @@ Which would you like?</ask>
 
 </step>
 
+<step n="17" goal="Update status if tracking enabled">
+
+<check if="tracking_mode == true">
+  <invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
+    <param>mode: update</param>
+    <param>action: complete_workflow</param>
+    <param>workflow_name: narrative</param>
+  </invoke-workflow>
+
+  <check if="success == true">
+    <output>✅ Status updated! Next: {{next_workflow}}</output>
+  </check>
+</check>
+</step>
+
 </workflow>

package/src/modules/bmm/workflows/{2-plan → 2-plan-workflows}/narrative/narrative-template.md

@@ -16,7 +16,7 @@
 
 {{core_themes}}
 
-### Tone & Atmosphere
+### Tone and Atmosphere
 
 {{tone_atmosphere}}
 
@@ -38,7 +38,7 @@
 
 {{story_beats}}
 
-### Pacing & Flow
+### Pacing and Flow
 
 {{pacing_flow}}
 
@@ -64,17 +64,17 @@
 
 ---
 
-## World & Lore
+## World and Lore
 
 ### World Overview
 
 {{world_overview}}
 
-### History & Backstory
+### History and Backstory
 
 {{history_backstory}}
 
-### Factions & Organizations
+### Factions and Organizations
 
 {{factions_organizations}}
 
@@ -102,7 +102,7 @@
 
 {{branching_dialogue}}
 
-### Voice & Characterization
+### Voice and Characterization
 
 {{voice_characterization}}
 
@@ -130,7 +130,7 @@
 
 ## Narrative Delivery
 
-### Cutscenes & Cinematics
+### Cutscenes and Cinematics
 
 {{cutscenes}}
 
@@ -190,6 +190,6 @@
 
 {{timeline}}
 
-### References & Inspirations
+### References and Inspirations
 
 {{references}}

package/src/modules/bmm/workflows/2-plan-workflows/narrative/workflow.yaml

@@ -0,0 +1,38 @@
+# Narrative Design Workflow
+name: narrative
+description: "Narrative design workflow for story-driven games and applications. Creates comprehensive narrative documentation including story structure, character arcs, dialogue systems, and narrative implementation guidance."
+author: "BMad"
+
+# Critical variables from config
+config_source: "{project-root}/bmad/bmm/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+document_output_language: "{config_source}:document_output_language"
+user_skill_level: "{config_source}:user_skill_level"
+date: system-generated
+
+# Workflow components
+installed_path: "{project-root}/bmad/bmm/workflows/2-plan-workflows/narrative"
+instructions: "{installed_path}/instructions-narrative.md"
+template: "{installed_path}/narrative-template.md"
+
+# Output configuration
+default_output_file: "{output_folder}/narrative-design.md"
+
+# Recommended input documents
+recommended_inputs:
+  - game_brief: "{output_folder}/game-brief.md"
+  - gdd: "{output_folder}/GDD.md"
+  - product_brief: "{output_folder}/product-brief.md"
+
+standalone: true
+
+web_bundle:
+  name: "narrative"
+  description: "Narrative design workflow for story-driven games and applications. Creates comprehensive narrative documentation including story structure, character arcs, dialogue systems, and narrative implementation guidance."
+  author: "BMad"
+  instructions: "bmad/bmm/workflows/2-plan-workflows/narrative/instructions-narrative.md"
+  web_bundle_files:
+    - "bmad/bmm/workflows/2-plan-workflows/narrative/instructions-narrative.md"
+    - "bmad/bmm/workflows/2-plan-workflows/narrative/narrative-template.md"

package/src/modules/bmm/workflows/2-plan-workflows/prd/checklist.md

@@ -0,0 +1,117 @@
+# PRD Workflow Validation Checklist
+
+**Purpose**: Validate PRD workflow outputs are complete, consistent, and ready for next phase.
+
+**Scope**: Levels 2-4 software projects
+
+**Expected Outputs**: PRD.md, epics.md, updated bmm-workflow-status.md
+
+---
+
+## 1. Output Files Exist
+
+- [ ] PRD.md created in output folder
+- [ ] epics.md created in output folder (separate file)
+- [ ] bmm-workflow-status.md updated
+- [ ] No unfilled {{template_variables}}
+
+---
+
+## 2. PRD.md Core Quality
+
+### Requirements Coverage
+
+- [ ] Functional requirements describe WHAT capabilities (not HOW to implement)
+- [ ] Each FR has unique identifier (FR001, FR002, etc.)
+- [ ] Non-functional requirements (if any) have business justification
+- [ ] Requirements are testable and verifiable
+
+### User Journeys
+
+- [ ] User journeys reference specific FR numbers
+- [ ] Journeys show complete user paths through system
+- [ ] Success outcomes are clear
+
+### Strategic Focus
+
+- [ ] PRD focuses on WHAT and WHY (not technical HOW)
+- [ ] No specific technology choices in PRD (those belong in technical-decisions.md)
+- [ ] Goals are outcome-focused, not implementation-focused
+
+---
+
+## 3. epics.md Story Quality
+
+### Story Format
+
+- [ ] All stories follow user story format: "As a [role], I want [capability], so that [benefit]"
+- [ ] Each story has numbered acceptance criteria
+- [ ] Prerequisites/dependencies explicitly stated
+
+### Story Sequencing (CRITICAL)
+
+- [ ] **Epic 1 establishes foundation** (infrastructure, initial deployable functionality)
+  - Exception noted if adding to existing app
+- [ ] **Vertical slices**: Each story delivers complete, testable functionality (not horizontal layers)
+- [ ] **No forward dependencies**: No story depends on work from a LATER story or epic
+- [ ] Stories are sequentially ordered within each epic
+- [ ] Each story leaves system in working state
+
+### Coverage
+
+- [ ] All FRs from PRD.md are covered by stories in epics.md
+- [ ] Epic list in PRD.md matches epics in epics.md (titles and count)
+
+---
+
+## 4. Cross-Document Consistency
+
+- [ ] Epic titles consistent between PRD.md and epics.md
+- [ ] FR references in user journeys exist in requirements section
+- [ ] Terminology consistent across documents
+- [ ] No contradictions between PRD and epics
+
+---
+
+## 5. Readiness for Next Phase
+
+**Adapt based on project level from bmm-workflow-status.md:**
+
+### If Level 2:
+
+- [ ] PRD provides sufficient context for tech-spec workflow (lightweight solutioning)
+- [ ] Epic structure supports 5-15 story implementation scope
+
+### If Level 3-4:
+
+- [ ] PRD provides sufficient context for create-architecture workflow
+- [ ] Epic structure supports phased delivery approach
+- [ ] Clear value delivery path through epic sequence
+
+---
+
+## 6. Critical Failures (Auto-Fail)
+
+- [ ] ❌ **No epics.md file** (two-file output is required)
+- [ ] ❌ **Epic 1 doesn't establish foundation** (violates core principle)
+- [ ] ❌ **Stories have forward dependencies** (would break sequential implementation)
+- [ ] ❌ **Stories not vertically sliced** (horizontal layers block value delivery)
+- [ ] ❌ **Technical decisions in PRD** (should be in technical-decisions.md)
+- [ ] ❌ **Epics don't cover all FRs** (orphaned requirements)
+- [ ] ❌ **User journeys don't reference FR numbers** (missing traceability)
+
+---
+
+## Validation Notes
+
+**Document any findings:**
+
+- Strengths:
+- Issues to address:
+- Recommended actions:
+
+**Ready for next phase?** [Yes / No - explain]
+
+---
+
+_Adapt this checklist based on actual outputs. Not all sections may apply to every project._

package/src/modules/bmm/workflows/2-plan-workflows/prd/epics-template.md

@@ -0,0 +1,63 @@
+# {{project_name}} - Epic Breakdown
+
+**Author:** {{user_name}}
+**Date:** {{date}}
+**Project Level:** {{project_level}}
+**Target Scale:** {{target_scale}}
+
+---
+
+## Overview
+
+This document provides the detailed epic breakdown for {{project_name}}, expanding on the high-level epic list in the [PRD](./PRD.md).
+
+Each epic includes:
+
+- Expanded goal and value proposition
+- Complete story breakdown with user stories
+- Acceptance criteria for each story
+- Story sequencing and dependencies
+
+**Epic Sequencing Principles:**
+
+- Epic 1 establishes foundational infrastructure and initial functionality
+- Subsequent epics build progressively, each delivering significant end-to-end value
+- Stories within epics are vertically sliced and sequentially ordered
+- No forward dependencies - each story builds only on previous work
+
+---
+
+{{epic_details}}
+
+---
+
+## Story Guidelines Reference
+
+**Story Format:**
+
+```
+**Story [EPIC.N]: [Story Title]**
+
+As a [user type],
+I want [goal/desire],
+So that [benefit/value].
+
+**Acceptance Criteria:**
+1. [Specific testable criterion]
+2. [Another specific criterion]
+3. [etc.]
+
+**Prerequisites:** [Dependencies on previous stories, if any]
+```
+
+**Story Requirements:**
+
+- **Vertical slices** - Complete, testable functionality delivery
+- **Sequential ordering** - Logical progression within epic
+- **No forward dependencies** - Only depend on previous work
+- **AI-agent sized** - Completable in 2-4 hour focused session
+- **Value-focused** - Integrate technical enablers into value-delivering stories
+
+---
+
+**For implementation:** Use the `create-story` workflow to generate individual story implementation plans from this epic breakdown.