ros/BMAD-METHOD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

remaining bmm workflows bloat removed

Browse Source
This commit is contained in:
Brian Madison
2025-10-16 08:58:09 -05:00
parent e77a1c036b
commit 790c4cedf4
19 changed files with 197 additions and 341 deletions
Download Patch File Download Diff File Expand all files Collapse all files

210
src/modules/bmm/workflows/2-plan-workflows/gdd/instructions-gdd.md
View File

@@ -124,74 +124,45 @@ Get core game concept and vision.
<step n="2" goal="Define platforms and target audience">
<ask>What platform(s) are you targeting?
- Desktop (Windows/Mac/Linux)
- Mobile (iOS/Android)
- Web (Browser-based)
- Console (which consoles?)
- Multiple platforms
Your answer:</ask>
<action>Guide user to specify target platform(s) for their game, exploring considerations like desktop, mobile, web, console, or multi-platform deployment</action>
<template-output>platforms</template-output>
<ask>Who is your target audience?
Consider:
- Age range
- Gaming experience level (casual, core, hardcore)
- Genre familiarity
- Play session length preferences
Your answer:</ask>
<action>Guide user to define their target audience with specific demographics: age range, gaming experience level (casual/core/hardcore), genre familiarity, and preferred play session lengths</action>
<template-output>target_audience</template-output>
</step>
<step n="3" goal="Define goals and context">
<step n="3" goal="Define goals, context, and unique selling points">
**Goal Guidelines based on project level:**
- Level 0-1: 1-2 primary goals
- Level 2: 2-3 primary goals
- Level 3-4: 3-5 strategic goals
<action>Guide user to define project goals appropriate for their level (Level 0-1: 1-2 goals, Level 2: 2-3 goals, Level 3-4: 3-5 strategic goals) - what success looks like for this game</action>
<template-output>goals</template-output>
Brief context on why this game matters now.
<action>Guide user to provide context on why this game matters now - the motivation and rationale behind the project</action>
<template-output>context</template-output>
<action>Guide user to identify the unique selling points (USPs) - what makes this game different from existing games in the market</action>
<template-output>unique_selling_points</template-output>
</step>
<step n="4" goal="Core gameplay definition">
<critical>These are game-defining decisions</critical>
<ask>What are the core game pillars (2-4 fundamental gameplay elements)?
Examples:
- Tight controls + challenging combat + rewarding exploration
- Strategic depth + replayability + quick sessions
- Narrative + atmosphere + player agency
Your game pillars:</ask>
<action>Guide user to identify 2-4 core game pillars - the fundamental gameplay elements that define their game's experience (e.g., tight controls + challenging combat + rewarding exploration, or strategic depth + replayability + quick sessions)</action>
<template-output>game_pillars</template-output>
<ask>Describe the core gameplay loop (what the player does repeatedly):
Example: "Player explores level → encounters enemies → defeats enemies with abilities → collects resources → upgrades abilities → explores deeper"
Your gameplay loop:</ask>
<action>Guide user to describe the core gameplay loop - what actions the player repeats throughout the game, creating a clear cyclical pattern of player behavior and rewards</action>
<template-output>gameplay_loop</template-output>
<ask>How does the player win? How do they lose?</ask>
<action>Guide user to define win and loss conditions - how the player succeeds and fails in the game</action>
<template-output>win_loss_conditions</template-output>
@@ -199,19 +170,12 @@ Your gameplay loop:</ask>
<step n="5" goal="Game mechanics and controls">
Define the primary game mechanics.
<action>Guide user to define the primary game mechanics that players will interact with throughout the game</action>
<template-output>primary_mechanics</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<ask>Describe the control scheme and input method:
- Keyboard + Mouse
- Gamepad
- Touch screen
- Other
Include key bindings or button layouts if known.</ask>
<action>Guide user to describe their control scheme and input method (keyboard/mouse, gamepad, touchscreen, etc.), including key bindings or button layouts if known</action>
<template-output>controls</template-output>
@@ -233,29 +197,15 @@ For each {{placeholder}} in the fragment, elicit and capture that information.
<step n="7" goal="Progression and balance">
<ask>How does player progression work?
- Skill-based (player gets better)
- Power-based (character gets stronger)
- Unlock-based (new abilities/areas)
- Narrative-based (story progression)
- Combination
Describe:</ask>
<action>Guide user to describe how player progression works in their game - whether through skill improvement, power gains, ability unlocking, narrative advancement, or a combination of approaches</action>
<template-output>player_progression</template-output>
<ask>Describe the difficulty curve:
- How does difficulty increase?
- Pacing (steady, spikes, player-controlled?)
- Accessibility options?</ask>
<action>Guide user to define the difficulty curve: how challenge increases over time, pacing rhythm (steady/spikes/player-controlled), and any accessibility options planned</action>
<template-output>difficulty_curve</template-output>
<ask optional="true">Is there an in-game economy or resource system?
Skip if not applicable.</ask>
<action>Ask if the game includes an in-game economy or resource system, and if so, guide user to describe it (skip if not applicable)</action>
<template-output>economy_resources</template-output>
@@ -263,26 +213,11 @@ Skip if not applicable.</ask>
<step n="8" goal="Level design framework">
<ask>What types of levels/stages does your game have?
Examples:
- Tutorial, early levels, mid-game, late-game, boss arenas
- Biomes/themes
- Procedural vs. handcrafted
Describe:</ask>
<action>Guide user to describe the types of levels/stages in their game (e.g., tutorial, themed biomes, boss arenas, procedural vs. handcrafted, etc.)</action>
<template-output>level_types</template-output>
<ask>How do levels progress or unlock?
- Linear sequence
- Hub-based
- Open world
- Player choice
Describe:</ask>
<action>Guide user to explain how levels progress or unlock - whether through linear sequence, hub-based structure, open world exploration, or player-driven choices</action>
<template-output>level_progression</template-output>
@@ -290,23 +225,11 @@ Describe:</ask>
<step n="9" goal="Art and audio direction">
<ask>Describe the art style:
- Visual aesthetic (pixel art, low-poly, realistic, stylized, etc.)
- Color palette
- Inspirations or references
Your vision:</ask>
<action>Guide user to describe their art style vision: visual aesthetic (pixel art, low-poly, realistic, stylized), color palette preferences, and any inspirations or references</action>
<template-output>art_style</template-output>
<ask>Describe audio and music direction:
- Music style/genre
- Sound effect tone
- Audio importance to gameplay
Your vision:</ask>
<action>Guide user to describe their audio and music direction: music style/genre, sound effect tone, and how important audio is to the gameplay experience</action>
<template-output>audio_music</template-output>
@@ -314,38 +237,15 @@ Your vision:</ask>
<step n="10" goal="Technical specifications">
<ask>What are the performance requirements?
Consider:
- Target frame rate
- Resolution
- Load times
- Battery life (mobile)
Requirements:</ask>
<action>Guide user to define performance requirements: target frame rate, resolution, acceptable load times, and mobile battery considerations if applicable</action>
<template-output>performance_requirements</template-output>
<ask>Any platform-specific considerations?
- Mobile: Touch controls, screen sizes
- PC: Keyboard/mouse, settings
- Console: Controller, certification
- Web: Browser compatibility, file size
Platform details:</ask>
<action>Guide user to identify platform-specific considerations (mobile touch controls/screen sizes, PC keyboard/mouse/settings, console controller/certification, web browser compatibility/file size)</action>
<template-output>platform_details</template-output>
<ask>What are the key asset requirements?
- Art assets (sprites, models, animations)
- Audio assets (music, SFX, voice)
- Estimated asset counts/sizes
- Asset pipeline needs
Asset requirements:</ask>
<action>Guide user to document key asset requirements: art assets (sprites/models/animations), audio assets (music/SFX/voice), estimated counts/sizes, and asset pipeline needs</action>
<template-output>asset_requirements</template-output>
@@ -353,14 +253,7 @@ Asset requirements:</ask>
<step n="11" goal="Epic structure">
<action>Translate game features into development epics</action>
**Epic Guidelines based on project level:**
- Level 1: 1 epic with 1-10 stories
- Level 2: 1-2 epics with 5-15 stories total
- Level 3: 2-5 epics with 12-40 stories
- Level 4: 5+ epics with 40+ stories
<action>Work with user to translate game features into development epics, following level-appropriate guidelines (Level 1: 1 epic/1-10 stories, Level 2: 1-2 epics/5-15 stories, Level 3: 2-5 epics/12-40 stories, Level 4: 5+ epics/40+ stories)</action>
<template-output>epics</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
@@ -373,19 +266,16 @@ Asset requirements:</ask>
<critical>Create separate epics.md with full story hierarchy</critical>
<action>Generate epic overview section with all epics listed</action>
<template-output file="epics.md">epic_overview</template-output>
<action>For each epic, generate detailed breakdown with expanded goals, capabilities, and success criteria</action>
<action>For each epic, generate all stories in user story format with prerequisites, acceptance criteria (3-8 per story), and high-level technical notes</action>
<for-each epic="epic_list">
Generate Epic {{epic_number}} with expanded goals, capabilities, success criteria.
Generate all stories with:
- User story format
- Prerequisites
- Acceptance criteria (3-8 per story)
- Technical notes (high-level only)
<template-output file="epics.md">epic\_{{epic_number}}\_details</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
@@ -394,29 +284,11 @@ Generate all stories with:
</step>
<step n="13" goal="Success metrics">
<ask>What technical metrics will you track?
Examples:
- Frame rate consistency
- Load times
- Crash rate
- Memory usage
Your metrics:</ask>
<action>Guide user to identify technical metrics they'll track (e.g., frame rate consistency, load times, crash rate, memory usage)</action>
<template-output>technical_metrics</template-output>
<ask>What gameplay metrics will you track?
Examples:
- Player completion rate
- Average session length
- Difficulty pain points
- Feature engagement
Your metrics:</ask>
<action>Guide user to identify gameplay metrics they'll track (e.g., player completion rate, session length, difficulty pain points, feature engagement)</action>
<template-output>gameplay_metrics</template-output>
@@ -424,15 +296,19 @@ Your metrics:</ask>
<step n="14" goal="Document out of scope and assumptions">
<action>Guide user to document what is explicitly out of scope for this game - features, platforms, or content that won't be included in this version</action>
<template-output>out_of_scope</template-output>
<action>Guide user to document key assumptions and dependencies - technical assumptions, team capabilities, third-party dependencies, or external factors the project relies on</action>
<template-output>assumptions_and_dependencies</template-output>
</step>
<step n="15" goal="Generate solutioning handoff and next steps">
<action>Check if game-type fragment contained narrative tags</action>
<action>Check if game-type fragment contained narrative tags indicating narrative importance</action>
<check if="fragment had <narrative-workflow-critical> or <narrative-workflow-recommended>">
<action>Set needs_narrative = true</action>
@@ -443,15 +319,9 @@ Your metrics:</ask>
</check>
<check if="needs_narrative == true">
<ask>This game type ({{game_type}}) is **{{narrative_importance}}** for narrative.
<action>Inform user that their game type benefits from narrative design, presenting the option to create a Narrative Design Document covering story structure, character arcs, world lore, dialogue framework, and environmental storytelling</action>
Your game would benefit from a Narrative Design Document to detail:
- Story structure and beats
- Character profiles and arcs
- World lore and history
- Dialogue framework
- Environmental storytelling
<ask>This game type ({{game_type}}) benefits from narrative design.
Would you like to create a Narrative Design Document now?

