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

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