workflow references to moved workflow status workflow

src/modules/bmm/workflows/1-analysis/brainstorm-game/instructions.md

@@ -6,7 +6,7 @@
 <workflow>
 
   <step n="1" goal="Validate workflow readiness">
-    <invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+    <invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
       <param>mode: validate</param>
       <param>calling_workflow: brainstorm-game</param>
     </invoke-workflow>

src/modules/bmm/workflows/1-analysis/brainstorm-project/instructions.md

@@ -9,7 +9,7 @@
 <workflow>
 
   <step n="1" goal="Validate workflow readiness">
-    <invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+    <invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
       <param>mode: validate</param>
       <param>calling_workflow: brainstorm-project</param>
     </invoke-workflow>

src/modules/bmm/workflows/1-analysis/document-project/instructions.md

@@ -10,7 +10,7 @@
 
 <step n="1" goal="Validate workflow and get project info">
 
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
   <param>mode: data</param>
   <param>data_request: project_config</param>
 </invoke-workflow>
@@ -36,7 +36,7 @@
   </check>
 
   <!-- Now validate sequencing -->
-  <invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+  <invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
     <param>mode: validate</param>
     <param>calling_workflow: document-project</param>
   </invoke-workflow>

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

@@ -10,7 +10,7 @@
 <workflow>
 
 <step n="0" goal="Validate workflow readiness">
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
   <param>mode: validate</param>
   <param>calling_workflow: game-brief</param>
 </invoke-workflow>

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

@@ -10,7 +10,7 @@
 <workflow>
 
 <step n="0" goal="Validate workflow readiness">
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
   <param>mode: validate</param>
   <param>calling_workflow: product-brief</param>
 </invoke-workflow>

src/modules/bmm/workflows/1-analysis/research/instructions-router.md

@@ -11,7 +11,7 @@
 <critical>This is a ROUTER that directs to specialized research instruction sets</critical>
 
 <step n="1" goal="Validate workflow readiness">
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
   <param>mode: validate</param>
   <param>calling_workflow: research</param>
 </invoke-workflow>

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

@@ -16,7 +16,7 @@
 
 <step n="0" goal="Validate workflow and extract project configuration">
 
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
   <param>mode: data</param>
   <param>data_request: project_config</param>
 </invoke-workflow>
@@ -65,7 +65,7 @@ Use: `prd`
 
 <step n="0.5" goal="Validate workflow sequencing">
 
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
   <param>mode: validate</param>
   <param>calling_workflow: gdd</param>
 </invoke-workflow>

src/modules/bmm/workflows/2-plan-workflows/narrative/instructions-narrative.md

@@ -12,7 +12,7 @@
 
 <step n="0" goal="Check for workflow status">
 
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
   <param>mode: init-check</param>
 </invoke-workflow>
 

src/modules/bmm/workflows/2-plan-workflows/prd/instructions.md

@@ -14,7 +14,7 @@
 
 <step n="0" goal="Validate workflow and extract project configuration">
 
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
   <param>mode: data</param>
   <param>data_request: project_config</param>
 </invoke-workflow>
@@ -64,7 +64,7 @@ Game projects should use GDD workflow instead of PRD.
 
 <step n="0.5" goal="Validate workflow sequencing">
 
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
   <param>mode: validate</param>
   <param>calling_workflow: prd</param>
 </invoke-workflow>

src/modules/bmm/workflows/2-plan-workflows/tech-spec/instructions.md

@@ -15,7 +15,7 @@
 
 <step n="0" goal="Validate workflow and extract project configuration">
 
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
   <param>mode: data</param>
   <param>data_request: project_config</param>
 </invoke-workflow>
@@ -65,7 +65,7 @@ Game projects should use GDD workflow instead of tech-spec.
 
 <step n="0.5" goal="Validate workflow sequencing">
 
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
   <param>mode: validate</param>
   <param>calling_workflow: tech-spec</param>
 </invoke-workflow>

