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

package/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-04-fundamentals.md

@@ -0,0 +1,231 @@
+---
+name: 'step-04-fundamentals'
+description: 'Define core gameplay pillars, mechanics, and player experience goals'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-04-fundamentals.md'
+nextStepFile: '{workflow_path}/steps/step-05-scope.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/game-brief.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Step 4: Game Fundamentals
+
+**Progress: Step 4 of 8** - Next: Scope & Constraints
+
+## STEP GOAL:
+
+Define the core gameplay pillars (fundamental design tenets), primary mechanics (what players do), and player experience goals (what feelings are designed for).
+
+## 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 designer facilitator collaborating with a creative peer
+- Pillars are the "constitution" - everything must serve them
+- Connect mechanics directly to emotional experiences
+
+### Step-Specific Rules:
+
+- Focus on the core of what makes this game unique
+- FORBIDDEN to generate fundamentals without real user input
+- Ensure pillars are specific and measurable
+- Focus on player actions rather than implementation details
+
+## 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
+
+## COLLABORATION MENUS (A/P/C):
+
+- **A (Advanced Elicitation)**: Stress test the fundamentals
+- **P (Party Mode)**: Get perspectives on core design
+- **C (Continue)**: Save the content and proceed
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Core Pillars Discovery
+
+**Guide user through pillar definition:**
+
+"Let's define the core pillars for {{game_name}} - the 2-4 fundamental design tenets that everything must serve.
+
+**Examples of Great Pillars:**
+
+| Game               | Pillars                                                   |
+| ------------------ | --------------------------------------------------------- |
+| **Hollow Knight**  | Tight controls, challenging combat, rewarding exploration |
+| **Celeste**        | Precision movement, accessibility, emotional narrative    |
+| **Dead Cells**     | Mastery, variety, momentum                                |
+| **Stardew Valley** | Relaxation, progression, community                        |
+
+**Questions to consider:**
+
+- If a feature doesn't serve a pillar, should it be in the game?
+- When pillars conflict, which wins?
+
+What are the 2-4 core pillars for {{game_name}}?"
+
+### 2. Primary Mechanics Discovery
+
+**Explore what players actually do:**
+
+"Now let's define what players actually DO in {{game_name}}.
+
+**Think in verbs - what actions define the experience?**
+
+Examples:
+
+- Jump, dash, climb (movement)
+- Attack, dodge, parry (combat)
+- Craft, build, place (creation)
+- Talk, choose, influence (social)
+- Collect, trade, manage (economy)
+
+**Questions to consider:**
+
+- What's the core action players repeat most often?
+- What actions create the most satisfying moments?
+- How do different mechanics interact?
+
+What are the primary mechanics in {{game_name}}?"
+
+### 3. Experience Goals Discovery
+
+**Define the emotional targets:**
+
+"Finally, let's define the player experience goals - what feelings are you designing for?
+
+**Emotional Experience Framework:**
+
+| Emotion                   | Examples                               |
+| ------------------------- | -------------------------------------- |
+| **Tension/Relief**        | Horror games, difficult boss fights    |
+| **Mastery/Growth**        | Skill-based games, RPG progression     |
+| **Creativity/Expression** | Sandbox games, character customization |
+| **Discovery/Surprise**    | Exploration games, mystery narratives  |
+| **Connection/Belonging**  | Multiplayer, community-driven games    |
+| **Relaxation/Flow**       | Cozy games, rhythm games               |
+
+**Questions to consider:**
+
+- What feeling do you want players to have after a session?
+- What emotional journey happens during play?
+- What makes this experience meaningful?
+
+What are the player experience goals for {{game_name}}?"
+
+### 4. Generate Fundamentals Content
+
+Based on the conversation, prepare the content:
+
+```markdown
+## Game Fundamentals
+
+### Core Gameplay Pillars
+
+{{pillars_with_descriptions}}
+
+**Pillar Priority:** When pillars conflict, prioritize:
+{{pillar_priority_order}}
+
+### Primary Mechanics
+
+{{mechanics_list_with_descriptions}}
+
+**Core Loop:** {{how_mechanics_combine_into_loop}}
+
+### Player Experience Goals
+
+{{experience_goals}}
+
+**Emotional Journey:** {{what_players_feel_during_play}}
+```
+
+### 5. Present Content and Menu
+
+Show the generated content to the user and present:
+
+"I've drafted the Game Fundamentals section 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 vision?
+- Do mechanics serve the pillars?
+- Do experience goals match your audience?
+
+**Select an Option:**
+[A] Advanced Elicitation - Stress test these fundamentals
+[P] Party Mode - Get other perspectives on core design
+[C] Continue - Save this and move to Scope & Constraints (Step 5 of 8)"
+
+### 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 [fundamentals content saved with frontmatter updated], will you then load and read fully `{nextStepFile}`.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- 2-4 clear, actionable pillars defined
+- Primary mechanics clearly described
+- Experience goals tied to audience and vision
+- Pillar priority established
+- A/P/C menu presented and handled correctly
+- Frontmatter updated with stepsCompleted: [1, 2, 3, 4]
+
+### SYSTEM FAILURE:
+
+- Generating fundamentals without user input
+- Generic pillars that don't guide decisions
+- Mechanics disconnected from experience 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.

