bmad-method 6.0.0-alpha.16 → 6.0.0-alpha.18

package/src/modules/bmgd/workflows/2-design/narrative/steps/step-11-complete.md

@@ -0,0 +1,331 @@
+---
+name: 'step-11-complete'
+description: 'Complete the narrative workflow with final summary, visualizations, and handoff'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-11-complete.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/narrative-design.md'
+
+# Handoff References
+architectureWorkflow: '{project-root}/_bmad/bmgd/workflows/3-technical/game-architecture/workflow.yaml'
+---
+
+# Step 11: Complete
+
+**Progress: Step 11 of 11** - Narrative Design Complete!
+
+## STEP GOAL:
+
+Generate final visualizations (character relationships, timeline), capture references, update workflow status, and provide clear handoff guidance.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- NEVER generate content without user input
+- CRITICAL: Read the complete step file before taking any action
+- YOU ARE A FACILITATOR, not a content generator
+- NEVER mention time estimates
+
+### Role Reinforcement:
+
+- You are a narrative design facilitator
+- This is the final step - ensure completeness
+- Provide actionable next steps
+
+### Step-Specific Rules:
+
+- Generate relationship map from characters defined
+- Generate timeline from story beats
+- Capture any references user wants to note
+
+## EXECUTION PROTOCOLS:
+
+- Show your analysis before taking any action
+- Generate final visualizations
+- Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11]`
+- Present completion summary and next steps
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Generate Character Relationship Map
+
+**Create text-based relationship visualization:**
+
+Based on all characters documented, generate:
+
+```markdown
+## Appendix: Character Relationships
+
+### Relationship Map
+```
+
+                    [ANTAGONIST]
+                         |
+                    (opposes)
+                         |
+    [MENTOR] ---(guides)--- [PROTAGONIST] ---(allies)--- [COMPANION]
+                         |
+                    (romantic)
+                         |
+                  [LOVE INTEREST]
+
+```
+
+### Relationship Key
+
+- {{character_1}} → {{character_2}}: {{relationship_type}}
+- {{character_2}} → {{character_3}}: {{relationship_type}}
+{{continue_for_all_relationships}}
+```
+
+### 2. Generate Story Timeline
+
+**Create timeline visualization:**
+
+Based on story beats documented, generate:
+
+```markdown
+## Appendix: Story Timeline
+
+### Chronological Events
+```
+
+[BACKSTORY]
+|
+v
+[ACT 1: SETUP]
+├── {{beat_1}}
+├── {{beat_2}}
+└── {{inciting_incident}}
+|
+v
+[ACT 2: CONFRONTATION]
+├── {{beat_3}}
+├── {{midpoint}}
+├── {{beat_4}}
+└── {{crisis}}
+|
+v
+[ACT 3: RESOLUTION]
+├── {{climax}}
+└── {{resolution}}
+
+```
+
+### Timeline Notes
+
+{{any_timeline_clarifications}}
+```
+
+### 3. References Discovery
+
+"**Do you have any references or inspirations to note?**
+
+This helps future writers understand your vision:
+
+- Books, movies, games that inspired you
+- Reference materials for tone/style
+- Mood boards or concept art references
+- Theme or narrative references
+
+What references should be documented? (or 'none'):"
+
+### 4. Finalize Document
+
+**Update the document with final content:**
+
+Add relationship map and timeline to document.
+
+**Final frontmatter:**
+
+```yaml
+---
+title: 'Narrative Design Document'
+project: '{{game_name}}'
+date: '{{date}}'
+author: '{{user_name}}'
+version: '1.0'
+stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11]
+status: 'complete'
+narrativeComplexity: '{{complexity}}'
+---
+```
+
+### 5. Update Workflow Status
+
+**If not in standalone mode:**
+
+Load `{output_folder}/bmm-workflow-status.yaml` and:
+
+- Update `narrative` status to the output file path
+- Preserve all comments and structure
+- Determine next workflow in sequence
+
+### 6. Present Completion Summary
+
+"**Narrative Design Complete!**
+
+{{user_name}}, the Narrative Design Document for **{{game_name}}** is complete!
+
+**Narrative Summary:**
+
+- **Premise:** {{premise_summary}}
+- **Themes:** {{themes_list}}
+- **Characters:** {{character_count}} ({{protagonist_count}} protagonist, {{antagonist_count}} antagonist, {{supporting_count}} supporting)
+- **Story Structure:** {{structure_type}}
+- **Writing Scope:** ~{{word_count}} words
+
+**Sections Completed:**
+
+1. Story Foundation (premise, themes, structure)
+2. Story Beats (major moments, pacing)
+3. Characters (all characters and arcs)
+4. World Building (setting, history, locations)
+5. Dialogue Framework (style, key conversations)
+6. Environmental Storytelling (visual, audio, documents)
+7. Narrative Delivery (cutscenes, in-game, endings)
+8. Gameplay Integration (gating, agency)
+9. Production Planning (scope, localization, voice)
+10. Appendices (relationships, timeline)
+
+**Document saved to:** `{outputFile}`
+
+Do you want to review or adjust anything before we finalize?"
+
+### 7. Handle Review Requests
+
+**If user wants to review:**
+
+"Which would you like to review?
+
+1. Story Foundation
+2. Story Beats
+3. Characters
+4. World Building
+5. Dialogue
+6. Environmental Storytelling
+7. Narrative Delivery
+8. Gameplay Integration
+9. Production Planning
+10. Full Document
+
+Select a section:"
+
+### 8. Present Next Steps Menu
+
+"**Recommended Next Steps:**
+
+1. **Technical Architecture** - Define how narrative systems will be implemented
+   - Workflow: `create-architecture`
+   - Input: GDD + Narrative Design
+   - Output: Technical architecture document
+
+2. **Create Script/Screenplay** - Write the actual dialogue and scenes
+   - This is done outside the workflow
+   - Use the Narrative Design as your blueprint
+
+3. **Review with Team** - Share with collaborators for feedback
+
+4. **Exit Workflow**
+
+**Which would you like to do next?**
+
+1. Start Architecture workflow
+2. Review the narrative document
+3. Exit workflow"
+
+### 9. Handle User Selection
+
+Based on user choice:
+
+**If 1 (Architecture):**
+
+- Confirm document is saved
+- Provide handoff guidance
+- Note narrative will inform technical decisions
+
+**If 2 (Review):**
+
+- Present full document or requested section
+- Return to next steps menu
+
+**If 3 (Exit):**
+
+- Confirm document is saved and complete
+- Exit workflow gracefully
+
+### 10. Final Completion Message
+
+"**Narrative Design Complete!**
+
+**Deliverables:**
+
+- Narrative design saved to: `{outputFile}`
+- {{character_count}} characters documented
+- {{beat_count}} story beats mapped
+- {{location_count}} locations defined
+
+{{#if standalone_mode != true}}
+**Status Updated:**
+
+- Progress tracking updated: narrative marked complete
+- Next recommended: Architecture workflow
+  {{/if}}
+
+**Your Narrative Is Ready For:**
+
+- Script/screenplay writing
+- Technical implementation planning
+- Team review and iteration
+- Production scheduling
+
+Excellent work crafting the narrative for {{game_name}}, {{user_name}}!"
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- Relationship map generated
+- Timeline generated
+- References captured
+- All content saved to document
+- Workflow status updated (if tracking)
+- Frontmatter shows all 11 steps completed
+- User has clear next steps
+
+### SYSTEM FAILURE:
+
+- Missing visualizations
+- Incomplete document
+- Status not updated when tracking
+- No clear next steps provided
+- User left without guidance
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
+
+---
+
+## Narrative Design Workflow Complete
+
+The Narrative Design workflow creates comprehensive narrative documentation through 11 collaborative steps:
+
+1. **Initialize** - Validate readiness, assess complexity
+2. **Foundation** - Premise, themes, tone, structure
+3. **Story** - Beats and pacing
+4. **Characters** - All characters and arcs
+5. **World** - Setting, history, factions, locations
+6. **Dialogue** - Style and systems
+7. **Environmental** - Environmental storytelling
+8. **Delivery** - Narrative delivery methods
+9. **Integration** - Gameplay-narrative connection
+10. **Production** - Scope and planning
+11. **Complete** - Visualizations and handoff
+
+This step-file architecture ensures consistent, thorough narrative design with user collaboration at every step.

package/src/modules/bmgd/workflows/2-design/narrative/workflow.md

@@ -0,0 +1,57 @@
+# Narrative Design Workflow
+
+**Comprehensive narrative design for story-driven games**
+
+## Overview
+
+This workflow creates detailed narrative content for games with significant story elements. It covers story structure, character development, world-building, dialogue systems, environmental storytelling, and production planning.
+
+## Workflow Structure
+
+The workflow uses a step-file architecture for modular, stateful execution:
+
+1. **Step 1: Initialize** - Validate readiness, load GDD, assess narrative complexity
+2. **Step 1b: Continue** - Resume existing narrative work
+3. **Step 2: Foundation** - Define premise, themes, tone, and story structure
+4. **Step 3: Story** - Map story beats and pacing
+5. **Step 4: Characters** - Develop all characters and their arcs
+6. **Step 5: World** - Build world, history, factions, and locations
+7. **Step 6: Dialogue** - Define dialogue style and systems
+8. **Step 7: Environmental** - Plan environmental storytelling
+9. **Step 8: Delivery** - Design narrative delivery methods
+10. **Step 9: Integration** - Plan gameplay-narrative integration
+11. **Step 10: Production** - Scope, localization, and voice acting
+12. **Step 11: Complete** - Final summary and handoff
+
+## State Tracking
+
+Progress is tracked in the narrative document frontmatter:
+
+```yaml
+stepsCompleted: [1, 2, 3, ...] # Array of completed step numbers
+```
+
+## Starting the Workflow
+
+To begin, load and execute step-01-init.md:
+
+```
+{workflow_path}/steps/step-01-init.md
+```
+
+## Critical Rules
+
+- **NEVER** generate narrative content without user input
+- **ALWAYS** facilitate user creativity - help them craft THEIR story
+- **NEVER** mention time estimates
+- **ALWAYS** present options and wait for user selection
+- **FOLLOW** the step sequence exactly - no skipping or optimizing
+
+## Agent Role
+
+You are a narrative design facilitator:
+
+- Draw out the user's story vision
+- Help weave user's ideas into cohesive narrative
+- Focus on what the user wants to create
+- The goal is for users to feel THEY crafted the narrative

package/src/modules/bmgd/workflows/2-design/narrative/workflow.yaml

@@ -1,10 +1,10 @@
 # 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."
+description: "Narrative design workflow for story-driven games. Creates comprehensive narrative documentation including story structure, character arcs, world-building, dialogue systems, and production planning."
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/.bmad/bmgd/config.yaml"
+config_source: "{project-root}/_bmad/bmgd/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -12,21 +12,66 @@ document_output_language: "{config_source}:document_output_language"
 game_dev_experience: "{config_source}:game_dev_experience"
 date: system-generated
 
-# Workflow components
-installed_path: "{project-root}/.bmad/bmgd/workflows/2-design/narrative"
-instructions: "{installed_path}/instructions-narrative.md"
-template: "{installed_path}/narrative-template.md"
+# Workflow components - Step-file architecture
+installed_path: "{project-root}/_bmad/bmgd/workflows/2-design/narrative"
+instructions: "{installed_path}/workflow.md"
+template: "{installed_path}/templates/narrative-template.md"
+validation: "{installed_path}/checklist.md"
+
+# Smart input file references
+input_file_patterns:
+  gdd:
+    description: "Game Design Document with mechanics and systems"
+    whole: "{output_folder}/*gdd*.md"
+    sharded: "{output_folder}/*gdd*/index.md"
+    load_strategy: "INDEX_GUIDED"
+
+  brief:
+    description: "Game Brief with vision (optional)"
+    whole: "{output_folder}/*brief*.md"
+    sharded: "{output_folder}/*brief*/index.md"
+    load_strategy: "INDEX_GUIDED"
 
 # Output configuration
 default_output_file: "{output_folder}/narrative-design.md"
 
+# Workflow metadata
+version: "2.0.0"
+paradigm: "step-file-architecture"
+features:
+  - "Step-file architecture for modular execution"
+  - "Narrative complexity assessment"
+  - "Character development facilitation"
+  - "World-building guidance"
+  - "Dialogue system design"
+  - "Environmental storytelling planning"
+  - "Production scope estimation"
+  - "State tracking via frontmatter"
+
 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."
+  description: "Narrative design workflow for story-driven games"
   author: "BMad"
-  instructions: ".bmad/bmgd/workflows/2-design/narrative/instructions-narrative.md"
+  instructions: "_bmad/bmgd/workflows/2-design/narrative/workflow.md"
   web_bundle_files:
-    - ".bmad/bmgd/workflows/2-design/narrative/instructions-narrative.md"
-    - ".bmad/bmgd/workflows/2-design/narrative/narrative-template.md"
+    # Main workflow file
+    - "_bmad/bmgd/workflows/2-design/narrative/workflow.md"
+    # Step files
+    - "_bmad/bmgd/workflows/2-design/narrative/steps/step-01-init.md"
+    - "_bmad/bmgd/workflows/2-design/narrative/steps/step-01b-continue.md"
+    - "_bmad/bmgd/workflows/2-design/narrative/steps/step-02-foundation.md"
+    - "_bmad/bmgd/workflows/2-design/narrative/steps/step-03-story.md"
+    - "_bmad/bmgd/workflows/2-design/narrative/steps/step-04-characters.md"
+    - "_bmad/bmgd/workflows/2-design/narrative/steps/step-05-world.md"
+    - "_bmad/bmgd/workflows/2-design/narrative/steps/step-06-dialogue.md"
+    - "_bmad/bmgd/workflows/2-design/narrative/steps/step-07-environmental.md"
+    - "_bmad/bmgd/workflows/2-design/narrative/steps/step-08-delivery.md"
+    - "_bmad/bmgd/workflows/2-design/narrative/steps/step-09-integration.md"
+    - "_bmad/bmgd/workflows/2-design/narrative/steps/step-10-production.md"
+    - "_bmad/bmgd/workflows/2-design/narrative/steps/step-11-complete.md"
+    # Template
+    - "_bmad/bmgd/workflows/2-design/narrative/templates/narrative-template.md"
+    # Validation checklist
+    - "_bmad/bmgd/workflows/2-design/narrative/checklist.md"

package/src/modules/bmgd/workflows/3-technical/game-architecture/instructions.md

@@ -2,7 +2,7 @@
 
 <workflow name="architecture">
 
-<critical>The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml</critical>
+<critical>The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
 <critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}</critical>
 <critical>The goal is ARCHITECTURAL DECISIONS that prevent AI agent conflicts, not detailed implementation specs</critical>

package/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-01-init.md

@@ -0,0 +1,223 @@
+---
+name: 'step-01-init'
+description: 'Initialize the architecture workflow, validate readiness, and discover input documents'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/3-technical/game-architecture'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-01-init.md'
+continueStepFile: '{workflow_path}/steps/step-01b-continue.md'
+nextStepFile: '{workflow_path}/steps/step-02-context.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/game-architecture.md'
+templateFile: '{workflow_path}/templates/architecture-template.md'
+
+# Knowledge Bases
+decisionCatalog: '{workflow_path}/decision-catalog.yaml'
+architecturePatterns: '{workflow_path}/architecture-patterns.yaml'
+patternCategories: '{workflow_path}/pattern-categories.csv'
+---
+
+# Step 1: Initialize Architecture Workflow
+
+**Progress: Step 1 of 9** - Next: Project Context
+
+## STEP GOAL:
+
+Validate workflow readiness, check for existing architecture work, discover input documents (GDD, Epics), and initialize the output document with proper frontmatter.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- NEVER generate content without user input
+- CRITICAL: Read the complete step file before taking any action
+- CRITICAL: When loading next step with 'C', ensure entire file is read
+- YOU ARE A FACILITATOR, not a content generator
+- NEVER mention time estimates
+
+### Role Reinforcement:
+
+- You are a veteran game architect facilitator
+- Focus on architectural decisions that prevent AI agent conflicts
+- This is a decision-focused workflow, not an implementation spec
+
+### Step-Specific Rules:
+
+- Check for existing architecture before starting fresh
+- Validate that required input documents exist (GDD at minimum)
+- Initialize document with proper frontmatter for state tracking
+
+## EXECUTION PROTOCOLS:
+
+- Show your analysis before taking any action
+- Wait for user confirmation at each checkpoint
+- Update frontmatter `stepsCompleted: [1]` before loading next step
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Check for Existing Architecture
+
+**Search for existing architecture document:**
+
+Look for existing architecture files in {output_folder}:
+
+- `*architecture*.md`
+- `*arch*.md`
+
+**If existing architecture found:**
+
+"I found an existing architecture document: `{{existing_file}}`
+
+**Options:**
+
+1. **Continue** - Resume from where you left off
+2. **Start Fresh** - Begin a new architecture (will overwrite)
+3. **Review** - Let me review the existing document first
+
+Which would you like to do?"
+
+**Handle user selection:**
+
+- If **Continue**: Load `{continueStepFile}`
+- If **Start Fresh**: Continue with step 2 below
+- If **Review**: Show document summary and return to options
+
+### 2. Discover Required Input Documents
+
+**Search for GDD:**
+
+Look for GDD files using patterns:
+
+- `{output_folder}/*gdd*.md`
+- `{output_folder}/*game-design*.md`
+
+**If GDD not found:**
+
+"**GDD Not Found**
+
+The Architecture workflow works from your Game Design Document (GDD).
+
+The GDD provides:
+
+- Core mechanics and systems to architect
+- Technical requirements and constraints
+- Platform targets and performance needs
+
+Please run the GDD workflow first: `create-gdd`"
+
+**Exit workflow - GDD required**
+
+**If GDD found:**
+
+"**Input Document Found:**
+
+- GDD: `{{gdd_file}}`
+
+I'll analyze this to understand your game's technical requirements."
+
+### 3. Discover Optional Input Documents
+
+**Search for additional documents:**
+
+- **Epics**: `{output_folder}/*epic*.md`
+- **Game Brief**: `{output_folder}/*brief*.md`
+- **Narrative**: `{output_folder}/*narrative*.md`
+
+**Report findings:**
+
+"**Additional Documents Found:**
+{{list_of_found_documents}}
+
+These will provide additional context for architectural decisions."
+
+### 4. Confirm Workflow Start
+
+**Present start confirmation:**
+
+"**Ready to Start Architecture Workflow**
+
+{{user_name}}, I'm ready to help you create the game architecture for your project.
+
+**What we'll cover:**
+
+1. Engine/framework selection and validation
+2. Core architectural decisions (rendering, physics, networking, etc.)
+3. Project structure and code organization
+4. Implementation patterns for AI agent consistency
+5. Cross-cutting concerns (error handling, logging, etc.)
+
+**Input documents:**
+
+- GDD: `{{gdd_file}}`
+  {{additional_documents_list}}
+
+**The goal:** Create an architecture document that ensures all AI agents implement your game consistently.
+
+Ready to begin? [Y/N]"
+
+### 5. Initialize Output Document
+
+**If user confirms, create the initial document:**
+
+Create `{outputFile}` with frontmatter:
+
+```markdown
+---
+title: 'Game Architecture'
+project: '{{project_name}}'
+date: '{{date}}'
+author: '{{user_name}}'
+version: '1.0'
+stepsCompleted: [1]
+status: 'in-progress'
+
+# Source Documents
+gdd: '{{gdd_file}}'
+epics: '{{epics_file_or_null}}'
+brief: '{{brief_file_or_null}}'
+---
+
+# Game Architecture
+
+## Document Status
+
+This architecture document is being created through the BMGD Architecture Workflow.
+
+**Steps Completed:** 1 of 9 (Initialize)
+
+---
+
+_Content will be added as we progress through the workflow._
+```
+
+### 6. Proceed to Context Step
+
+After initialization:
+
+- Update frontmatter: `stepsCompleted: [1]`
+- Load `{nextStepFile}`
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- Existing architecture check performed
+- GDD discovered and validated
+- Optional documents discovered
+- User confirmed workflow start
+- Output document initialized with proper frontmatter
+- Frontmatter updated with stepsCompleted: [1]
+
+### SYSTEM FAILURE:
+
+- Skipping input document discovery
+- Starting without user confirmation
+- Not checking for existing architecture
+- Missing frontmatter initialization
+- Proceeding without GDD
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.