src/modules/bmm/workflows/2-plan-workflows/ux/instructions-ux.md

@@ -14,7 +14,7 @@
 
 <step n="0" goal="Check for workflow status">
 
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
   <param>mode: init-check</param>
 </invoke-workflow>
 

src/modules/bmm/workflows/3-solutioning/implementation-ready-check/workflow.yaml

@@ -12,8 +12,8 @@ document_output_language: "{config_source}:document_output_language"
 date: system-generated
 
 # Workflow status integration
-workflow_status_workflow: "{project-root}/bmad/bmm/workflows/1-analysis/workflow-status/workflow.yaml"
-workflow_paths_dir: "{project-root}/bmad/bmm/workflows/1-analysis/workflow-status/paths"
+workflow_status_workflow: "{project-root}/bmad/bmm/workflows/workflow-status/workflow.yaml"
+workflow_paths_dir: "{project-root}/bmad/bmm/workflows/workflow-status/paths"
 
 # Module path and component files
 installed_path: "{project-root}/bmad/bmm/workflows/3-solutioning/implementation-ready-check"

src/modules/bmm/workflows/3-solutioning/instructions.md

@@ -13,7 +13,7 @@ This workflow generates scale-adaptive solution architecture documentation that
 
 <step n="0" goal="Validate workflow and extract project configuration">
 
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
   <param>mode: data</param>
   <param>data_request: project_config</param>
 </invoke-workflow>
@@ -52,7 +52,7 @@ After setup, return here to run solution-architecture.
 
 <step n="0.5" goal="Validate workflow sequencing and prerequisites">
 
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
   <param>mode: validate</param>
   <param>calling_workflow: solution-architecture</param>
 </invoke-workflow>

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

@@ -10,7 +10,7 @@
 <workflow>
 
 <step n="0" goal="Check project status" optional="true">
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
   <param>mode: init-check</param>
 </invoke-workflow>
 

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

@@ -32,7 +32,7 @@
   </step>
 
   <step n="2.5" goal="Get story to draft from status file">
-    <invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+    <invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
       <param>mode: data</param>
       <param>data_request: next_story</param>
     </invoke-workflow>

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

@@ -16,7 +16,7 @@
 <workflow>
 
   <step n="1" goal="Load story from status file IN PROGRESS section">
-    <invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+    <invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
       <param>mode: data</param>
       <param>data_request: next_story</param>
     </invoke-workflow>

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

@@ -21,7 +21,7 @@ FACILITATION NOTES:
 <workflow>
 
 <step n="1" goal="Check workflow status">
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
   <param>mode: init-check</param>
 </invoke-workflow>
 
@@ -36,14 +36,10 @@ Running in standalone mode - no progress tracking.</output>
 </step>
 
 <step n="2" goal="Epic Context Discovery">
-<action>Identify the completed epic</action>
-
-<ask>Which epic has just been completed? (Enter epic number, e.g., "003" or auto-detect from highest completed story)</ask>
-
-  <check if="auto-detecting">
-    <action>Check {output_folder}/stories/ for highest numbered completed story</action>
-    <action>Extract epic number from story file (e.g., "Epic: 003" section)</action>
-  </check>
+<action>Help the user identify which epic was just completed through natural conversation</action>
+<action>Attempt to auto-detect by checking {output_folder}/stories/ for the highest numbered completed story and extracting the epic number</action>
+<action>If auto-detection succeeds, confirm with user: "It looks like Epic {{epic_number}} was just completed - is that correct?"</action>
+<action>If auto-detection fails or user indicates different epic, ask them to share which epic they just completed</action>
 
 <action>Load the completed epic from: {output_folder}/prd/epic-{{epic_number}}.md</action>
 <action>Extract epic details:
@@ -166,77 +162,71 @@ Focus Areas:
 </step>
 
 <step n="4" goal="Epic Review Discussion">
