External/BMAD-METHOD
1
0
Fork 0
mirror of https://github.com/bmadcode/BMAD-METHOD.git synced 2025-12-29 16:14:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

checks checked

Browse Source
This commit is contained in:
Brian Madison
2025-10-22 15:40:51 -05:00
parent be5b06f55e
commit be5556bf42
8 changed files with 88 additions and 78 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
src/modules/bmm/workflows/1-analysis/game-brief/instructions.md
View File

@@ -300,9 +300,10 @@ This brief will serve as the primary input for creating the Game Design Document
- Proceed to GDD workflow: `workflow gdd`
- Validate assumptions with target players</ask>
<check>If user chooses option 3 (executive summary):</check>
<action>Create condensed 3-page executive brief focusing on: core concept, target market, gameplay pillars, key differentiators, and success criteria</action>
<action>Save as: {output_folder}/game-brief-executive-{{game_name}}-{{date}}.md</action>
<check if="user chooses option 3 (executive summary)">
<action>Create condensed 3-page executive brief focusing on: core concept, target market, gameplay pillars, key differentiators, and success criteria</action>
<action>Save as: {output_folder}/game-brief-executive-{{game_name}}-{{date}}.md</action>
</check>
<template-output>final_brief</template-output>
<template-output>executive_brief</template-output>

7
src/modules/bmm/workflows/1-analysis/product-brief/instructions.md
View File

@@ -264,9 +264,10 @@ Which approach works best for you?</ask>
This brief will serve as the primary input for creating the Product Requirements Document (PRD).</ask>
<check>If user chooses option 3 (executive summary):</check>
<action>Create condensed 3-page executive brief focusing on: problem statement, proposed solution, target users, MVP scope, financial impact, and strategic alignment</action>
<action>Save as: {output_folder}/product-brief-executive-{{project_name}}-{{date}}.md</action>
<check if="user chooses option 3 (executive summary)">
<action>Create condensed 3-page executive brief focusing on: problem statement, proposed solution, target users, MVP scope, financial impact, and strategic alignment</action>
<action>Save as: {output_folder}/product-brief-executive-{{project_name}}-{{date}}.md</action>
</check>
<template-output>final_brief</template-output>
<template-output>executive_brief</template-output>

10
src/modules/bmm/workflows/4-implementation/correct-course/checklist.md
View File

@@ -33,8 +33,8 @@
</check-item>
<halt-condition>
<check>If trigger is unclear: "Cannot proceed without understanding what caused the need for change"</check>
<check>If no evidence provided: "Need concrete evidence or examples of the issue before analyzing impact"</check>
<action if="trigger is unclear">HALT: "Cannot proceed without understanding what caused the need for change"</action>
<action if="no evidence provided">HALT: "Need concrete evidence or examples of the issue before analyzing impact"</action>
</halt-condition>
</section>
@@ -261,9 +261,9 @@
</check-item>
<halt-condition>
<check>If any critical section cannot be completed: "Cannot proceed to proposal without complete impact analysis"</check>
<check>If user approval not obtained: "Must have explicit approval before implementing changes"</check>
<check>If handoff responsibilities unclear: "Must clearly define who will execute the proposed changes"</check>
<action if="any critical section cannot be completed">HALT: "Cannot proceed to proposal without complete impact analysis"</action>
<action if="user approval not obtained">HALT: "Must have explicit approval before implementing changes"</action>
<action if="handoff responsibilities unclear">HALT: "Must clearly define who will execute the proposed changes"</action>
</halt-condition>
</section>

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

