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

package/src/modules/bmgd/workflows/2-design/narrative/steps/step-01b-continue.md

@@ -0,0 +1,163 @@
+---
+name: 'step-01b-continue'
+description: 'Continue an existing narrative workflow from where it left off'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/narrative-design.md'
+
+# Step Files (for routing)
+step02: '{workflow_path}/steps/step-02-foundation.md'
+step03: '{workflow_path}/steps/step-03-story.md'
+step04: '{workflow_path}/steps/step-04-characters.md'
+step05: '{workflow_path}/steps/step-05-world.md'
+step06: '{workflow_path}/steps/step-06-dialogue.md'
+step07: '{workflow_path}/steps/step-07-environmental.md'
+step08: '{workflow_path}/steps/step-08-delivery.md'
+step09: '{workflow_path}/steps/step-09-integration.md'
+step10: '{workflow_path}/steps/step-10-production.md'
+step11: '{workflow_path}/steps/step-11-complete.md'
+---
+
+# Step 1b: Continue Existing Narrative
+
+**Resuming Narrative Workflow**
+
+## STEP GOAL:
+
+Load the existing narrative document, determine progress, and route to the appropriate next step.
+
+## 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
+
+### Step-Specific Rules:
+
+- Parse frontmatter to determine completed steps
+- Present summary of current progress
+- Route to correct next step based on state
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Load Existing Narrative
+
+**Read the existing narrative document:**
+
+Load `{outputFile}` and parse the frontmatter to extract:
+
+- `stepsCompleted` array
+- `status`
+- `project` name
+- `narrativeComplexity`
+- GDD reference
+
+### 2. Analyze Progress
+
+**Determine workflow state:**
+
+Map completed steps to workflow progress:
+
+- Step 1: Initialize
+- Step 2: Foundation (premise, themes, structure)
+- Step 3: Story (beats and pacing)
+- Step 4: Characters (all characters and arcs)
+- Step 5: World (world, history, locations)
+- Step 6: Dialogue (dialogue systems)
+- Step 7: Environmental (environmental storytelling)
+- Step 8: Delivery (narrative delivery methods)
+- Step 9: Integration (gameplay integration)
+- Step 10: Production (scope and planning)
+- Step 11: Complete
+
+**Calculate next step:**
+
+Find the highest completed step and determine the next step file to load.
+
+### 3. Present Continuation Summary
+
+"**Resuming Narrative Workflow**
+
+{{user_name}}, I found your existing narrative for **{{game_name}}**.
+
+**Progress:** Steps completed: {{stepsCompleted}}
+
+**Narrative Complexity:** {{narrativeComplexity}}
+
+**Sections Completed:**
+{{list_of_completed_sections}}
+
+**Current Status:**
+
+- Last completed: {{last_step_name}}
+- Next step: {{next_step_name}} (Step {{next_step_number}} of 11)
+
+Would you like to:
+
+1. **Continue** - Resume from {{next_step_name}}
+2. **Review** - Show me what we've written so far
+3. **Restart Step** - Redo the last completed step
+
+Select an option:"
+
+### 4. Handle User Selection
+
+**If Continue:**
+
+- Load the next step file based on `stepsCompleted`
+
+**If Review:**
+
+- Present summary of all completed sections
+- Show key narrative elements (premise, characters, etc.)
+- Return to continuation options
+
+**If Restart Step:**
+
+- Decrement stepsCompleted to remove last step
+- Load the step file for the step being restarted
+
+### 5. Route to Next Step
+
+Based on next step number, load the appropriate step file:
+
+| Next Step | File     |
+| --------- | -------- |
+| 2         | {step02} |
+| 3         | {step03} |
+| 4         | {step04} |
+| 5         | {step05} |
+| 6         | {step06} |
+| 7         | {step07} |
+| 8         | {step08} |
+| 9         | {step09} |
+| 10        | {step10} |
+| 11        | {step11} |
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- Existing document loaded and parsed
+- Progress accurately determined
+- User presented with clear options
+- Correct step file loaded based on state
+
+### SYSTEM FAILURE:
+
+- Failing to parse frontmatter correctly
+- Loading wrong step file
+- Not presenting continuation options
+- Overwriting existing progress without confirmation
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/modules/bmgd/workflows/2-design/narrative/steps/step-02-foundation.md