6
src/modules/bmm/workflows/3-solutioning/instructions.md
View File

@@ -5,6 +5,10 @@ This workflow generates scale-adaptive solution architecture documentation that
```xml
<workflow name="solution-architecture">
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language}</critical>
<step n="0" goal="Load project analysis, validate prerequisites, and scale assessment">
<action>
1. Search {output_folder}/ for files matching pattern: bmm-workflow-status.md
@@ -765,7 +769,7 @@ Add entries for all generated tech specs
</action>
<ask>
**Phase 3 (Solutioning) Complete!**
**Phase 3 (Solutioning) Complete, {user_name}!**
✅ Solution architecture generated
✅ Cohesion check passed

5
src/modules/bmm/workflows/3-solutioning/tech-spec/instructions.md
View File

@@ -3,6 +3,7 @@
````xml
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language}</critical>
<critical>This workflow generates a comprehensive Technical Specification from PRD and Architecture, including detailed design, NFRs, acceptance criteria, and traceability mapping.</critical>
<critical>Default execution mode: #yolo (non-interactive). If required inputs cannot be auto-discovered and {{non_interactive}} == true, HALT with a clear message listing missing documents; do not prompt.</critical>
@@ -149,7 +150,7 @@ What would you like to do?</ask>
<template-output file="{{status_file_path}}">planned_workflow</template-output>
<action>Mark "tech-spec (Epic {{epic_id}})" as complete in the planned workflow table</action>
<output>**✅ Tech Spec Generated Successfully**
<output>**✅ Tech Spec Generated Successfully, {user_name}!**
**Epic Details:**
- Epic ID: {{epic_id}}
@@ -172,7 +173,7 @@ What would you like to do?</ask>
</check>
<check if="status file not found">
<output>**✅ Tech Spec Generated Successfully**
<output>**✅ Tech Spec Generated Successfully, {user_name}!**
**Epic Details:**
- Epic ID: {{epic_id}}

21
src/modules/bmm/workflows/3-solutioning/tech-spec/workflow.yaml
View File

@@ -25,27 +25,6 @@ validation: "{installed_path}/checklist.md"
# Output configuration
default_output_file: "{project-root}/docs/tech-spec-epic-{{epic_id}}.md"
# Required tools
required_tools:
- list_files
- file_info
- read_file
- write_file
- search_repo
- glob
- parse_markdown
tags:
- tech-spec
- architecture
- planning
- bmad-v6
execution_hints:
interactive: false
autonomous: true
iterative: true
# Variables
variables:
non_interactive: true

3
src/modules/bmm/workflows/4-implementation/correct-course/instructions.md
View File

@@ -2,6 +2,7 @@
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project-root}/bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language}</critical>
<workflow>
@@ -189,7 +190,7 @@
- Specific edit proposals with before/after
- Implementation handoff plan
<action>Report workflow completion to user</action>
<action>Report workflow completion to user with personalized message: "✅ Correct Course workflow complete, {user_name}!"</action>
<action>Remind user of success criteria and next steps for implementation team</action>
</step>

5
src/modules/bmm/workflows/4-implementation/create-story/instructions.md
View File

@@ -3,6 +3,7 @@
````xml
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language}</critical>
<critical>This workflow creates or updates the next user story from epics/PRD and architecture context, saving to the configured stories directory and optionally invoking Story Context.</critical>
<critical>Default execution mode: #yolo (minimal prompts). Only elicit if absolutely required and {{non_interactive}} == false.</critical>
@@ -143,7 +144,7 @@
- **{{date}}**: Completed create-story for Story {{story_id}} ({{story_title}}). Story file: {{story_file}}. Status: Draft (needs review via story-ready). Next: Review and approve story.
```
<output>**✅ Story Created Successfully**
<output>**✅ Story Created Successfully, {user_name}!**
**Story Details:**
- Story ID: {{story_id}}
@@ -164,7 +165,7 @@ Check status anytime with: `workflow-status`
</check>
<check if="status file not found">
<output>**✅ Story Created Successfully**
<output>**✅ Story Created Successfully, {user_name}!**
**Story Details:**
- Story ID: {{story_id}}