-<action>Scrum Master facilitates Part 1: Reviewing the completed epic</action>
-<action>Each agent shares in their unique voice, referencing actual story data</action>
-<action>Maintain psychological safety - focus on learning, not blame</action>
+<action>Scrum Master facilitates Part 1: Reviewing the completed epic through natural, psychologically safe discussion</action>
+<action>Create space for each agent to share their perspective in their unique voice and communication style, grounded in actual story data and outcomes</action>
+<action>Maintain psychological safety throughout - focus on learning and systems, not blame or individual performance</action>
 
-<action>For each participating agent, present structured feedback:</action>
+<action>Guide the retrospective conversation to naturally surface key themes across three dimensions:</action>
 
-**{{Agent Name}} ({{Role}})**:
+**1. Successes and Strengths:**
+<action>Facilitate discussion that helps agents share what worked well during the epic - encourage specific examples from completed stories, effective practices, velocity achievements, collaboration wins, and smart technical decisions</action>
+<action>Draw out concrete examples: "Can you share a specific story where that approach worked well?"</action>
 
-**What Went Well:**
+**2. Challenges and Growth Areas:**
+<action>Create safe space for agents to explore challenges encountered - guide them to discuss blockers, process friction, technical debt decisions, and coordination issues with curiosity rather than judgment</action>
+<action>Probe for root causes: "What made that challenging? What pattern do we see here?"</action>
+<action>Keep focus on systems and processes, not individuals</action>
 
-- Successes from completed stories (cite specific examples)
-- Effective practices or processes that worked
-- Velocity achievements or quality wins
-- Collaboration highlights
-- Technical successes or good decisions
+**3. Insights and Learning:**
+<action>Help the team articulate what they learned from this epic - facilitate discovery of patterns to repeat or avoid, skills gained, and process improvements worth trying</action>
+<action>Connect insights to future application: "How might this insight help us in future epics?"</action>
 
-**What Could Improve:**
+<action>For each agent participating (loaded from {agent_manifest}):</action>
 
-- Challenges from story records (cite specifics)
-- Blockers that slowed progress and why
-- Process friction or inefficiencies
-- Technical debt incurred and rationale
-- Communication or coordination issues
+- Let them speak naturally in their role's voice and communication style
+- Encourage grounding in specific story records, metrics, and real outcomes
+- Allow themes to emerge organically rather than forcing a rigid structure
+- Follow interesting threads with adaptive questions
+- Balance celebration with honest assessment
 
-**Lessons Learned:**
-
-- Key insights for future epics
-- Patterns to repeat or avoid
-- Skills or knowledge gained
-- Process improvements to implement
-
-<action>Agent personality guidance:
-Each agent loaded from {agent_manifest} will interact with their role and personality and communication style best represented and simulated during discussions
-</action>
-
-<action>Encourage specific examples from story records, metrics, and real outcomes</action>
-<action>Scrum Master synthesizes common themes as discussion progresses</action>
+<action>As facilitator, actively synthesize common themes and patterns as the discussion unfolds</action>
+<action>Notice when multiple agents mention similar issues or successes - call these out to deepen the team's shared understanding</action>
+<action>Ensure every voice is heard, inviting quieter agents to contribute</action>
 </step>
 
 <step n="5" goal="Next Epic Preparation Discussion">
-<action>Scrum Master facilitates Part 2: Preparing for the next epic</action>
-<action>Each agent addresses preparation needs from their domain</action>
+<action>Scrum Master facilitates Part 2: Preparing for the next epic through forward-looking exploration</action>
+<action>Shift the team's focus from reflection to readiness - guide each agent to explore preparation needs from their domain perspective</action>
 
-<action>For each agent, present forward-looking analysis:</action>
+<action>Facilitate discovery across critical preparation dimensions:</action>
 