@@ -0,0 +1,262 @@
+---
+name: 'step-02-foundation'
+description: 'Define narrative premise, themes, tone, and story structure'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-02-foundation.md'
+nextStepFile: '{workflow_path}/steps/step-03-story.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/narrative-design.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Step 2: Story Foundation
+
+**Progress: Step 2 of 11** - Next: Story Beats
+
+## STEP GOAL:
+
+Define the narrative foundation: premise, themes, tone/atmosphere, and overall story structure. These elements form the backbone of all narrative content.
+
+## 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 narrative design facilitator
+- Help users articulate THEIR story vision
+- The premise should come from the user
+
+### Step-Specific Rules:
+
+- FORBIDDEN to generate premise without user input
+- Draw out user's ideas through questions
+- Themes should resonate with user's intent
+
+## EXECUTION PROTOCOLS:
+
+- Show your analysis before taking any action
+- Present A/P/C menu after generating content
+- ONLY save when user chooses C (Continue)
+- Update frontmatter `stepsCompleted: [1, 2]` before loading next step
+
+## COLLABORATION MENUS (A/P/C):
+
+- **A (Advanced Elicitation)**: Explore themes deeper
+- **P (Party Mode)**: Get perspectives on foundation
+- **C (Continue)**: Save the content and proceed
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Narrative Premise Discovery
+
+"Let's define the narrative foundation for **{{game_name}}**.
+
+**First, the premise - your story's elevator pitch in 2-3 sentences.**
+
+Good premises have:
+
+- A protagonist with a clear goal
+- An obstacle or conflict
+- Stakes (what happens if they fail?)
+
+**Examples:**
+
+- \"A young knight discovers they're the last hope to stop an ancient evil, but must choose between saving the kingdom or their own family.\"
+- \"After a mysterious pandemic, survivors must navigate a world where telling the truth is deadly but lying corrupts your soul.\"
+
+What's the premise for {{game_name}}?"
+
+### 2. Theme Discovery
+
+"**Now let's identify your core themes.**
+
+Themes are the underlying ideas or messages woven throughout the story.
+
+**Common game themes:**
+
+- Redemption, sacrifice, identity
+- Power and corruption
+- Hope vs. despair
+- Nature vs. technology
+- Freedom vs. control
+- Family, loyalty, betrayal
+
+**Questions to consider:**
+
+- What questions does your story ask?
+- What will players think about after playing?
+- What emotions do you want to evoke?
+
+What are 2-4 core themes for {{game_name}}?"
+
+### 3. Tone and Atmosphere Discovery
+
+"**Let's define the tone and atmosphere.**
+
+Tone shapes how the story feels moment-to-moment.
+
+**Tone spectrums:**
+
+- Dark ←→ Lighthearted
+- Serious ←→ Comedic
+- Gritty ←→ Fantastical
+- Intimate ←→ Epic
+- Hopeful ←→ Melancholic
+
+**Atmosphere elements:**
+
+- Visual mood (colors, lighting)
+- Audio mood (music style)
+- Pacing (contemplative vs. urgent)
+- Emotional register
+
+Describe the tone and atmosphere for {{game_name}}:"
+
+### 4. Story Structure Discovery
+
+"**What story structure will you use?**
+
+**Common structures:**
+
+| Structure          | Description                                            |
+| ------------------ | ------------------------------------------------------ |
+| **3-Act**          | Setup → Confrontation → Resolution                     |
+| **Hero's Journey** | Campbell's monomyth (departure, initiation, return)    |
+| **Kishōtenketsu**  | 4-act: Introduction → Development → Twist → Conclusion |
+| **Episodic**       | Self-contained episodes with overarching arc           |
+| **Branching**      | Multiple paths and endings                             |
+| **Freeform**       | Player-driven, emergent narrative                      |
+
+What structure fits {{game_name}}?"
+
+### 5. Act Breakdown
+
+"**Let's break down your story into acts/sections.**
+
+Based on {{selected_structure}}:
+
+{{structure_specific_prompts}}
+
+Describe each act/section for {{game_name}}:"
+
+### 6. Generate Foundation Content
+
+Based on the conversation, prepare the content:
+
+```markdown
+## Story Foundation
+
+### Narrative Premise
+
+{{user_premise}}
+
+### Core Themes
+
+{{themes_list_with_descriptions}}
+
+### Tone and Atmosphere
+
+**Tone:** {{tone_description}}
+
+**Atmosphere:** {{atmosphere_description}}
+
+**Emotional Register:** {{emotional_goals}}
+
+---
+
+## Story Structure
+
+### Structure Type
+
+**{{structure_type}}**
+
+{{structure_description}}
+
+### Act Breakdown
+
+{{act_breakdown_details}}
+```
+
+### 7. Present Content and Menu
+
+Show the generated content to the user and present:
+
+"I've drafted the Story Foundation based on our conversation.
+
+**Here's what I'll add to the document:**
+
+[Show the complete markdown content from step 6]
+
+**Validation Check:**
+
+- Does the premise capture your vision?
+- Do the themes resonate with your intent?
+- Does the structure fit your gameplay?
+
+**Select an Option:**
+[A] Advanced Elicitation - Explore themes and structure deeper
+[P] Party Mode - Get perspectives on foundation
+[C] Continue - Save this and move to Story Beats (Step 3 of 11)"
+
+### 8. Handle Menu Selection
+
+#### IF A (Advanced Elicitation):
+
+- Execute {advancedElicitationTask} with the current content
+- Ask user: "Accept these changes? (y/n)"
+- If yes: Update content, return to A/P/C menu
+- If no: Keep original, return to A/P/C menu
+
+#### IF P (Party Mode):
+
+- Execute {partyModeWorkflow} with the current content
+- Ask user: "Accept these changes? (y/n)"
+- If yes: Update content, return to A/P/C menu
+- If no: Keep original, return to A/P/C menu
+
+#### IF C (Continue):
+
+- Append the final content to `{outputFile}`
+- Update frontmatter: `stepsCompleted: [1, 2]`
+- Load `{nextStepFile}`
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [foundation content saved with frontmatter updated], will you then load and read fully `{nextStepFile}`.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- Premise captured from user input
+- Themes identified and described
+- Tone and atmosphere defined
+- Story structure selected and broken down
+- A/P/C menu presented and handled correctly
+- Frontmatter updated with stepsCompleted: [1, 2]
+
+### SYSTEM FAILURE:
+
+- Generating premise FOR user
+- Generic themes not connected to user's vision
+- Proceeding without structure breakdown
+- Not presenting A/P/C menu after content
+- Proceeding without user selecting 'C'
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/modules/bmgd/workflows/2-design/narrative/steps/step-03-story.md

