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

package/src/modules/bmgd/workflows/1-preproduction/game-brief/steps/step-01b-continue.md

@@ -0,0 +1,151 @@
+---
+name: 'step-01b-continue'
+description: 'Resume an interrupted Game Brief workflow from the last completed step'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/game-brief.md'
+---
+
+# Step 1B: Workflow Continuation
+
+## STEP GOAL:
+
+Resume the Game Brief workflow from where it was left off, ensuring smooth continuation with full context restoration.
+
+## 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
+- Resume workflow from exact point where it was interrupted
+
+### Step-Specific Rules:
+
+- FOCUS on understanding where we left off and continuing appropriately
+- FORBIDDEN to modify content completed in previous steps
+- Only reload documents that were already tracked in `inputDocuments`
+
+## EXECUTION PROTOCOLS:
+
+- Show your analysis of current state before taking action
+- Keep existing frontmatter `stepsCompleted` values
+- Only load documents that were already tracked in `inputDocuments`
+- FORBIDDEN to discover new input documents during continuation
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Analyze Current State
+
+**State Assessment:**
+Review the frontmatter to understand:
+
+- `stepsCompleted`: Which steps are already done
+- `lastStep`: The most recently completed step number
+- `inputDocuments`: What context was already loaded
+- `documentCounts`: brainstorming, research, notes counts
+- `game_name`: The game name (if set)
+- All other frontmatter variables
+
+### 2. Restore Context Documents
+
+**Context Reloading:**
+
+- For each document in `inputDocuments`, load the complete file
+- This ensures you have full context for continuation
+- Don't discover new documents - only reload what was previously processed
+
+### 3. Present Current Progress
+
+**Progress Report to User:**
+"Welcome back {{user_name}}! I'm resuming our Game Brief collaboration for {{game_name or project_name}}.
+
+**Current Progress:**
+
+- Steps completed: {stepsCompleted}
+- Last worked on: Step {lastStep}
+- Context documents available: {len(inputDocuments)} files
+
+**Document Status:**
+
+- Current Game Brief is ready with all completed sections
+- Ready to continue from where we left off
+
+Does this look right, or do you want to make any adjustments before we proceed?"
+
+### 4. Determine Continuation Path
+
+**Next Step Logic:**
+Based on `lastStep` value, determine which step to load next:
+
+- If `lastStep = 1` -> Load `./step-02-vision.md`
+- If `lastStep = 2` -> Load `./step-03-market.md`
+- If `lastStep = 3` -> Load `./step-04-fundamentals.md`
+- If `lastStep = 4` -> Load `./step-05-scope.md`
+- If `lastStep = 5` -> Load `./step-06-references.md`
+- If `lastStep = 6` -> Load `./step-07-content.md`
+- If `lastStep = 7` -> Load `./step-08-complete.md`
+- If `lastStep = 8` -> Workflow already complete
+
+### 5. Handle Workflow Completion
+
+**If workflow already complete (`lastStep = 8`):**
+"Great news! It looks like we've already completed the Game Brief workflow for {{game_name}}.
+
+The final document is ready at `{outputFile}` with all sections completed.
+
+Would you like me to:
+
+- Review the completed brief with you
+- Suggest next workflow steps (like GDD creation)
+- Start a new brief revision
+
+What would be most helpful?"
+
+### 6. Present MENU OPTIONS
+
+**If workflow not complete:**
+Display: "Ready to continue with Step {nextStepNumber}?
+
+**Select an Option:** [C] Continue to next step"
+
+#### Menu Handling Logic:
+
+- IF C: Load, read entire file, then execute the appropriate next step file based on `lastStep`
+- IF Any other comments or queries: respond and redisplay menu
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [current state confirmed], will you then load and read fully the appropriate next step file to resume the workflow.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- All previous input documents successfully reloaded
+- Current workflow state accurately analyzed and presented
+- User confirms understanding of progress before continuation
+- Correct next step identified and prepared for loading
+
+### SYSTEM FAILURE:
+
+- Discovering new input documents instead of reloading existing ones
+- Modifying content from already completed steps
+- Loading wrong next step based on `lastStep` value
+- Proceeding without user confirmation of current state
+
+**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-02-vision.md

