bmad-method 6.0.0-alpha.2 → 6.0.0-alpha.21

package/src/modules/bmgd/workflows/2-design/gdd/steps/step-04-vision.md

@@ -0,0 +1,229 @@
+---
+name: 'step-04-vision'
+description: 'Define project goals, context, and unique selling points'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/gdd'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-04-vision.md'
+nextStepFile: '{workflow_path}/steps/step-05-core-gameplay.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/gdd.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Step 4: Goals & Vision
+
+**Progress: Step 4 of 14** - Next: Core Gameplay
+
+## STEP GOAL:
+
+Define the project goals, background context for why this game matters now, and the unique selling points that differentiate this game from others in the market.
+
+## 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
+
+### Role Reinforcement:
+
+- You are a veteran game designer facilitator collaborating with a creative peer
+- We engage in collaborative dialogue, not command-response
+- Vision and USPs are critical for maintaining focus throughout development
+
+### Step-Specific Rules:
+
+- Focus on the "why" behind this game project
+- FORBIDDEN to generate goals/USPs without real user input
+- Help user articulate what makes their game worth making
+- Approach: Challenge assumptions about differentiation
+
+## 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, 4]` before loading next step
+- FORBIDDEN to load next step until C is selected
+
+## COLLABORATION MENUS (A/P/C):
+
+- **A (Advanced Elicitation)**: Dig deeper into goals and differentiation
+- **P (Party Mode)**: Challenge and strengthen the vision with multiple perspectives
+- **C (Continue)**: Save the content to the document and proceed to next step
+
+## CONTEXT BOUNDARIES:
+
+- Game type, platform, and audience from previous steps are available
+- Goals should be achievable and measurable where possible
+- USPs must be genuinely differentiating, not just features
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Goals Discovery
+
+**Guide user through goal definition:**
+
+"Let's define what success looks like for {{game_name}}.
+
+**Types of Goals to Consider:**
+
+| Goal Type         | Examples                                             |
+| ----------------- | ---------------------------------------------------- |
+| **Creative**      | "Create a game that makes players feel powerful"     |
+| **Technical**     | "Ship a stable 60fps experience on target platforms" |
+| **Business**      | "Achieve 10,000 wishlists before launch"             |
+| **Personal**      | "Learn Godot through this project"                   |
+| **Player Impact** | "Create a speedrunning community"                    |
+
+**Questions to consider:**
+
+1. What does success look like for this project?
+2. What would make you proud to have shipped this?
+3. Are there specific metrics you want to hit?
+
+What are your 2-4 main goals for {{game_name}}?"
+
+### 2. Context Discovery
+
+**Guide user through background context:**
+
+"Now let's capture why this game matters right now.
+
+**Context Questions:**
+
+- **Motivation:** What inspired you to make this game?
+- **Timing:** Why is now the right time for this game?
+- **Gap:** What's missing in the market that this fills?
+- **Personal:** What unique perspective or experience do you bring?
+
+Tell me the story behind {{game_name}}. Why are you making this?"
+
+### 3. USP Discovery
+
+**Guide user through unique selling points:**
+
+"Now for the critical question: What makes {{game_name}} different?
+
+**USP Framework:**
+
+A strong USP answers: "Why would someone play THIS game instead of the alternatives?"
+
+**Categories of Differentiation:**
+
+- **Mechanical Innovation:** New gameplay systems or combinations
+- **Narrative/World:** Unique setting, story, or characters
+- **Art/Audio:** Distinctive aesthetic or soundscape
+- **Audience Focus:** Serving an underserved player segment
+- **Technical:** Performance, accessibility, or platform features
+
+**For {{game_type}} games, common USPs include:**
+{typical_usps_for_game_type}
+
+But what's YOUR unique angle?
+
+**Challenge Questions:**
+
+1. If I removed your USP, would the game still be interesting?
+2. Can another developer easily copy this USP?
+3. Does this USP matter to your target audience?
+
+What 2-4 things make {{game_name}} genuinely different?"
+
+### 4. Generate Vision Content
+
+Based on the conversation, prepare the content:
+
+```markdown
+## Goals and Context
+
+### Project Goals
+
+{{goals_list_with_descriptions}}
+
+### Background and Rationale
+
+{{context_narrative}}
+
+---
+
+## Unique Selling Points (USPs)
+
+{{usps_with_descriptions}}
+
+### Competitive Positioning
+
+{{how_this_game_stands_out_in_the_market}}
+```
+
+### 5. Present Content and Menu
+
+Show the generated content to the user and present:
+
+"I've drafted the Goals & Vision sections based on our conversation.
+
+**Here's what I'll add to the document:**
+
+[Show the complete markdown content from step 4]
+
+**Select an Option:**
+[A] Advanced Elicitation - Challenge and strengthen these points
+[P] Party Mode - Get other perspectives on differentiation
+[C] Continue - Save this and move to Core Gameplay (Step 5 of 14)"
+
+### 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, 4]`
+- Load `{nextStepFile}`
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [vision content saved with frontmatter updated], will you then load and read fully `{nextStepFile}`.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- 2-4 clear, achievable goals defined
+- Background context captures the "why"
+- USPs are genuinely differentiating, not just features
+- Competitive positioning is clear
+- A/P/C menu presented and handled correctly
+- Frontmatter updated with stepsCompleted: [1, 2, 3, 4]
+
+### SYSTEM FAILURE:
+
+- Generating generic goals without user input
+- USPs that are just feature lists, not differentiation
+- Not challenging weak USPs
+- Not presenting A/P/C menu after content generation
+- 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/gdd/steps/step-05-core-gameplay.md

