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

package/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-07-content.md

@@ -0,0 +1,282 @@
+---
+name: 'step-07-content'
+description: 'Define content framework, art/audio direction, and risk assessment'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-07-content.md'
+nextStepFile: '{workflow_path}/steps/step-08-complete.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 7: Content & Production
+
+**Progress: Step 7 of 8** - Next: Final Review
+
+## STEP GOAL:
+
+Define the content framework (world, narrative approach, volume), art and audio direction, and assess key risks with mitigation strategies.
+
+## 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
+- Ensure art/audio vision aligns with budget and team
+- Facilitate honest risk assessment
+
+### Step-Specific Rules:
+
+- Focus on production realities
+- FORBIDDEN to generate content framework without user input
+- Flag content-heavy areas that need planning
+- Prioritize risks by impact and likelihood
+
+## 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, 7]` before loading next step
+
+## COLLABORATION MENUS (A/P/C):
+
+- **A (Advanced Elicitation)**: Deep dive into risks
+- **P (Party Mode)**: Get perspectives on feasibility
+- **C (Continue)**: Save the content and proceed
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. World & Setting Discovery
+
+**Explore the game's world:**
+
+"Let's define the world of {{game_name}}.
+
+**World Questions:**
+
+- **Setting:** Where and when does this take place?
+- **World-building depth:** How much lore matters?
+- **Narrative importance:** Story-driven or story-light?
+- **Atmosphere:** What mood should the world evoke?
+
+Describe the world and setting for {{game_name}}."
+
+### 2. Narrative Approach Discovery
+
+**Define storytelling strategy:**
+
+"How will {{game_name}} handle narrative?
+
+**Narrative Approaches:**
+
+| Approach          | Examples                                  |
+| ----------------- | ----------------------------------------- |
+| **Story-Driven**  | Linear narrative with cutscenes, dialogue |
+| **Environmental** | Story told through world, items, visuals  |
+| **Emergent**      | Player creates their own stories          |
+| **Minimal**       | Pure gameplay, little to no story         |
+
+**Questions:**
+
+- How is story delivered? (cutscenes, dialogue, text, environmental)
+- Is there a dedicated narrative workflow needed later?
+
+What's the narrative approach for {{game_name}}?"
+
+### 3. Art & Audio Direction Discovery
+
+**Establish aesthetic vision:**
+
+"Let's define the look and sound of {{game_name}}.
+
+**Visual Style:**
+
+- Art style (pixel, low-poly, stylized 3D, realistic)
+- Color palette and mood
+- Reference games or images
+- Animation complexity
+
+**Audio Style:**
+
+- Music genre and mood
+- Sound effect approach
+- Voice acting scope (none, grunts, partial, full)
+
+**Production Reality:**
+
+- What can be created in-house?
+- What needs outsourcing?
+- Are asset store/AI tools acceptable?
+
+Describe the art and audio direction for {{game_name}}."
+
+### 4. Risk Assessment Discovery
+
+**Facilitate honest risk evaluation:**
+
+"Now let's honestly assess the risks for {{game_name}}.
+
+**Risk Categories:**
+
+| Category      | Questions                               |
+| ------------- | --------------------------------------- |
+| **Technical** | Unproven systems? Performance concerns? |
+| **Market**    | Saturated genre? Discoverability?       |
+| **Scope**     | Too ambitious? Feature creep?           |
+| **Team**      | Skill gaps? Availability?               |
+| **Financial** | Runway? Unexpected costs?               |
+
+**For each major risk:**
+
+- What could go wrong?
+- How likely is it?
+- What's the impact if it happens?
+- How can we mitigate it?
+
+What are the key risks for {{game_name}}?"
+
+### 5. Generate Content & Production Content
+
+Based on the conversation, prepare the content:
+
+```markdown
+## Content Framework
+
+### World and Setting
+
+{{world_setting_description}}
+
+### Narrative Approach
+
+{{narrative_approach}}
+
+**Story Delivery:** {{how_story_delivered}}
+
+### Content Volume
+
+{{content_volume_estimates}}
+
+---
+
+## Art and Audio Direction
+
+### Visual Style
+
+{{visual_style_description}}
+
+**References:** {{reference_games_or_images}}
+
+### Audio Style
+
+{{audio_direction}}
+
+### Production Approach
+
+{{production_strategy}}
+
+---
+
+## Risk Assessment
+
+### Key Risks
+
+{{prioritized_risk_list}}
+
+### Technical Challenges
+
+{{technical_risks}}
+
+### Market Risks
+
+{{market_risks}}
+
+### Mitigation Strategies
+
+{{mitigation_strategies}}
+```
+
+### 6. Present Content and Menu
+
+Show the generated content to the user and present:
+
+"I've drafted the Content & Production section based on our conversation.
+
+**Here's what I'll add to the document:**
+
+[Show the complete markdown content from step 5]
+
+**Validation Check:**
+
+- Does art/audio align with budget and team?
+- Have we identified the biggest risks?
+- Are mitigations actionable?
+
+**Select an Option:**
+[A] Advanced Elicitation - Deep dive into risks
+[P] Party Mode - Get perspectives on feasibility
+[C] Continue - Save this and move to Final Review (Step 8 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, 6, 7]`
+- Load `{nextStepFile}`
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [content saved with frontmatter updated], will you then load and read fully `{nextStepFile}`.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- World and setting clearly defined
+- Narrative approach documented
+- Art/audio direction established
+- Risks prioritized with mitigations
+- A/P/C menu presented and handled correctly
+- Frontmatter updated with stepsCompleted: [1, 2, 3, 4, 5, 6, 7]
+
+### SYSTEM FAILURE:
+
+- Generating content without user input
+- Art/audio vision misaligned with resources
+- Missing major risk categories
+- 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-08-complete.md

@@ -0,0 +1,296 @@
+---
+name: 'step-08-complete'
+description: 'Define success criteria and complete the game brief with handoff guidance'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-08-complete.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/game-brief.md'
+
+# Workflow References
+gddWorkflow: '{project-root}/_bmad/bmgd/workflows/2-design/gdd/workflow.yaml'
+---
+
+# Step 8: Success & Handoff
+
+**Progress: Step 8 of 8** - Game Brief Complete!
+
+## STEP GOAL:
+
+Define MVP scope, success metrics, immediate next steps, and provide clear handoff guidance for proceeding to GDD creation.
+
+## 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 veteran game designer facilitator collaborating with a creative peer
+- This is the final step - ensure completeness
+- Provide actionable next steps
+
+### Step-Specific Rules:
+
+- Focus on measurable success criteria
+- Push for specificity - challenge vague aspirations
+- Clearly distinguish MVP from full release
+
+## EXECUTION PROTOCOLS:
+
+- Show your analysis before taking any action
+- Generate final sections
+- Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8]`
+- Present completion summary and next steps
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. MVP Definition Discovery
+
+**Define minimum viable product:**
+
+"Let's define the MVP (Minimum Playable Version) for {{game_name}}.
+
+**MVP is the absolute minimum where:**
+
+- Core gameplay loop is fun and complete
+- Only essential content is included
+- It could stand alone as a playable experience
+
+**Questions:**
+
+- What features are absolutely required?
+- What content is the minimum to prove the concept?
+- What can be cut and added later?
+
+What's the MVP for {{game_name}}?"
+
+### 2. Success Metrics Discovery
+
+**Define measurable success:**
+
+"Let's define how you'll measure success for {{game_name}}.
+
+**Metric Categories:**
+
+| Category               | Examples                                |
+| ---------------------- | --------------------------------------- |
+| **Player Acquisition** | Wishlists, downloads, sales             |
+| **Engagement**         | Session length, retention, completion   |
+| **Quality**            | Review scores, bug reports              |
+| **Community**          | Discord members, streamers, fan content |
+| **Financial**          | Revenue, ROI, sustainability            |
+
+**For each metric, answer:** How will you measure that?
+
+What success metrics matter for {{game_name}}?"
+
+### 3. Immediate Actions Discovery
+
+**Identify next steps:**
+
+"What should happen immediately after this brief is complete?
+
+**Common Next Actions:**
+
+- Prototype core mechanic
+- Create art style test
+- Validate technical feasibility
+- Build vertical slice
+- Playtest with target audience
+- Proceed to GDD workflow
+
+**Open Questions:**
+
+- What design questions are still unresolved?
+- What assumptions need validation?
+- What blockers must be resolved?
+
+What are the immediate next steps for {{game_name}}?"
+
+### 4. Generate Executive Summary
+
+**Create summary section:**
+
+Based on all previous sections, synthesize an executive summary:
+
+```markdown
+## Executive Summary
+
+{{game_name}} is {{core_concept}}.
+
+**Target Audience:** {{primary_audience_summary}}
+
+**Core Pillars:** {{pillars_list}}
+
+**Key Differentiators:** {{top_differentiators}}
+
+**Platform:** {{primary_platform}}
+
+**Success Vision:** {{what_success_looks_like}}
+```
+
+### 5. Generate Success & Next Steps Content
+
+Based on the conversation, prepare the content:
+
+```markdown
+## Success Criteria
+
+### MVP Definition
+
+{{mvp_scope}}
+
+### Success Metrics
+
+{{metrics_with_targets}}
+
+### Launch Goals
+
+{{launch_targets}}
+
+---
+
+## Next Steps
+
+### Immediate Actions
+
+{{prioritized_action_list}}
+
+### Research Needs
+
+{{research_requirements}}
+
+### Open Questions
+
+{{unresolved_questions}}
+```
+
+### 6. Present Completion Summary
+
+"**Game Brief Complete!**
+
+{{user_name}}, the Game Brief for **{{game_name}}** is now complete!
+
+**Brief Summary:**
+
+- **Core Concept:** {{core_concept}}
+- **Target Audience:** {{primary_audience}}
+- **Pillars:** {{pillars}}
+- **Platform:** {{platform}}
+
+**Sections Completed:**
+
+1. Game Vision
+2. Target Market
+3. Game Fundamentals
+4. Scope & Constraints
+5. Reference Framework
+6. Content & Production
+7. Success Criteria
+8. Next Steps
+
+**Document saved to:** `{outputFile}`
+
+Do you want to review or adjust anything before we finalize?"
+
+### 7. Present Next Steps Menu
+
+**After user confirms completion:**
+
+"**Recommended Next Steps for {{game_name}}:**
+
+1. **Create GDD** - Transform this brief into a detailed Game Design Document
+   - Command: `create-gdd` (Game Designer agent)
+   - Input: This game brief
+   - Output: Comprehensive GDD
+
+2. **Prototype Core Mechanic** - Validate gameplay before full production
+
+3. **Art Style Test** - Validate visual direction
+
+4. **Market Validation** - Test interest with target audience
+
+**Which would you like to do next?**
+
+1. Start GDD workflow
+2. Review the completed brief
+3. Exit workflow"
+
+### 8. Handle User Selection
+
+Based on user choice:
+
+**If 1 (Start GDD):**
+
+- Update frontmatter with final `stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8]`
+- Provide handoff guidance for GDD workflow
+
+**If 2 (Review):**
+
+- Present full document summary
+- Return to next steps menu
+
+**If 3 (Exit):**
+
+- Update frontmatter with final stepsCompleted
+- Confirm brief is saved
+- Exit workflow gracefully
+
+## CRITICAL STEP COMPLETION NOTE
+
+This is the final step. Ensure:
+
+- Executive summary is generated
+- All content is saved to game-brief.md
+- Frontmatter shows all 8 steps completed
+- User has clear actionable next steps
+- Handoff to GDD workflow is smooth
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- MVP clearly scoped
+- Success metrics are measurable
+- Immediate actions are actionable
+- Executive summary synthesizes the brief
+- Document is complete and saved
+- Clear next steps provided
+- Frontmatter updated with all steps completed
+
+### SYSTEM FAILURE:
+
+- Missing MVP definition
+- Vague success metrics that can't be measured
+- No clear next steps
+- Frontmatter not updated to show completion
+- User left without actionable guidance
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
+
+---
+
+## Game Brief Workflow Complete
+
+The Game Brief workflow transforms a game idea into a validated vision through 8 collaborative steps:
+
+1. **Initialize** - Set up workflow and discover input documents
+2. **Vision** - Capture core concept, pitch, and vision statement
+3. **Market** - Define target audience and market context
+4. **Fundamentals** - Establish pillars, mechanics, and experience goals
+5. **Scope** - Set realistic constraints and resources
+6. **References** - Identify inspirations and differentiators
+7. **Content** - Define world, art/audio, and assess risks
+8. **Complete** - Set success criteria and provide handoff
+
+This step-file architecture ensures consistent, thorough game brief creation with user collaboration at every step.