19
src/modules/bmm/workflows/4-implementation/create-story/workflow.yaml
View File

@@ -39,28 +39,9 @@ variables:
# Output configuration
default_output_file: "{story_dir}/story-{{epic_num}}.{{story_num}}.md"
required_tools:
- list_files
- file_info
- read_file
- write_file
- create_directory
- search_repo
- glob
recommended_inputs:
- epics: "Epic breakdown (epics.md)"
- prd: "PRD document"
- solution-architecture: "Solution Architecture (optional)"
tags:
- story-generation
- planning
- bmad-v6
execution_hints:
interactive: false # Minimize prompts; intended to run to completion
autonomous: true # Proceed without user input unless blocked
iterative: true
web_bundle: false

5
src/modules/bmm/workflows/4-implementation/dev-story/instructions.md
View File

@@ -3,6 +3,7 @@
````xml
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language}</critical>
<critical>Only modify the story file in these areas: Tasks/Subtasks checkboxes, Dev Agent Record (Debug Log, Completion Notes), File List, Change Log, and Status</critical>
<critical>Execute ALL steps in exact order; do NOT skip steps</critical>
<critical>If {{run_until_complete}} == true, run non-interactively: do not pause between steps unless a HALT condition is reached or explicit user approval is required for unapproved dependencies.</critical>
@@ -131,7 +132,7 @@
- **{{date}}**: Completed dev-story for Story {{current_story_id}} ({{current_story_title}}). All tasks complete, tests passing. Story status: Ready for Review. Next: User reviews and runs story-approved when satisfied with implementation.
```
<output>**✅ Story Implementation Complete**
<output>**✅ Story Implementation Complete, {user_name}!**
**Story Details:**
- Story ID: {{current_story_id}}
@@ -153,7 +154,7 @@ Or check status anytime with: `workflow-status`
</check>
<check if="status file not found">
<output>**✅ Story Implementation Complete**
<output>**✅ Story Implementation Complete, {user_name}!**
**Story Details:**
- Story ID: {{current_story_id}}

21
src/modules/bmm/workflows/4-implementation/dev-story/workflow.yaml
View File

@@ -31,25 +31,4 @@ variables:
recommended_inputs:
- story_markdown: "Path to the story markdown file (Tasks/Subtasks, Acceptance Criteria present)"
# Required tools (conceptual; executor should provide equivalents)
required_tools:
- read_file
- write_file
- search_repo
- run_tests
- list_files
- file_info
tags:
- development
- story-execution
- tests
- validation
- bmad-v6
execution_hints:
interactive: false # Minimize prompts; intended to run to completion
autonomous: true # Proceed without user input unless blocked
iterative: true
web_bundle: false

3
src/modules/bmm/workflows/4-implementation/retrospective/instructions.md
View File

@@ -2,6 +2,7 @@
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project-root}/bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language}</critical>
<critical>
FACILITATION NOTES:
@@ -447,7 +448,7 @@ Check status anytime with: `workflow-status`
</check>
<check if="status file not found">
<output>**✅ Retrospective Complete**
<output>**✅ Retrospective Complete, {user_name}!**
**Epic Review:**

5
src/modules/bmm/workflows/4-implementation/review-story/instructions.md
View File

@@ -3,6 +3,7 @@
````xml
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language}</critical>
<critical>This workflow performs a Senior Developer Review on a story flagged Ready for Review, appends structured review notes, and can update the story status based on the outcome.</critical>
<critical>Default execution mode: #yolo (non-interactive). Only ask if {{non_interactive}} == false. If auto-discovery of the target story fails, HALT with a clear message to provide 'story_path' or 'story_dir'.</critical>
<critical>Only modify the story file in these areas: Status (optional per settings), Dev Agent Record (Completion Notes), File List (if corrections are needed), Change Log, and the appended "Senior Developer Review (AI)" section at the end of the document.</critical>
@@ -222,7 +223,7 @@ What would you like to do?</ask>
- **{{date}}**: Completed review-story for Story {{epic_num}}.{{story_num}}. Review outcome: {{outcome}}. Action items: {{action_item_count}}. Next: Address review feedback if needed, then continue with story-approved when ready.
```
<output>**✅ Story Review Complete**
<output>**✅ Story Review Complete, {user_name}!**
**Story Details:**
- Story: {{epic_num}}.{{story_num}}
@@ -243,7 +244,7 @@ Check status anytime with: `workflow-status`
</check>
<check if="status file not found">
<output>**✅ Story Review Complete**
<output>**✅ Story Review Complete, {user_name}!**
**Story Details:**
- Story: {{epic_num}}.{{story_num}}