@@ -0,0 +1,258 @@
+---
+name: 'step-05-core-gameplay'
+description: 'Define game pillars, core gameplay loop, and win/loss conditions'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/gdd'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-05-core-gameplay.md'
+nextStepFile: '{workflow_path}/steps/step-06-mechanics.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/gdd.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Step 5: Core Gameplay
+
+**Progress: Step 5 of 14** - Next: Game Mechanics
+
+## STEP GOAL:
+
+Define the fundamental gameplay elements: game pillars (core design tenets), the core gameplay loop (what players repeatedly do), and win/loss conditions (how players succeed or fail).
+
+## 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
+
+### Role Reinforcement:
+
+- You are a veteran game designer facilitator collaborating with a creative peer
+- These are GAME-DEFINING decisions - treat them with appropriate weight
+- Every future decision should serve these pillars and loop
+
+### Step-Specific Rules:
+
+- Focus on the heart of the gameplay experience
+- FORBIDDEN to generate pillars/loops without real user input
+- Challenge: Do these pillars and loop serve the stated USPs?
+- Approach: Help user think through the player experience
+
+## 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, 4, 5]` before loading next step
+- FORBIDDEN to load next step until C is selected
+
+## COLLABORATION MENUS (A/P/C):
+
+- **A (Advanced Elicitation)**: Deep dive into the player experience
+- **P (Party Mode)**: Test these fundamentals with multiple perspectives
+- **C (Continue)**: Save the content to the document and proceed to next step
+
+## CONTEXT BOUNDARIES:
+
+- All previous context (type, platform, audience, goals, USPs) available
+- Pillars are the "constitution" that guides all design decisions
+- Core loop is what players do 80% of the time
+- Win/loss conditions provide motivation and stakes
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Game Pillars Discovery
+
+**Guide user through pillar definition:**
+
+"Now we define the core pillars - the fundamental design principles that every feature must serve.
+
+**What are Game Pillars?**
+
+Pillars are 2-4 non-negotiable design tenets. Every mechanic, system, and feature should support at least one pillar. If something doesn't serve a pillar, question whether it belongs.
+
+**Examples of Pillars:**
+
+| Game           | Pillars                                            |
+| -------------- | -------------------------------------------------- |
+| **Dark Souls** | Challenge, Discovery, Consequence                  |
+| **Celeste**    | Tight Controls, Accessibility, Emotional Narrative |
+| **Minecraft**  | Creativity, Exploration, Player Agency             |
+| **Dead Cells** | Mastery, Variety, Momentum                         |
+
+**For your {{game_type}} with USPs of {{usps}}:**
+
+What 2-4 pillars will define every design decision in {{game_name}}?"
+
+### 2. Core Loop Discovery
+
+**Guide user through loop definition:**
+
+"Now let's define the core gameplay loop - the cycle of actions players repeat throughout the game.
+
+**Core Loop Structure:**
+
+A good loop has: **Action -> Feedback -> Reward -> Motivation to repeat**
+
+**Examples:**
+
+| Game          | Core Loop                                                              |
+| ------------- | ---------------------------------------------------------------------- |
+| **Roguelike** | Enter dungeon -> Fight/loot -> Die/extract -> Upgrade -> Enter dungeon |
+| **Puzzle**    | See puzzle -> Analyze -> Attempt -> Succeed/fail -> Next puzzle        |
+| **FPS**       | Engage enemy -> Shoot -> Kill/die -> Respawn/proceed -> Engage         |
+
+**For {{game_type}} games, typical loops include:**
+{typical_loops_for_game_type}
+
+**Questions to consider:**
+
+1. What does the player do most of the time?
+2. What makes each loop iteration feel different from the last?
+3. How long is one loop cycle? (seconds, minutes, hours?)
+
+Describe the core loop for {{game_name}}."
+
+### 3. Win/Loss Conditions Discovery
+
+**Guide user through win/loss definition:**
+
+"Finally, let's define how players succeed and fail.
+
+**Win/Loss Framework:**
+
+| Condition Type | Examples                                                        |
+| -------------- | --------------------------------------------------------------- |
+| **Victory**    | Beat final boss, reach score, complete story, survive time      |
+| **Failure**    | Run out of lives, time expires, resources depleted, story fails |
+| **Soft Fail**  | Lose progress, restart level, dropped loot                      |
+| **No Failure** | Sandbox games, creative tools, walking sims                     |
+
+**Questions to consider:**
+
+1. Is there a definitive "win state" or is success ongoing?
+2. What happens when players fail? How punishing is it?
+3. Are there multiple win/lose conditions (lives AND time)?
+4. Does failure teach the player something?
+
+How do players win and lose in {{game_name}}?"
+
+### 4. Generate Core Gameplay Content
+
+Based on the conversation, prepare the content:
+
+```markdown
+## Core Gameplay
+
+### Game Pillars
+
+{{pillar_list_with_descriptions}}
+
+**Pillar Prioritization:** When pillars conflict, prioritize in this order:
+{{pillar_priority_order}}
+
+### Core Gameplay Loop
+
+{{loop_description}}
+
+**Loop Diagram:**
+{{text_based_loop_visualization}}
+
+**Loop Timing:** {{typical_loop_duration}}
+
+**Loop Variation:** {{what_makes_each_iteration_different}}
+
+### Win/Loss Conditions
+
+#### Victory Conditions
+
+{{win_conditions}}
+
+#### Failure Conditions
+
+{{loss_conditions}}
+
+#### Failure Recovery
+
+{{what_happens_on_failure}}
+```
+
+### 5. Present Content and Menu
+
+Show the generated content to the user and present:
+
+"I've drafted the Core Gameplay sections based on our conversation.
+
+**Here's what I'll add to the document:**
+
+[Show the complete markdown content from step 4]
+
+**Validation Check:**
+
+- Do all pillars support your USPs?
+- Does the core loop deliver on your pillars?
+- Do win/loss conditions create appropriate stakes?
+
+**Select an Option:**
+[A] Advanced Elicitation - Stress test these fundamentals
+[P] Party Mode - Get other perspectives on the core design
+[C] Continue - Save this and move to Game Mechanics (Step 6 of 14)"
+
+### 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, 4, 5]`
+- Load `{nextStepFile}`
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [core gameplay content saved with frontmatter updated], will you then load and read fully `{nextStepFile}`.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- 2-4 clear, actionable pillars defined
+- Pillar prioritization established for conflicts
+- Core loop clearly described with timing and variation
+- Win/loss conditions appropriate for game type
+- Failure recovery explained
+- A/P/C menu presented and handled correctly
+- Frontmatter updated with stepsCompleted: [1, 2, 3, 4, 5]
+
+### SYSTEM FAILURE:
+
+- Generic pillars that don't guide decisions
+- Core loop that doesn't match the game type
+- Generating content without real user input
+- Win/loss conditions misaligned with stated goals
+- Not presenting A/P/C menu after content generation
+- Proceeding without user selecting 'C'
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.