@@ -50,9 +50,9 @@
<action>Parse sections: Story, Acceptance Criteria, Tasks/Subtasks, Dev Notes, Dev Agent Record, File List, Change Log, Status</action>
<action>Identify first incomplete task (unchecked [ ]) in Tasks/Subtasks</action>
<check>If no incomplete tasks → <goto step="6">Completion sequence</goto></check>
<check>If story file inaccessible → HALT: "Cannot develop story without access to story file"</check>
<check>If task requirements ambiguous → ASK user to clarify or HALT</check>
<action if="no incomplete tasks"><goto step="6">Completion sequence</goto></action>
<action if="story file inaccessible">HALT: "Cannot develop story without access to story file"</action>
<action if="task requirements ambiguous">ASK user to clarify or HALT</action>
</step>
<step n="1.5" goal="Mark story in-progress in sprint status">
@@ -88,11 +88,11 @@ Story is already marked in-progress
<action>Plan implementation steps and edge cases; write down a brief plan in Dev Agent Record → Debug Log</action>
<action>Implement the task COMPLETELY including all subtasks, following architecture patterns and coding standards in this repo</action>
<action>Handle error conditions and edge cases appropriately</action>
<check>If unapproved dependencies are needed → ASK user for approval before adding</check>
<check>If 3 consecutive implementation failures occur → HALT and request guidance</check>
<check>If required configuration is missing → HALT: "Cannot proceed without necessary configuration files"</check>
<check>If {{run_until_complete}} == true → Do not stop after partial progress; continue iterating tasks until all ACs are satisfied or a HALT condition triggers</check>
<check>Do NOT propose to pause for review, standups, or validation until Step 6 gates are satisfied</check>
<action if="unapproved dependencies are needed">ASK user for approval before adding</action>
<action if="3 consecutive implementation failures occur">HALT and request guidance</action>
<action if="required configuration is missing">HALT: "Cannot proceed without necessary configuration files"</action>
<action if="{{run_until_complete}} == true">Do not stop after partial progress; continue iterating tasks until all ACs are satisfied or a HALT condition triggers</action>
<critical>Do NOT propose to pause for review, standups, or validation until Step 6 gates are satisfied</critical>
</step>
<step n="3" goal="Author comprehensive tests">
@@ -108,8 +108,8 @@ Story is already marked in-progress
<action>Run the new tests to verify implementation correctness</action>
<action>Run linting and code quality checks if configured</action>
<action>Validate implementation meets ALL story acceptance criteria; if ACs include quantitative thresholds (e.g., test pass rate), ensure they are met before marking complete</action>
<check>If regression tests fail → STOP and fix before continuing</check>
<check>If new tests fail → STOP and fix before continuing</check>
<action if="regression tests fail">STOP and fix before continuing</action>
<action if="new tests fail">STOP and fix before continuing</action>
</step>
<step n="5" goal="Mark task complete and update story">
@@ -118,9 +118,9 @@ Story is already marked in-progress
<action>Add completion notes to Dev Agent Record if significant changes were made (summarize intent, approach, and any follow-ups)</action>
<action>Append a brief entry to Change Log describing the change</action>
<action>Save the story file</action>
<check>Determine if more incomplete tasks remain</check>
<check>If more tasks remain → <goto step="1">Next task</goto></check>
<check>If no tasks remain → <goto step="6">Completion</goto></check>
<action>Determine if more incomplete tasks remain</action>
<action if="more tasks remain"><goto step="1">Next task</goto></action>
<action if="no tasks remain"><goto step="6">Completion</goto></action>
</step>
<step n="6" goal="Story completion sequence">
@@ -144,9 +144,9 @@ Story is marked Ready for Review in file, but sprint-status.yaml may be out of s
</output>
</check>
<check>If any task is incomplete → Return to step 1 to complete remaining work (Do NOT finish with partial progress)</check>
<check>If regression failures exist → STOP and resolve before completing</check>
<check>If File List is incomplete → Update it before completing</check>
<action if="any task is incomplete">Return to step 1 to complete remaining work (Do NOT finish with partial progress)</action>
<action if="regression failures exist">STOP and resolve before completing</action>
<action if="File List is incomplete">Update it before completing</action>
</step>
<step n="7" goal="Validation and handoff" optional="true">

43
src/modules/cis/workflows/storytelling/instructions.md
View File

@@ -10,20 +10,24 @@
<step n="1" goal="Story Context Setup">
<action>Check if context data was provided with workflow invocation</action>
<check>If data attribute was passed to this workflow:</check>
<action>Load the context document from the data file path</action>
<action>Study the background information, brand details, or subject matter</action>
<action>Use the provided context to inform story development</action>
<action>Acknowledge the focused storytelling goal</action>
<ask response="story_refinement">I see we're crafting a story based on the context provided. What specific angle or emphasis would you like?</ask>
<check>Else (no context data provided):</check>
<action>Proceed with context gathering</action>
<ask response="story_purpose">1. What's the purpose of this story? (e.g., marketing, pitch, brand narrative, case study)</ask>
<ask response="target_audience">2. Who is your target audience?</ask>
<ask response="key_messages">3. What key messages or takeaways do you want the audience to have?</ask>
<ask>4. Any constraints? (length, tone, medium, existing brand guidelines)</ask>
<check if="data attribute was passed to this workflow">
<action>Load the context document from the data file path</action>
<action>Study the background information, brand details, or subject matter</action>
<action>Use the provided context to inform story development</action>
<action>Acknowledge the focused storytelling goal</action>
<ask response="story_refinement">I see we're crafting a story based on the context provided. What specific angle or emphasis would you like?</ask>
</check>
<check if="no context data provided">
<action>Proceed with context gathering</action>
<ask response="story_purpose">1. What's the purpose of this story? (e.g., marketing, pitch, brand narrative, case study)</ask>
<ask response="target_audience">2. Who is your target audience?</ask>
<ask response="key_messages">3. What key messages or takeaways do you want the audience to have?</ask>
<ask>4. Any constraints? (length, tone, medium, existing brand guidelines)</ask>
<critical>Wait for user response before proceeding. This context shapes the narrative approach.</critical>
</check>
<template-output>story_purpose, target_audience, key_messages</template-output>
@@ -53,13 +57,14 @@ I can help craft your story using these proven narrative frameworks:
Which framework best fits your purpose? (Enter 1-10, or ask for my recommendation)
</ask>
<check>If user asks for recommendation:</check>
<action>Analyze story_purpose, target_audience, and key_messages</action>
<action>Recommend best-fit framework with clear rationale</action>
<example>
Based on your {{story_purpose}} for {{target_audience}}, I recommend:
**{{framework_name}}** because {{rationale}}
</example>
<check if="user asks for recommendation">
<action>Analyze story_purpose, target_audience, and key_messages</action>
<action>Recommend best-fit framework with clear rationale</action>
<example>
Based on your {{story_purpose}} for {{target_audience}}, I recommend:
**{{framework_name}}** because {{rationale}}
</example>
</check>
<template-output>story_type, framework_name</template-output>