package/src/modules/bmgd/workflows/1-preproduction/game-brief/workflow.md

@@ -0,0 +1,62 @@
+---
+name: create-game-brief
+description: Creates a comprehensive Game Brief through collaborative step-by-step discovery to capture game vision before detailed design.
+main_config: '{project-root}/_bmad/bmgd/config.yaml'
+web_bundle: true
+---
+
+# Game Brief Workflow
+
+**Goal:** Create comprehensive Game Briefs through collaborative step-by-step discovery to capture and validate the core game vision before detailed design work.
+
+**Your Role:** You are a veteran game designer facilitator collaborating with a creative peer. This is a partnership, not a client-vendor relationship. You bring structured game design thinking and market awareness, while the user brings their game vision and creative ideas. Work together as equals. You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for disciplined execution:
+
+### Core Principles
+
+- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
+- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
+- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
+- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
+- **Append-Only Building**: Build documents by appending content as directed to the output file
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
+5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
+6. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
+
+### Critical Rules (NO EXCEPTIONS)
+
+- NEVER load multiple step files simultaneously
+- ALWAYS read entire step file before execution
+- NEVER skip steps or optimize the sequence
+- ALWAYS update frontmatter of output files when writing the final output for a specific step
+- ALWAYS follow the exact instructions in the step file
+- ALWAYS halt at menus and wait for user input
+- NEVER create mental todo lists from future steps
+- NEVER mention time estimates
+
+---
+
+## INITIALIZATION SEQUENCE
+
+### 1. Configuration Loading
+
+Load and read full config from {main_config} and resolve:
+
+- `project_name`, `output_folder`, `user_name`
+- `communication_language`, `document_output_language`, `user_skill_level`
+- `date` as system-generated current datetime
+
+### 2. First Step EXECUTION
+
+Load, read the full file and then execute `steps/step-01-init.md` to begin the workflow.