@@ -0,0 +1,218 @@
+---
+name: 'step-02-vision'
+description: 'Define the core game vision including name, concept, pitch, and vision statement'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-02-vision.md'
+nextStepFile: '{workflow_path}/steps/step-03-market.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 2: Game Vision
+
+**Progress: Step 2 of 8** - Next: Target Market
+
+## STEP GOAL:
+
+Capture the core game vision including the working title, one-sentence concept, elevator pitch, and aspirational vision statement that will guide all design decisions.
+
+## 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
+- Vision is the foundation - get it right before moving forward
+- Challenge vague language and elevate compelling ideas
+
+### Step-Specific Rules:
+
+- Focus on crystallizing the game's core identity
+- FORBIDDEN to generate vision without real user input
+- Push for specificity and clarity
+- Reference successful games as examples of good pitches
+
+## 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
+- FORBIDDEN to load next step until C is selected
+
+## COLLABORATION MENUS (A/P/C):
+
+- **A (Advanced Elicitation)**: Dig deeper into the vision
+- **P (Party Mode)**: Get multiple perspectives on the vision
+- **C (Continue)**: Save the content to the document and proceed to next step
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Game Name Discovery
+
+**Start with the basics:**
+
+"Let's start with your game's identity.
+
+**What's the working title for your game?**
+
+(Don't worry if it's not final - working titles help us talk about the game and can always change later.)"
+
+Store in frontmatter: `game_name: '{user_provided_name}'`
+
+### 2. Context Check
+
+**If input documents were loaded:**
+
+"I've reviewed your {brainstorming/research} documents and noticed some interesting ideas:
+
+{summarize_key_themes_from_documents}
+
+Let's use these as a starting point for crystallizing your vision."
+
+### 3. Core Concept Discovery
+
+**Guide user through concept definition:**
+
+"Now let's capture the essence of {{game_name}} in a single sentence.
+
+**Examples of great one-sentence concepts:**
+
+- 'A roguelike deck-builder where you climb a mysterious spire' (Slay the Spire)
+- 'A precision platformer about climbing a mountain and overcoming anxiety' (Celeste)
+- 'A cozy farming sim where you rebuild your grandfather's farm and become part of a small town' (Stardew Valley)
+
+**What is {{game_name}}?** Give me one sentence that captures the core experience."
+
+### 4. Elevator Pitch Discovery
+
+**Build on the concept:**
+
+"Now let's expand that into an elevator pitch - 2-3 sentences that would compel a player or publisher to want to know more.
+
+**A great elevator pitch answers:**
+
+- What is it? (genre, style)
+- What do you do? (core action)
+- What makes it special? (hook)
+
+**Refine this until it hooks attention.** What's your elevator pitch for {{game_name}}?"
+
+### 5. Vision Statement Discovery
+
+**Explore the aspirational vision:**
+
+"Finally, let's capture your aspirational vision - the experience you want to create and what makes it meaningful.
+
+**Questions to consider:**
+
+- What feeling do you want players to have when they put down the controller?
+- What would make this game matter to someone?
+- What's your personal motivation for making this?
+
+**This is your North Star** - ambitious yet achievable. What's your vision for {{game_name}}?"
+
+### 6. Generate Vision Content
+
+Based on the conversation, prepare the content:
+
+```markdown
+## Game Vision
+
+### Core Concept
+
+{{core_concept}}
+
+### Elevator Pitch
+
+{{elevator_pitch}}
+
+### Vision Statement
+
+{{vision_statement}}
+```
+
+### 7. Present Content and Menu
+
+Show the generated content to the user and present:
+
+"I've drafted the Game Vision section 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 core concept capture the essence?
+- Does the pitch hook attention?
+- Does the vision inspire?
+
+**Select an Option:**
+[A] Advanced Elicitation - Refine and strengthen the vision
+[P] Party Mode - Get other perspectives on the vision
+[C] Continue - Save this and move to Target Market (Step 3 of 8)"
+
+### 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]`, `game_name: '{game_name}'`
+- Load `{nextStepFile}`
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [vision content saved with frontmatter updated including game_name], will you then load and read fully `{nextStepFile}`.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- Game name captured and stored in frontmatter
+- Core concept is clear and concise (one sentence)
+- Elevator pitch is compelling (2-3 sentences)
+- Vision statement is aspirational yet achievable
+- A/P/C menu presented and handled correctly
+- Frontmatter updated with stepsCompleted: [1, 2]
+
+### SYSTEM FAILURE:
+
+- Generating vision without user input
+- Core concept is vague or generic
+- Elevator pitch doesn't hook attention
+- 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-03-market.md