-**{{Agent Name}} ({{Role}})**:
+**Dependencies and Continuity:**
+<action>Guide agents to explore connections between the completed epic and the upcoming one - help them identify what components, decisions, or work from Epic {{completed_number}} the next epic relies upon</action>
+<action>Probe for gaps: "What needs to be in place before we can start Epic {{next_number}}?"</action>
+<action>Surface hidden dependencies: "Are there integration points we need to verify?"</action>
 
-**Dependencies Check:**
+**Readiness and Setup:**
+<action>Facilitate discussion about what preparation work is needed before the next epic can begin successfully - technical setup, knowledge development, refactoring, documentation, or infrastructure</action>
+<action>Draw out specific needs: "What do you need to feel ready to start Epic {{next_number}}?"</action>
+<action>Identify knowledge gaps: "What do we need to learn or research before diving in?"</action>
 
-- What from Epic {{completed_number}} is needed for Epic {{next_number}}?
-- Any incomplete work that could block us?
-- Integration points or handoffs to verify?
+**Risks and Mitigation:**
+<action>Create space for agents to voice concerns and uncertainties about the upcoming epic based on what they learned from this one</action>
+<action>Explore proactively: "Based on Epic {{completed_number}}, what concerns do you have about Epic {{next_number}}?"</action>
+<action>Develop mitigation thinking: "What could we do now to reduce that risk?"</action>
+<action>Identify early warning signs: "How will we know if we're heading for that problem again?"</action>
 
-**Preparation Needs:**
+<action>For each agent participating:</action>
 
-- Technical setup required before starting
-- Knowledge gaps to fill (research, training, spikes)
-- Refactoring or cleanup needed
-- Documentation or specifications to create
-- Tools or infrastructure to provision
+- Let them share preparation needs in their natural voice
+- Encourage domain-specific insights (Architect on technical setup, PM on requirements clarity, etc.)
+- Follow interesting preparation threads with adaptive questions
+- Help agents build on each other's observations
+- Surface quick wins that could de-risk the epic early
 
-**Risk Assessment:**
-
-- Potential issues based on Epic {{completed_number}} experience
-- Unknowns or uncertainties in Epic {{next_number}}
-- Mitigation strategies to consider
-- Early warning signs to watch for
-
-<action>Focus on actionable preparation items</action>
-<action>Identify dependencies between preparation tasks</action>
-<action>Note any quick wins that could de-risk the next epic</action>
+<action>As facilitator, identify dependencies between preparation tasks as they emerge</action>
+<action>Notice when preparation items from different agents connect or conflict - explore these intersections</action>
+<action>Build a shared understanding of what "ready to start Epic {{next_number}}" actually means</action>
 </step>
 
 <step n="6" goal="Synthesize Action Items">
@@ -310,44 +300,44 @@ Risk Mitigation:
 <action>Identify which tasks can run in parallel vs. sequential</action>
 </step>
 
-<step n="7" goal="Critical User Verification">
-<action>Scrum Master leads final verification checks before concluding retrospective</action>
-<action>User must confirm readiness before next epic begins</action>
+<step n="7" goal="Critical Readiness Exploration">
+<action>Scrum Master leads a thoughtful exploration of whether Epic {{completed_number}} is truly complete and the team is ready for Epic {{next_number}}</action>
+<action>Approach this as discovery, not interrogation - help user surface any concerns or unfinished elements that could impact the next epic</action>
 
-<ask>Let's verify Epic {{completed_number}} is truly complete. Please confirm each item:</ask>
+<action>Guide a conversation exploring the completeness of Epic {{completed_number}} across critical dimensions:</action>
 
-**Testing Verification:**
-<ask>Has full regression testing been completed for Epic {{completed_number}}? (yes/no/partial)</ask>
+**Testing and Quality:**
+<action>Explore the testing state of the epic - help user assess whether quality verification is truly complete</action>
+<action>Ask thoughtfully: "Walk me through the testing that's been done for Epic {{completed_number}}. Does anything still need verification?"</action>
+<action>Probe for gaps: "Are you confident the epic is production-ready from a quality perspective?"</action>
+<action if="testing concerns surface">Add to Critical Path: Complete necessary testing before Epic {{next_number}}</action>
 