package/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-05-scope.md

@@ -0,0 +1,242 @@
+---
+name: 'step-05-scope'
+description: 'Define project scope including platforms, constraints, and resources'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-05-scope.md'
+nextStepFile: '{workflow_path}/steps/step-06-references.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/game-brief.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Step 5: Scope & Constraints
+
+**Progress: Step 5 of 8** - Next: Reference Framework
+
+## STEP GOAL:
+
+Define realistic project constraints including target platforms, budget considerations, team resources, and technical constraints. Push for realism about scope.
+
+## 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 designer facilitator collaborating with a creative peer
+- Push for realism about constraints
+- Identify potential blockers early
+
+### Step-Specific Rules:
+
+- Focus on establishing realistic boundaries
+- FORBIDDEN to generate scope without real user input
+- Help identify skill gaps and resource assumptions
+- Document constraints that will affect design decisions
+
+## 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
+
+## COLLABORATION MENUS (A/P/C):
+
+- **A (Advanced Elicitation)**: Challenge assumptions about scope
+- **P (Party Mode)**: Get perspectives on feasibility
+- **C (Continue)**: Save the content and proceed
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Platform Discovery
+
+**Guide user through platform selection:**
+
+"Let's define where {{game_name}} will be played.
+
+**Platform Considerations:**
+
+| Platform       | Key Considerations                                      |
+| -------------- | ------------------------------------------------------- |
+| **PC (Steam)** | Keyboard/mouse, largest indie audience, most flexible   |
+| **Console**    | Controller-first, certification, couch play             |
+| **Mobile**     | Touch controls, short sessions, different monetization  |
+| **Web**        | Instant access, file size limits, browser compatibility |
+| **VR**         | Specialized hardware, motion controls, comfort          |
+
+**Questions to consider:**
+
+- Where does your target audience primarily play?
+- Which platform(s) are you targeting for launch?
+- Are there secondary platforms for later?
+
+What platform(s) are you targeting for {{game_name}}?"
+
+### 2. Budget Considerations
+
+**Explore financial constraints:**
+
+"Let's be realistic about budget constraints.
+
+**Budget Categories:**
+
+- **Development costs:** Tools, software, hardware
+- **Asset creation:** Art, audio, music (in-house vs outsource)
+- **Marketing:** Visibility, trailers, press
+- **Platform fees:** Store cuts, devkit costs
+- **External services:** Servers, analytics, localization
+
+**Questions to consider:**
+
+- What's your budget reality? (self-funded, funded, shoestring)
+- What can you create yourself vs need to outsource?
+- Are there areas where budget will limit scope?
+
+What are the budget considerations for {{game_name}}?"
+
+### 3. Team Resources Discovery
+
+**Assess team capabilities:**
+
+"Let's understand what team resources you have.
+
+**Resource Questions:**
+
+- **Team size:** Solo, small team, larger team?
+- **Roles covered:** Design, programming, art, audio, marketing?
+- **Availability:** Full-time, part-time, nights/weekends?
+- **Skill gaps:** What expertise is missing?
+- **Outsourcing:** What might need external help?
+
+What team resources do you have for {{game_name}}?"
+
+### 4. Technical Constraints Discovery
+
+**Identify technical boundaries:**
+
+"Finally, let's identify technical constraints.
+
+**Technical Considerations:**
+
+- **Engine/framework:** Already decided or open?
+- **Performance targets:** Frame rate, file size, load times?
+- **Technical experience:** Team's technical capabilities?
+- **Accessibility:** What accessibility features are required?
+- **Online features:** Multiplayer, leaderboards, cloud saves?
+
+What technical constraints apply to {{game_name}}?"
+
+### 5. Generate Scope Content
+
+Based on the conversation, prepare the content:
+
+```markdown
+## Scope and Constraints
+
+### Target Platforms
+
+**Primary:** {{primary_platform}}
+**Secondary:** {{secondary_platforms}}
+
+### Budget Considerations
+
+{{budget_overview}}
+
+### Team Resources
+
+{{team_composition}}
+
+**Skill Gaps:** {{identified_gaps}}
+
+### Technical Constraints
+
+{{technical_constraints}}
+
+### Scope Realities
+
+{{scope_acknowledgements}}
+```
+
+### 6. Present Content and Menu
+
+Show the generated content to the user and present:
+
+"I've drafted the Scope & Constraints section based on our conversation.
+
+**Here's what I'll add to the document:**
+
+[Show the complete markdown content from step 5]
+
+**Validation Check:**
+
+- Are these constraints realistic?
+- Have we identified potential blockers?
+- Is the scope achievable with these resources?
+
+**Select an Option:**
+[A] Advanced Elicitation - Challenge scope assumptions
+[P] Party Mode - Get perspectives on feasibility
+[C] Continue - Save this and move to Reference Framework (Step 6 of 8)"
+
+### 7. 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 [scope content saved with frontmatter updated], will you then load and read fully `{nextStepFile}`.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- Target platforms clearly defined
+- Budget constraints documented realistically
+- Team resources and gaps identified
+- Technical constraints established
+- A/P/C menu presented and handled correctly
+- Frontmatter updated with stepsCompleted: [1, 2, 3, 4, 5]
+
+### SYSTEM FAILURE:
+
+- Generating scope without user input
+- Unrealistic constraints that set project up for failure
+- Missing critical blockers
+- 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/1-preproduction/game-brief/steps/step-06-references.md