@@ -0,0 +1,218 @@
+---
+name: 'step-03-market'
+description: 'Define target audience and market context'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-03-market.md'
+nextStepFile: '{workflow_path}/steps/step-04-fundamentals.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 3: Target Market
+
+**Progress: Step 3 of 8** - Next: Game Fundamentals
+
+## STEP GOAL:
+
+Define the primary and secondary target audiences with specific demographics, and establish the market context including competitive landscape and timing.
+
+## 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 specificity beyond generic descriptions
+- Challenge vague answers like "people who like fun games"
+
+### Step-Specific Rules:
+
+- Focus on who will actually play this game
+- FORBIDDEN to generate audience without real user input
+- Help identify a realistic and reachable audience segment
+- Consider secondary audiences if applicable
+
+## 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)**: Dig deeper into audience insights
+- **P (Party Mode)**: Get multiple perspectives on market positioning
+- **C (Continue)**: Save the content and proceed
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Primary Audience Discovery
+
+**Guide user through audience definition:**
+
+"Let's define who {{game_name}} is really for.
+
+**Primary Audience Questions:**
+
+- **Age range:** Who are you designing for?
+- **Gaming experience:** Casual, core, or hardcore gamers?
+- **Genre familiarity:** Do they know this genre well, or are they new to it?
+- **Play patterns:** When and how do they play? (commute, evening sessions, weekends)
+- **Motivations:** What draws them to games like this?
+
+**Push for specificity:**
+'People who like roguelikes' is too broad. 'Experienced roguelike fans who want deeper deckbuilding strategy' is better.
+
+Who is your primary audience for {{game_name}}?"
+
+### 2. Secondary Audience Discovery
+
+**Explore additional audiences:**
+
+"Are there secondary audiences who might enjoy {{game_name}}?
+
+**Examples:**
+
+- Primary: Hardcore roguelike fans → Secondary: Strategy game players looking for something new
+- Primary: Cozy game fans → Secondary: Burnt-out competitive gamers seeking relaxation
+
+**If you have a secondary audience:**
+
+- How do their needs differ from primary?
+- What features might appeal specifically to them?
+
+Do you have a secondary audience in mind?"
+
+### 3. Market Context Discovery
+
+**Explore the competitive landscape:**
+
+"Let's understand the market context for {{game_name}}.
+
+**Market Questions:**
+
+- **Similar successful games:** What games have proven there's an audience?
+- **Market gaps:** What's missing that {{game_name}} could fill?
+- **Timing:** Why is now the right time for this game?
+- **Competition:** Who are you competing with for player attention?
+- **Discoverability:** How will players find your game?
+
+What does the market look like for {{game_name}}?"
+
+### 4. Generate Market Content
+
+Based on the conversation, prepare the content:
+
+```markdown
+## Target Market
+
+### Primary Audience
+
+{{primary_audience_description}}
+
+**Demographics:**
+{{demographics}}
+
+**Gaming Preferences:**
+{{gaming_preferences}}
+
+**Motivations:**
+{{what_draws_them}}
+
+### Secondary Audience
+
+{{secondary_audience_description}}
+
+### Market Context
+
+{{market_context_analysis}}
+
+**Similar Successful Games:**
+{{comparable_titles}}
+
+**Market Opportunity:**
+{{why_now}}
+```
+
+### 5. Present Content and Menu
+
+Show the generated content to the user and present:
+
+"I've drafted the Target Market section based on our conversation.
+
+**Here's what I'll add to the document:**
+
+[Show the complete markdown content from step 4]
+
+**Validation Check:**
+
+- Is the primary audience specific enough to guide design decisions?
+- Does the market context support the viability of this game?
+
+**Select an Option:**
+[A] Advanced Elicitation - Dig deeper into market insights
+[P] Party Mode - Get perspectives on market positioning
+[C] Continue - Save this and move to Game Fundamentals (Step 4 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]`
+- Load `{nextStepFile}`
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [market content saved with frontmatter updated], will you then load and read fully `{nextStepFile}`.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- Primary audience is specific and well-defined
+- Secondary audience considered (even if none exists)
+- Market context provides business rationale
+- A/P/C menu presented and handled correctly
+- Frontmatter updated with stepsCompleted: [1, 2, 3]
+
+### SYSTEM FAILURE:
+
+- Generating audience without user input
+- Audience is too vague to guide decisions
+- 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.