-<action if="no or partial">Add to Critical Path: Complete regression testing before Epic {{next_number}}</action>
+**Deployment and Release:**
+<action>Understand where the epic currently stands in the deployment pipeline</action>
+<action>Explore: "What's the deployment status for Epic {{completed_number}}? Is it live, scheduled, or still pending?"</action>
+<action>If not yet deployed, clarify timeline: "When is deployment planned? Does that timing work for starting Epic {{next_number}}?"</action>
+<action if="deployment must happen first">Add to Critical Path: Deploy Epic {{completed_number}} with clear timeline</action>
 
-**Deployment Status:**
-
-<ask>Has Epic {{completed_number}} been deployed to production? (yes/no/scheduled)</ask>
-<action if="no deployment to prod">Add to Critical Path: Deploy Epic {{completed_number}} - scheduled for {{date}}</action>
-
-**Business Validation:**
-<ask>Have stakeholders reviewed and accepted Epic {{completed_number}} deliverables? (yes/no/pending)</ask>
-
-<action if="no or pending deliverables">Add to Critical Path: Obtain stakeholder acceptance before Epic {{next_number}}</action>
+**Stakeholder Acceptance:**
+<action>Guide user to reflect on business validation and stakeholder satisfaction</action>
+<action>Ask: "Have stakeholders seen and accepted the Epic {{completed_number}} deliverables? Any feedback pending?"</action>
+<action>Probe for risk: "Is there anything about stakeholder acceptance that could affect Epic {{next_number}}?"</action>
+<action if="acceptance incomplete">Add to Critical Path: Obtain stakeholder acceptance before proceeding</action>
 
 **Technical Health:**
-<ask>Is the codebase in a stable, maintainable state after Epic {{completed_number}}? (yes/no/concerns)</ask>
+<action>Create space for honest assessment of codebase stability after the epic</action>
+<action>Explore: "How does the codebase feel after Epic {{completed_number}}? Stable and maintainable, or are there concerns?"</action>
+<action>If concerns arise, probe deeper: "What's causing those concerns? What would it take to address them?"</action>
+<action if="stability concerns exist">Document concerns and add to Preparation Sprint: Address stability issues before Epic {{next_number}}</action>
 
-<check if="not stable or maintainable or concerns about codebase">
-  <action>Document concerns: {{user_input}}</action>
-  <action>Add to Preparation Sprint: Address stability concerns</action>
-</check>
+**Unresolved Blockers:**
+<action>Help user surface any lingering issues that could create problems for the next epic</action>
+<action>Ask: "Are there any unresolved blockers or technical issues from Epic {{completed_number}} that we need to address before moving forward?"</action>
+<action>Explore impact: "How would these blockers affect Epic {{next_number}} if left unresolved?"</action>
+<action if="blockers exist">Document blockers and add to Critical Path with appropriate priority</action>
 
-**Blocker Resolution:**
-<ask>Are there any unresolved blockers from Epic {{completed_number}} that will impact Epic {{next_number}}? (yes/no)</ask>
-
-<check if="yes unresolved blockers exist">
-  <action>Document blockers: {{user_input}}</action>
-  <action>Add to Critical Path with highest priority</action>
-</check>
-
-<action>Summarize the verification results and any critical items added</action>
+<action>Synthesize the readiness discussion into a clear picture of what must happen before Epic {{next_number}} can safely begin</action>
+<action>Summarize any critical items identified and ensure user agrees with the assessment</action>
 
 </step>
 

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

@@ -15,7 +15,7 @@
 <workflow>
 
   <step n="1" goal="Check workflow status">