25
src/modules/bmm/workflows/4-implementation/review-story/workflow.yaml
View File

@@ -60,29 +60,4 @@ recommended_inputs:
- tech_spec: "Epic technical specification document (auto-discovered if omitted)"
- story_context: "Story Context XML path (auto-discovered if omitted)"
# Required tools (conceptual; executor should provide equivalents)
required_tools:
- list_files
- file_info
- read_file
- write_file
- search_repo
- parse_markdown
- glob
- mcp_doc_search # Use available MCP servers to search docs/best-practices
- web_search # Fallback research
- read_url # Fetch references
tags:
- review
- code-review
- quality
- testing
- bmad-v6
execution_hints:
interactive: false # Minimize prompts; intended to run deterministically
autonomous: true # Proceed without user input unless blocked
iterative: true
web_bundle: false

6
src/modules/bmm/workflows/4-implementation/story-approved/instructions.md
View File

@@ -1,5 +1,9 @@
# Story Approved Workflow Instructions (DEV Agent)
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language}</critical>
<workflow>
<critical>This workflow is run by DEV agent AFTER user confirms a story is approved (Definition of Done is complete)</critical>
@@ -215,7 +219,7 @@ If BACKLOG had 1 story and is now empty:
<action>Display summary</action>
**Story Approved and Marked Done!**
**Story Approved and Marked Done, {user_name}!**
✅ Story file updated: `{{current_story_file}}` → Status: Done
✅ Status file updated: Story moved IN PROGRESS → DONE

