status normalization

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

@@ -134,7 +134,7 @@ All stories are either still in backlog or already marked ready/in-progress/done
   <step n="7" goal="Update story file and mark ready for dev" tag="sprint-status">
     <action>Open {{story_path}}</action>
     <action>Find the "Status:" line (usually at the top)</action>
-    <action>Update story file: Change Status to "Ready"</action>
+    <action>Update story file: Change Status to "ready-for-dev"</action>
     <action>Under 'Dev Agent Record' → 'Context Reference' (create if missing), add or update a list item for {default_output_file}.</action>
     <action>Save the story file.</action>
 
@@ -152,21 +152,31 @@ You may need to run sprint-planning to refresh tracking.
       </output>
     </check>
 
-    <output>**✅ Story Context Generated Successfully, {user_name}!**
+    <action>Communicate to {user_name} that story context has been successfully generated</action>
+    <action>Summarize what was accomplished: story ID, story key, title, context file location</action>
+    <action>Explain that story status is now "ready-for-dev" (was "drafted") and sprint status is "ready-for-dev" (was "drafted")</action>
+    <action>Highlight the value of the generated context: provides docs, code references, interfaces, constraints, and test guidance</action>
 
-**Story Details:**
-- Story ID: {{story_id}}
-- Story Key: {{story_key}}
-- Title: {{story_title}}
-- Context File: {{default_output_file}}
-- Story Status: Ready (was Draft)
-- Sprint Status: ready-for-dev (was drafted)
+    <action>Based on {user_skill_level}, ask if user would like to understand:
+      - What information was gathered in the context file
+      - How the context file will help during implementation
+      - What the next steps are
+      - Anything else about the context generation process
+    </action>
 
-**Next Steps:**
-1. Load DEV agent (bmad/bmm/agents/dev.md)
-2. Run `dev-story` workflow to implement the story
-3. The context file will provide comprehensive implementation guidance
-    </output>
+    <check if="user asks for explanations">
+      <action>Provide clear explanations tailored to {user_skill_level}</action>
+      <action>Reference specific sections of the generated context when helpful</action>
+    </check>
+
+    <action>Once explanations are complete (or user indicates no questions), suggest logical next steps</action>
+    <action>Common next steps to suggest (but allow user flexibility):
+      - Review the generated context file to understand implementation guidance
+      - Load DEV agent and run `dev-story` workflow to implement the story
+      - Check sprint-status.yaml to see which stories are ready for development
+      - Generate context for additional drafted stories if needed
+    </action>
+    <action>Remain flexible - allow user to choose their own path or ask for other assistance</action>
   </step>
 
 </workflow>

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

@@ -8,6 +8,8 @@ config_source: "{project-root}/bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
+story_path: "{config_source}:dev_story_location"
+context_path: "{config_source}:dev_story_location"
 date: system-generated
 
 # Workflow components
@@ -26,10 +28,7 @@ variables:
   non_interactive: true
 
 # Output configuration
-default_output_file: "{story_dir}/story-context-{{epic_id}}.{{story_id}}.xml"
-
-# Recommended inputs
-recommended_inputs:
-  - story_markdown: "Path to a story markdown file to build context for"
+# Uses story_key from sprint-status.yaml (e.g., "1-2-user-authentication")
+default_output_file: "{story_dir}/{{story_key}}.context.md"
 
 web_bundle: false