-    <invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+    <invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
       <param>mode: init-check</param>
     </invoke-workflow>
 

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

@@ -13,7 +13,7 @@
 
 <step n="1" goal="Get story queue from status file">
 
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
   <param>mode: data</param>
   <param>data_request: all</param>
 </invoke-workflow>

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

@@ -12,7 +12,7 @@
 
 <workflow>
   <step n="1" goal="Validate workflow sequence">
-    <invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+    <invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
       <param>mode: validate</param>
       <param>calling_workflow: story-context</param>
     </invoke-workflow>

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

@@ -13,7 +13,7 @@
 
 <step n="1" goal="Get TODO story from status file">
 
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
   <param>mode: data</param>
   <param>data_request: next_story</param>
 </invoke-workflow>

src/modules/bmm/workflows/workflow-status/INTEGRATION-EXAMPLE.md

@@ -20,7 +20,7 @@ With the new service call:
 ```xml
 <!-- NEW WAY - Clean and simple -->
 <step n="0" goal="Validate workflow readiness">
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
   <param>mode: validate</param>
   <param>calling_workflow: product-brief</param>
 </invoke-workflow>
@@ -61,7 +61,7 @@ With the new service call:
 ```xml
 <!-- NEW WAY - Let workflow-status handle the complexity -->
 <step n="2.5" goal="Get next story to draft">
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
   <param>mode: data</param>
   <param>data_request: next_story</param>
 </invoke-workflow>
@@ -83,7 +83,7 @@ With the new service call:
 
 ```xml
 <step n="0" goal="Load project configuration">
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
   <param>mode: data</param>
   <param>data_request: project_config</param>
 </invoke-workflow>
@@ -104,7 +104,7 @@ With the new service call:
 
 ```xml
 <step n="0" goal="Check if status exists">
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/1-analysis/workflow-status">
+<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
   <param>mode: init-check</param>
 </invoke-workflow>
 

src/modules/bmm/workflows/workflow-status/init/workflow.yaml

@@ -14,12 +14,12 @@ user_skill_level: "{config_source}:user_skill_level"
 date: system-generated
 
 # Workflow components
-installed_path: "{project-root}/bmad/bmm/workflows/1-analysis/workflow-init"
+installed_path: "{project-root}/bmad/bmm/workflows/workflow-status/init"
 instructions: "{installed_path}/instructions.md"
-template: "{project-root}/bmad/bmm/workflows/1-analysis/workflow-status/workflow-status-template.md"
+template: "{project-root}/bmad/bmm/workflows/workflow-status/workflow-status-template.md"
 
 # Path data files
-path_files: "{project-root}/src/modules/bmm/workflows/1-analysis/workflow-status/paths/"
+path_files: "{project-root}/src/modules/bmm/workflows/workflow-status/paths/"
 
 # Output configuration
 default_output_file: "{output_folder}/bmm-workflow-status.md"

src/modules/bmm/workflows/workflow-status/instructions.md

@@ -1,7 +1,7 @@
 # Workflow Status Check - Multi-Mode Service
 
 <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/1-analysis/workflow-status/workflow.yaml</critical>
+<critical>You MUST have already loaded and processed: {project-root}/bmad/bmm/workflows/workflow-status/workflow.yaml</critical>
 <critical>This workflow operates in multiple modes: interactive (default), validate, data, init-check</critical>
 <critical>Other workflows can call this as a service to avoid duplicating status logic</critical>
 

src/modules/bmm/workflows/workflow-status/workflow.yaml

@@ -13,7 +13,7 @@ user_skill_level: "{config_source}:user_skill_level"
 date: system-generated
 
 # Workflow components
-installed_path: "{project-root}/bmad/bmm/workflows/1-analysis/workflow-status"
+installed_path: "{project-root}/bmad/bmm/workflows/workflow-status"
 instructions: "{installed_path}/instructions.md"
 
 # Template for status file creation (used by workflow-init)