@@ -0,0 +1,238 @@
+---
+name: 'step-03-story'
+description: 'Define major story beats and narrative pacing'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-03-story.md'
+nextStepFile: '{workflow_path}/steps/step-04-characters.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/narrative-design.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Step 3: Story Beats
+
+**Progress: Step 3 of 11** - Next: Characters
+
+## STEP GOAL:
+
+Define the major story beats (key narrative moments) and establish pacing and flow throughout the game experience.
+
+## 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 narrative design facilitator
+- Story beats are the skeleton of the narrative
+- Help user identify key moments, don't create them
+
+### Step-Specific Rules:
+
+- FORBIDDEN to generate story beats without user input
+- Guide user through beat mapping
+- Connect beats to structure defined in Step 2
+
+## EXECUTION PROTOCOLS:
+
+- Show your analysis before taking any action
+- Present A/P/C menu after generating content
+- ONLY save when user chooses C (Continue)
+- Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step
+
+## COLLABORATION MENUS (A/P/C):
+
+- **A (Advanced Elicitation)**: Explore beats and connections
+- **P (Party Mode)**: Get perspectives on pacing
+- **C (Continue)**: Save the content and proceed
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Story Beats Discovery
+
+"**Let's map the major story beats for {{game_name}}.**
+
+Story beats are significant events that drive the narrative forward.
+
+**Key beat types:**
+
+- **Inciting Incident** - What sets the story in motion?
+- **Plot Points** - Major turning points
+- **Midpoint** - Central pivot moment
+- **Climax** - Highest tension point
+- **Resolution** - How things conclude
+
+**Based on your {{structure_type}} structure, list 10-20 key moments.**
+
+Format:
+
+1. [Beat name] - Brief description
+2. [Beat name] - Brief description
+
+What are the major story beats for {{game_name}}?"
+
+### 2. Beat Placement
+
+"**Now let's place these beats within your structure.**
+
+For {{structure_type}}:
+
+**Act 1 beats:**
+Which of your beats belong in the setup/introduction?
+
+**Act 2 beats:**
+Which beats drive the main conflict/development?
+
+**Act 3 beats:**
+Which beats resolve the story?
+
+Let's organize your beats:"
+
+### 3. Pacing Discovery
+
+"**Let's define the pacing and flow.**
+
+**Pacing considerations:**
+
+| Aspect              | Options                           |
+| ------------------- | --------------------------------- |
+| **Overall tempo**   | Slow burn vs. fast-paced          |
+| **Tension pattern** | Escalating vs. waves              |
+| **Story density**   | Heavy sections vs. light sections |
+| **Player agency**   | Mandatory vs. optional content    |
+
+**Questions:**
+
+- When should tension be highest?
+- Where are the breathing room moments?
+- How much story per gameplay hour?
+
+Describe the pacing for {{game_name}}:"
+
+### 4. Generate Story Content
+
+Based on the conversation, prepare the content:
+
+```markdown
+## Story Beats
+
+### Major Story Beats
+
+{{beats_list_with_descriptions}}
+
+### Beat Placement by Act
+
+**Act 1: Setup**
+{{act1_beats}}
+
+**Act 2: Confrontation**
+{{act2_beats}}
+
+**Act 3: Resolution**
+{{act3_beats}}
+
+---
+
+## Pacing and Flow
+
+### Narrative Tempo
+
+{{pacing_description}}
+
+### Tension Curve
+
+{{tension_pattern}}
+
+### Story Density
+
+{{density_by_section}}
+
+### Key Moments
+
+**Highest tension:** {{peak_moment}}
+**Emotional climax:** {{emotional_peak}}
+**Resolution beat:** {{resolution_moment}}
+```
+
+### 5. Present Content and Menu
+
+Show the generated content to the user and present:
+
+"I've mapped out the story beats and pacing.
+
+**Here's what I'll add to the document:**
+
+[Show the complete markdown content from step 4]
+
+**Validation Check:**
+
+- Are all major moments captured?
+- Does pacing match your vision?
+- Are beats properly distributed?
+
+**Select an Option:**
+[A] Advanced Elicitation - Explore beats and connections
+[P] Party Mode - Get perspectives on pacing
+[C] Continue - Save this and move to Characters (Step 4 of 11)"
+
+### 6. Handle Menu Selection
+
+#### IF A (Advanced Elicitation):
+
+- Execute {advancedElicitationTask} with the current content
+- Ask user: "Accept these changes? (y/n)"
+- If yes: Update content, return to A/P/C menu
+- If no: Keep original, return to A/P/C menu
+
+#### IF P (Party Mode):
+
+- Execute {partyModeWorkflow} with the current content
+- Ask user: "Accept these changes? (y/n)"
+- If yes: Update content, return to A/P/C menu
+- If no: Keep original, return to A/P/C menu
+
+#### IF C (Continue):
+
+- Append the final content to `{outputFile}`
+- Update frontmatter: `stepsCompleted: [1, 2, 3]`
+- Load `{nextStepFile}`
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [story content saved with frontmatter updated], will you then load and read fully `{nextStepFile}`.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- 10-20 story beats identified from user input
+- Beats organized by act/structure
+- Pacing and flow defined
+- Tension curve established
+- A/P/C menu presented and handled correctly
+- Frontmatter updated with stepsCompleted: [1, 2, 3]
+
+### SYSTEM FAILURE:
+
+- Generating beats FOR user
+- Beats not connected to structure
+- Missing pacing considerations
+- Not presenting A/P/C menu after content
+- Proceeding without user selecting 'C'
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.