2025-10-12 16:59:54 -05:00
|
|
|
# Story Ready Workflow Instructions (SM Agent)
|
|
|
|
|
|
2025-10-16 08:58:09 -05:00
|
|
|
<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>
|
2025-10-17 20:33:38 -05:00
|
|
|
<critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical>
|
|
|
|
|
<critical>Generate all documents in {document_output_language}</critical>
|
2025-10-16 08:58:09 -05:00
|
|
|
|
2025-10-12 16:59:54 -05:00
|
|
|
<workflow>
|
|
|
|
|
|
|
|
|
|
<critical>This workflow is run by SM agent AFTER user reviews a drafted story and confirms it's ready for development</critical>
|
2025-10-21 22:25:26 -05:00
|
|
|
<critical>Simple workflow: Update story file status to Ready</critical>
|
2025-10-12 16:59:54 -05:00
|
|
|
|
2025-10-21 22:25:26 -05:00
|
|
|
<step n="1" goal="Locate story and update status">
|
2025-10-12 16:59:54 -05:00
|
|
|
|
2025-10-21 22:25:26 -05:00
|
|
|
<action>If {{story_path}} explicitly provided → use it</action>
|
|
|
|
|
<action>Otherwise list story-\*.md files from {{story_dir}}, sort by modified time</action>
|
|
|
|
|
<ask>Select the drafted story to mark as Ready, or enter path:</ask>
|
2025-10-12 16:59:54 -05:00
|
|
|
|
2025-10-21 22:25:26 -05:00
|
|
|
<action>Read the story file: {{story_path}}</action>
|
|
|
|
|
<action>Extract story ID and title from the file</action>
|
2025-10-12 16:59:54 -05:00
|
|
|
|
|
|
|
|
<action>Find the "Status:" line (usually at the top)</action>
|
|
|
|
|
|
|
|
|
|
<action>Update story file:</action>
|
|
|
|
|
|
2025-10-21 22:25:26 -05:00
|
|
|
- Change: `Status: Draft` or similar
|
2025-10-12 16:59:54 -05:00
|
|
|
- To: `Status: Ready`
|
|
|
|
|
|
|
|
|
|
<action>Save the story file</action>
|
|
|
|
|
|
|
|
|
|
</step>
|
|
|
|
|
|
2025-10-21 22:25:26 -05:00
|
|
|
<step n="2" goal="Confirm completion to user">
|
2025-10-12 16:59:54 -05:00
|
|
|
|
2025-10-21 22:25:26 -05:00
|
|
|
<output>**Story Marked Ready for Development, {user_name}!**
|
2025-10-12 16:59:54 -05:00
|
|
|
|
2025-10-21 22:25:26 -05:00
|
|
|
✅ Story file updated: `{{story_file}}` → Status: Ready
|
2025-10-12 16:59:54 -05:00
|
|
|
|
2025-10-21 22:25:26 -05:00
|
|
|
**Story Details:**
|
2025-10-12 16:59:54 -05:00
|
|
|
|
2025-10-21 22:25:26 -05:00
|
|
|
- **ID:** {{story_id}}
|
|
|
|
|
- **Title:** {{story_title}}
|
|
|
|
|
- **File:** `{{story_file}}`
|
2025-10-12 16:59:54 -05:00
|
|
|
- **Status:** Ready for development
|
|
|
|
|
|
|
|
|
|
**Next Steps:**
|
|
|
|
|
|
|
|
|
|
1. **Recommended:** Run `story-context` workflow to generate implementation context
|
|
|
|
|
- This creates a comprehensive context XML for the DEV agent
|
|
|
|
|
- Includes relevant architecture, dependencies, and existing code
|
|
|
|
|
|
|
|
|
|
2. **Alternative:** Skip context generation and go directly to `dev-story` workflow
|
|
|
|
|
- Faster, but DEV agent will have less context
|
|
|
|
|
- Only recommended for simple, well-understood stories
|
|
|
|
|
|
|
|
|
|
**To proceed:**
|
|
|
|
|
|
|
|
|
|
- For context generation: Stay with SM agent and run `story-context` workflow
|
|
|
|
|
- For direct implementation: Load DEV agent and run `dev-story` workflow
|
|
|
|
|
|
|
|
|
|
</step>
|
|
|
|
|
|
|
|
|
|
</workflow>
|