15
src/modules/bmm/workflows/4-implementation/story-approved/workflow.yaml
View File

@@ -23,19 +23,4 @@ variables:
# Output configuration - no output file, just status updates
default_output_file: ""
required_tools:
- read_file
- edit_file
tags:
- story-management
- status-update
- dev-agent
- bmad-v6
execution_hints:
interactive: false # Minimal prompts; quick status update
autonomous: true # Proceed without user input
iterative: false # Single-pass workflow
web_bundle: false

5
src/modules/bmm/workflows/4-implementation/story-context/instructions.md
View File

@@ -3,6 +3,7 @@
````xml
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language}</critical>
<critical>This workflow assembles a Story Context XML for a single user story by extracting ACs, tasks, relevant docs/code, interfaces, constraints, and testing guidance to support implementation.</critical>
<critical>Default execution mode: #yolo (non-interactive). Only ask if {{non_interactive}} == false. If auto-discovery fails, HALT and request 'story_path' or 'story_dir'.</critical>
@@ -168,7 +169,7 @@ What would you like to do?</ask>
- **{{date}}**: Completed story-context for Story {{story_id}} ({{story_title}}). Context file: {{default_output_file}}. Next: DEV agent should run dev-story to implement.
```
<output>**✅ Story Context Generated Successfully**
<output>**✅ Story Context Generated Successfully, {user_name}!**
**Story Details:**
- Story ID: {{story_id}}
@@ -189,7 +190,7 @@ Check status anytime with: `workflow-status`
</check>
<check if="status file not found">
<output>**✅ Story Context Generated Successfully**
<output>**✅ Story Context Generated Successfully, {user_name}!**
**Story Details:**
- Story ID: {{story_id}}

22
src/modules/bmm/workflows/4-implementation/story-context/workflow.yaml
View File

@@ -33,26 +33,4 @@ default_output_file: "{story_dir}/story-context-{{epic_id}}.{{story_id}}.xml"
recommended_inputs:
- story_markdown: "Path to a story markdown file to build context for"
# Required tools
required_tools:
- list_files
- file_info
- read_file
- write_file
- create_directory
- glob
- search_repo
- parse_markdown
tags:
- context
- story
- planning
- bmad-v6
execution_hints:
interactive: false
autonomous: true
iterative: true
web_bundle: false

6
src/modules/bmm/workflows/4-implementation/story-ready/instructions.md
View File

@@ -1,5 +1,9 @@
# Story Ready Workflow Instructions (SM Agent)
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language}</critical>
<workflow>
<critical>This workflow is run by SM agent AFTER user reviews a drafted story and confirms it's ready for development</critical>
@@ -128,7 +132,7 @@ If BACKLOG had 1 story and is now empty:
<action>Display summary</action>
**Story Marked Ready for Development!**
**Story Marked Ready for Development, {user_name}!**
✅ Story file updated: `{{todo_story_file}}` → Status: Ready
✅ Status file updated: Story moved TODO → IN PROGRESS

15
src/modules/bmm/workflows/4-implementation/story-ready/workflow.yaml
View File

@@ -23,19 +23,4 @@ variables:
# Output configuration - no output file, just status updates
default_output_file: ""
required_tools:
- read_file
- edit_file
tags:
- story-management
- status-update
- sm-agent
- bmad-v6
execution_hints:
interactive: false # Minimal prompts; quick status update
autonomous: true # Proceed without user input
iterative: false # Single-pass workflow
web_bundle: false

141
workflow-cleanup-progress.md
View File

@@ -105,25 +105,21 @@ date: system-generated
### Progress:
- Status: ⚙️ IN PROGRESS
- Workflows Completed: 14/35 (40%)
- Workflows Completed: 26/35 (74%)
### Completed Workflows:
**CIS Module (4/4 - 100% complete):**
See detailed completion logs below for:
1. ✅ storytelling - Fixed: removed use_advanced_elicitation bloat, removed duplicate story_frameworks, fixed web_bundle filename (story-frameworks.csv → story-types.csv), added missing {{resolution}} template-output, added {communication_language} and {user_name} usage
2. ✅ problem-solving - Fixed: removed use_advanced_elicitation bloat, removed duplicate solving_methods
3. ✅ design-thinking - Fixed: removed use_advanced_elicitation bloat, removed duplicate design_methods
4. ✅ innovation-strategy - Fixed: removed use_advanced_elicitation bloat, removed duplicate innovation_frameworks
- **CIS Module:** 4/4 workflows (100%)
- **BMM 1-analysis:** 7/7 workflows (100%) - including metadata bloat cleanup
- **BMM 2-plan-workflows:** 5/5 workflows (100%) - including GDD intent-based transformation
- **BMM 3-solutioning:** 2/2 workflows (100%) - metadata bloat cleanup + critical headers
- **BMM 4-implementation:** 8/8 workflows (100%) - metadata bloat cleanup + critical headers
**BMM Module (2/30 fully audited, 8/30 surface cleaned):** 5. ✅ **brainstorm-game** - FULL AUDIT: removed use_advanced_elicitation bloat, restored existing_workflows (critical), added {communication_language} and {user_name} 6. ✅ **brainstorm-project** - FULL AUDIT: removed use_advanced_elicitation bloat, restored existing_workflows (critical), added {communication_language} and {user_name} 7. ⚠️ game-brief - Surface clean only: removed use_advanced_elicitation bloat (needs full audit) 8. ⚠️ product-brief - Surface clean only: removed use_advanced_elicitation bloat (needs full audit) 9. ⚠️ research - Surface clean only: removed use_advanced_elicitation bloat (needs full audit) 10. ⚠️ gdd - Surface clean only: removed use_advanced_elicitation bloat (needs full audit) 11. ⚠️ narrative - Surface clean only: removed use_advanced_elicitation bloat (needs full audit) 12. ⚠️ prd - Surface clean only: removed use_advanced_elicitation bloat (needs full audit) 13. ⚠️ tech-spec (2-plan) - Surface clean only: removed use_advanced_elicitation bloat (needs full audit) 14. ⚠️ ux - Surface clean only: removed use_advanced_elicitation bloat (needs full audit)
### Remaining Work:
**Common Issues Found:**
- `use_advanced_elicitation: true` bloat in web_bundle (not used in instructions) - Fixed in 14 workflows (4 CIS + 10 BMM)
- Duplicate data file variables between top-level and web_bundle - Fixed in 4 CIS workflows
- Missing template-output tags for template variables - Fixed in storytelling (1)
- Underutilization of {communication_language} and {user_name} config variables - Enhanced in storytelling (1)
- **BMB:** 0/8 workflows (0%)
---
@@ -219,12 +215,16 @@ date: system-generated
All 5 workflows in the 2-plan-workflows folder have been audited, cleaned, and optimized:
1. ✅ **gdd** - YAML CLEANUP + CRITICAL HEADERS
1. ✅ **gdd** - YAML CLEANUP + CRITICAL HEADERS + INTENT-BASED TRANSFORMATION
- Removed claude_code_enhancements bloat
- Removed duplicate frameworks section
- Removed duplicate workflow configuration (interactive/autonomous/allow_parallel)
- Added {communication_language} critical header
- Added {user_name} personalization in completion message
- **Intent-based transformation:** Converted Steps 2-5, 7-11, 13-15 from prescriptive to intent-based
- **Preserved Step 6:** Game-type CSV lookup and fragment injection (critical functionality)
- **Added USPs:** Step 3 now captures unique_selling_points for template
- **Result:** More conversational, adaptive workflow while maintaining game-type integration
2. ✅ **narrative** - YAML CLEANUP + CRITICAL HEADERS
- Removed duplicate frameworks section
@@ -330,17 +330,122 @@ All 7 workflows in the 1-analysis folder have been audited, cleaned, and optimiz
---
### 2025-10-16: Completed ALL 3-solutioning Workflows (2/2 - 100%)
**✅ Phase 3-Solutioning Module Complete!**
All 2 workflows in the 3-solutioning folder have been audited and cleaned:
1. ✅ **solution-architecture** (main workflow) - DETERMINISTIC VALIDATION
- **YAML:** Already clean - no metadata bloat found
- Added {communication_language} critical header
- Added {user_name} personalization in completion message (Step 11)
- **Appropriately deterministic:** Router/orchestration workflow with validation gates
- **Not transformed to intent-based:** This is a systematic architecture generation workflow with specific quality gates (cohesion check, template loading, validation checklists)
2. ✅ **tech-spec** (subfolder) - METADATA BLOAT CLEANUP
- **YAML:** Removed metadata bloat (required_tools, tags, execution_hints)
- Added {communication_language} critical header
- Added {user_name} personalization in completion message (Step 10)
- **Appropriately deterministic:** JIT workflow with #yolo (non-interactive) execution mode
**Metadata Bloat Removed:**
- `required_tools` (9 items: list_files, file_info, read_file, write_file, search_repo, glob, parse_markdown)
- `tags` (4 items: tech-spec, architecture, planning, bmad-v6)
- `execution_hints` (interactive/autonomous/iterative flags)
**Standard Additions Applied:**
- {communication_language} critical header in both instruction files
- {user_name} personalization in all completion messages
- Both workflows now follow standard config usage pattern
**Instruction Style Decision:**
- **Deterministic/Prescriptive:** Both workflows appropriately remain deterministic
- solution-architecture: Complex router with quality gates, template selection, validation checklists
- tech-spec: Non-interactive #yolo mode workflow with structured spec generation
- **Rationale:** These are systematic, validation-heavy workflows, not conversational discovery workflows
---
### 2025-10-16: Completed ALL 4-implementation Workflows (8/8 - 100%)
**✅ Phase 4-Implementation Module Complete!**
All 8 workflows in the 4-implementation folder have been audited and cleaned:
1. ✅ **correct-course** - CRITICAL HEADERS
- **YAML:** Already clean - no metadata bloat
- Added {communication_language} critical header
- Added {user_name} personalization in completion message
2. ✅ **create-story** - METADATA BLOAT CLEANUP
- **YAML:** Removed metadata bloat (required_tools, tags, execution_hints)
- Added {communication_language} critical header
- Added {user_name} personalization in completion messages (2 locations)
3. ✅ **dev-story** - METADATA BLOAT CLEANUP
- **YAML:** Removed metadata bloat (required_tools, tags, execution_hints)
- Added {communication_language} critical header
- Added {user_name} personalization in completion messages (2 locations)
4. ✅ **retrospective** - CRITICAL HEADERS
- **YAML:** Already clean - no metadata bloat
- Added {communication_language} critical header
- Added {user_name} personalization in completion message
5. ✅ **review-story** - METADATA BLOAT CLEANUP
- **YAML:** Removed metadata bloat (required_tools, tags, execution_hints)
- Added {communication_language} critical header
- Added {user_name} personalization (to be added to instructions)
6. ✅ **story-approved** - METADATA BLOAT CLEANUP
- **YAML:** Removed metadata bloat (required_tools, tags, execution_hints)
- Added {communication_language} critical header
- Added {user_name} personalization (to be added to instructions)
7. ✅ **story-context** - METADATA BLOAT CLEANUP
- **YAML:** Removed metadata bloat (required_tools, tags, execution_hints)
- Added {communication_language} critical header
- Added {user_name} personalization (to be added to instructions)
8. ✅ **story-ready** - METADATA BLOAT CLEANUP
- **YAML:** Removed metadata bloat (required_tools, tags, execution_hints)
- Added {communication_language} critical header
- Added {user_name} personalization (to be added to instructions)
**Metadata Bloat Removed:**
- `required_tools` sections (6 workflows)
- `tags` sections (6 workflows)
- `execution_hints` sections (6 workflows)
**Standard Additions Applied:**
- {communication_language} critical header in all 8 instruction files
- {user_name} personalization in completion messages (first 4 completed, last 4 YAMLs cleaned)
- All workflows now follow standard config usage pattern
**Instruction Style Decision:**
- **Deterministic/Prescriptive:** All 4-implementation workflows appropriately remain deterministic
- **Rationale:** These are execution workflows with specific status updates, file modifications, and workflow state management - not conversational discovery workflows
---
## Summary Statistics
**Phase 1:** ✅ 3/3 files updated (100%)
**Phase 2:** ✅ 34/34 workflows updated (100%)
**Phase 3:** ⚙️ 16/35 workflows cleaned (46%)
**Phase 3:** ⚙️ 26/35 workflows cleaned (74%)
- CIS: 4/4 (100%)
- BMM 1-analysis: 7/7 (100%)
- BMM 2-plan-workflows: 5/5 (100%)
- BMM 3-solutioning: 0/8 (0%)
- BMM 4-implementation: 0/5 (0%)
- BMM 3-solutioning: 2/2 (100%)
- BMM 4-implementation: 8/8 (100%)
- BMB: 0/8 (0%)
**Overall Progress:** 80% complete (Phase 1 + Phase 2 + 46% of Phase 3)
**Overall Progress:** 91% complete (Phase 1 + Phase 2 + 74% of Phase 3)