@@ -0,0 +1,224 @@
+---
+name: 'step-06-references'
+description: 'Define inspiration games, competitive analysis, and key differentiators'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-06-references.md'
+nextStepFile: '{workflow_path}/steps/step-07-content.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/game-brief.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Step 6: Reference Framework
+
+**Progress: Step 6 of 8** - Next: Content Framework
+
+## STEP GOAL:
+
+Identify inspiration games (what you're drawing from and NOT taking), analyze competition, and define concrete differentiators that make this game worth making.
+
+## 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 designer facilitator collaborating with a creative peer
+- Challenge "just better" thinking
+- Push for genuine, specific differentiation
+
+### Step-Specific Rules:
+
+- Focus on what makes this game unique
+- FORBIDDEN to generate references without real user input
+- Validate that differentiators are concrete and achievable
+- Understand both what you're taking AND what you're avoiding
+
+## 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, 6]` before loading next step
+
+## COLLABORATION MENUS (A/P/C):
+
+- **A (Advanced Elicitation)**: Challenge differentiation claims
+- **P (Party Mode)**: Get perspectives on uniqueness
+- **C (Continue)**: Save the content and proceed
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Inspiration Games Discovery
+
+**Guide user through references:**
+
+"Let's identify the games that inspire {{game_name}}.
+
+**For each inspiration game, I want to know:**
+
+1. **What game?**
+2. **What are you taking?** (mechanics, feel, art style, structure)
+3. **What are you NOT taking?** (equally important!)
+
+**Example:**
+
+- 'From Hades: the combat feel and build variety'
+- 'NOT from Hades: the roguelike structure or the dialogue system'
+
+What 3-5 games inspire {{game_name}}, and what specifically are you drawing from each?"
+
+### 2. Competitive Analysis Discovery
+
+**Explore the competition:**
+
+"Now let's analyze your competition.
+
+**Competition Questions:**
+
+- **Direct competitors:** Games that scratch the same itch
+- **What they do well:** Why do players love them?
+- **What they do poorly:** Where do they fall short?
+- **Market positioning:** How crowded is this space?
+
+**For {{game_name}}, who are you competing with?**
+
+Remember: if there are no competitors, that might mean there's no market. Some competition is healthy."
+
+### 3. Differentiators Discovery
+
+**Define unique value:**
+
+"Now for the critical question: What makes {{game_name}} genuinely different?
+
+**Differentiation Test:**
+
+A strong differentiator passes ALL of these:
+
+1. Is it concrete and achievable?
+2. Does it matter to your target audience?
+3. Can competitors easily copy it?
+4. Would you still make the game without it?
+
+**Challenge 'just better' thinking:**
+'Better graphics' or 'more content' aren't differentiators - they're expectations.
+
+What 2-4 things make {{game_name}} genuinely different and worth players' attention?"
+
+### 4. Generate References Content
+
+Based on the conversation, prepare the content:
+
+```markdown
+## Reference Framework
+
+### Inspiration Games
+
+{{for_each_inspiration}}
+**{{game_name}}**
+
+- Taking: {{what_taking}}
+- Not Taking: {{what_avoiding}}
+  {{/for_each}}
+
+### Competitive Analysis
+
+**Direct Competitors:**
+{{competitors_list}}
+
+**Competitor Strengths:**
+{{what_they_do_well}}
+
+**Competitor Weaknesses:**
+{{where_they_fall_short}}
+
+### Key Differentiators
+
+{{differentiators_with_descriptions}}
+
+**Unique Value Proposition:**
+{{one_sentence_why_choose_this}}
+```
+
+### 5. Present Content and Menu
+
+Show the generated content to the user and present:
+
+"I've drafted the Reference Framework section based on our conversation.
+
+**Here's what I'll add to the document:**
+
+[Show the complete markdown content from step 4]
+
+**Validation Check:**
+
+- Are differentiators genuine, not just features?
+- Does the competitive analysis reveal opportunity?
+- Are inspirations specific about what you're taking vs avoiding?
+
+**Select an Option:**
+[A] Advanced Elicitation - Challenge differentiation claims
+[P] Party Mode - Get perspectives on uniqueness
+[C] Continue - Save this and move to Content Framework (Step 7 of 8)"
+
+### 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, 6]`
+- Load `{nextStepFile}`
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [references content saved with frontmatter updated], will you then load and read fully `{nextStepFile}`.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- 3-5 inspiration games with specific takeaways
+- Competition analyzed with strengths and weaknesses
+- Differentiators are concrete and achievable
+- Unique value proposition is clear
+- A/P/C menu presented and handled correctly
+- Frontmatter updated with stepsCompleted: [1, 2, 3, 4, 5, 6]
+
+### SYSTEM FAILURE:
+
+- Generating references without user input
+- Generic differentiators like "better gameplay"
+- Missing the "not taking" aspect of inspirations
+- 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.