@devo-bmad-custom/agent-orchestration 1.0.2 → 1.0.3

package/src/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md

@@ -1,58 +1,58 @@
----
-name: create-epics-and-stories
-description: 'Break requirements into epics and user stories. Use when the user says "create the epics and stories list"'
----
-
-# Create Epics and Stories
-
-**Goal:** Transform PRD requirements and Architecture decisions into comprehensive stories organized by user value, creating detailed, actionable stories with complete acceptance criteria for development teams.
-
-**Your Role:** In addition to your name, communication_style, and persona, you are also a product strategist and technical specifications writer collaborating with a product owner. This is a partnership, not a client-vendor relationship. You bring expertise in requirements decomposition, technical implementation context, and acceptance criteria writing, while the user brings their product vision, user needs, and business requirements. Work together as equals.
-
----
-
-## WORKFLOW ARCHITECTURE
-
-This uses **step-file architecture** for disciplined execution:
-
-### Core Principles
-
-- **Micro-file Design**: Each step of the overall goal is a self contained instruction file that you will adhere too 1 file as directed at a time
-- **Just-In-Time Loading**: Only 1 current step file will be loaded and followed to completion - never load future step files until told to do so
-- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
-- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
-- **Append-Only Building**: Build documents by appending content as directed to the output file
-
-### Step Processing Rules
-
-1. **READ COMPLETELY**: Always read the entire step file before taking any action
-2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
-3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
-4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
-5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
-6. **LOAD NEXT**: When directed, read fully and follow the next step file
-
-### Critical Rules (NO EXCEPTIONS)
-
-- 🛑 **NEVER** load multiple step files simultaneously
-- 📖 **ALWAYS** read entire step file before execution
-- 🚫 **NEVER** skip steps or optimize the sequence
-- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
-- 🎯 **ALWAYS** follow the exact instructions in the step file
-- ⏸️ **ALWAYS** halt at menus and wait for user input
-- 📋 **NEVER** create mental todo lists from future steps
-
----
-
-## INITIALIZATION SEQUENCE
-
-### 1. Configuration Loading
-
-Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve:
-
-- `project_name`, `output_folder`, `planning_artifacts`, `user_name`, `communication_language`, `document_output_language`
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### 2. First Step EXECUTION
-
-Read fully and follow: `{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md` to begin the workflow.
+---
+name: create-epics-and-stories
+description: 'Break requirements into epics and user stories. Use when the user says "create the epics and stories list"'
+---
+
+# Create Epics and Stories
+
+**Goal:** Transform PRD requirements and Architecture decisions into comprehensive stories organized by user value, creating detailed, actionable stories with complete acceptance criteria for development teams.
+
+**Your Role:** In addition to your name, communication_style, and persona, you are also a product strategist and technical specifications writer collaborating with a product owner. This is a partnership, not a client-vendor relationship. You bring expertise in requirements decomposition, technical implementation context, and acceptance criteria writing, while the user brings their product vision, user needs, and business requirements. Work together as equals.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for disciplined execution:
+
+### Core Principles
+
+- **Micro-file Design**: Each step of the overall goal is a self contained instruction file that you will adhere too 1 file as directed at a time
+- **Just-In-Time Loading**: Only 1 current step file will be loaded and followed to completion - never load future step files until told to do so
+- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
+- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
+- **Append-Only Building**: Build documents by appending content as directed to the output file
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
+5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
+6. **LOAD NEXT**: When directed, read fully and follow the next step file
+
+### Critical Rules (NO EXCEPTIONS)
+
+- 🛑 **NEVER** load multiple step files simultaneously
+- 📖 **ALWAYS** read entire step file before execution
+- 🚫 **NEVER** skip steps or optimize the sequence
+- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
+- 🎯 **ALWAYS** follow the exact instructions in the step file
+- ⏸️ **ALWAYS** halt at menus and wait for user input
+- 📋 **NEVER** create mental todo lists from future steps
+
+---
+
+## INITIALIZATION SEQUENCE
+
+### 1. Configuration Loading
+
+Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve:
+
+- `project_name`, `output_folder`, `planning_artifacts`, `user_name`, `communication_language`, `document_output_language`
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### 2. First Step EXECUTION
+
+Read fully and follow: `{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md` to begin the workflow.

package/src/bmm/workflows/4-implementation/code-review/workflow.yaml

@@ -1,43 +1,43 @@
-# Review Story Workflow
-name: code-review
-description: 'Perform adversarial code review finding specific issues. Use when the user says "run code review" or "review this code"'
-
-# Critical variables from config
-config_source: "{project-root}/_bmad/bmm/config.yaml"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-user_skill_level: "{config_source}:user_skill_level"
-document_output_language: "{config_source}:document_output_language"
-date: system-generated
-planning_artifacts: "{config_source}:planning_artifacts"
-implementation_artifacts: "{config_source}:implementation_artifacts"
-sprint_status: "{implementation_artifacts}/sprint-status.yaml"
-
-# Workflow components
-installed_path: "{project-root}/_bmad/bmm/workflows/4-implementation/code-review"
-instructions: "{installed_path}/instructions.xml"
-validation: "{installed_path}/checklist.md"
-template: false
-
-project_context: "**/project-context.md"
-
-# Smart input file references - handles both whole docs and sharded docs
-# Priority: Whole document first, then sharded version
-# Strategy: SELECTIVE LOAD - only load the specific epic needed for this story review
-input_file_patterns:
-  architecture:
-    description: "System architecture for review context"
-    whole: "{planning_artifacts}/*architecture*.md"
-    sharded: "{planning_artifacts}/*architecture*/*.md"
-    load_strategy: "FULL_LOAD"
-  ux_design:
-    description: "UX design specification (if UI review)"
-    whole: "{planning_artifacts}/*ux*.md"
-    sharded: "{planning_artifacts}/*ux*/*.md"
-    load_strategy: "FULL_LOAD"
-  epics:
-    description: "Epic containing story being reviewed"
-    whole: "{planning_artifacts}/*epic*.md"
-    sharded_index: "{planning_artifacts}/*epic*/index.md"
-    sharded_single: "{planning_artifacts}/*epic*/epic-{{epic_num}}.md"
-    load_strategy: "SELECTIVE_LOAD"
+# Review Story Workflow
+name: code-review
+description: 'Perform adversarial code review finding specific issues. Use when the user says "run code review" or "review this code"'
+
+# Critical variables from config
+config_source: "{project-root}/_bmad/bmm/config.yaml"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+user_skill_level: "{config_source}:user_skill_level"
+document_output_language: "{config_source}:document_output_language"
+date: system-generated
+planning_artifacts: "{config_source}:planning_artifacts"
+implementation_artifacts: "{config_source}:implementation_artifacts"
+sprint_status: "{implementation_artifacts}/sprint-status.yaml"
+
+# Workflow components
+installed_path: "{project-root}/_bmad/bmm/workflows/4-implementation/code-review"
+instructions: "{installed_path}/instructions.xml"
+validation: "{installed_path}/checklist.md"
+template: false
+
+project_context: "**/project-context.md"
+
+# Smart input file references - handles both whole docs and sharded docs
+# Priority: Whole document first, then sharded version
+# Strategy: SELECTIVE LOAD - only load the specific epic needed for this story review
+input_file_patterns:
+  architecture:
+    description: "System architecture for review context"
+    whole: "{planning_artifacts}/*architecture*.md"
+    sharded: "{planning_artifacts}/*architecture*/*.md"
+    load_strategy: "FULL_LOAD"
+  ux_design:
+    description: "UX design specification (if UI review)"
+    whole: "{planning_artifacts}/*ux*.md"
+    sharded: "{planning_artifacts}/*ux*/*.md"
+    load_strategy: "FULL_LOAD"
+  epics:
+    description: "Epic containing story being reviewed"
+    whole: "{planning_artifacts}/*epic*.md"
+    sharded_index: "{planning_artifacts}/*epic*/index.md"
+    sharded_single: "{planning_artifacts}/*epic*/epic-{{epic_num}}.md"
+    load_strategy: "SELECTIVE_LOAD"

package/src/bmm/workflows/4-implementation/correct-course/workflow.yaml

@@ -1,53 +1,53 @@
-# Correct Course - Sprint Change Management Workflow
-name: "correct-course"
-description: 'Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change"'
-
-config_source: "{project-root}/_bmad/bmm/config.yaml"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-user_skill_level: "{config_source}:user_skill_level"
-document_output_language: "{config_source}:document_output_language"
-date: system-generated
-implementation_artifacts: "{config_source}:implementation_artifacts"
-planning_artifacts: "{config_source}:planning_artifacts"
-project_knowledge: "{config_source}:project_knowledge"
-project_context: "**/project-context.md"
-
-# Smart input file references - handles both whole docs and sharded docs
-# Priority: Whole document first, then sharded version
-# Strategy: Load project context for impact analysis
-input_file_patterns:
-  prd:
-    description: "Product requirements for impact analysis"
-    whole: "{planning_artifacts}/*prd*.md"
-    sharded: "{planning_artifacts}/*prd*/*.md"
-    load_strategy: "FULL_LOAD"
-  epics:
-    description: "All epics to analyze change impact"
-    whole: "{planning_artifacts}/*epic*.md"
-    sharded: "{planning_artifacts}/*epic*/*.md"
-    load_strategy: "FULL_LOAD"
-  architecture:
-    description: "System architecture and decisions"
-    whole: "{planning_artifacts}/*architecture*.md"
-    sharded: "{planning_artifacts}/*architecture*/*.md"
-    load_strategy: "FULL_LOAD"
-  ux_design:
-    description: "UX design specification (if UI impacts)"
-    whole: "{planning_artifacts}/*ux*.md"
-    sharded: "{planning_artifacts}/*ux*/*.md"
-    load_strategy: "FULL_LOAD"
-  tech_spec:
-    description: "Technical specification"
-    whole: "{planning_artifacts}/*tech-spec*.md"
-    load_strategy: "FULL_LOAD"
-  document_project:
-    description: "Brownfield project documentation (optional)"
-    sharded: "{project_knowledge}/index.md"
-    load_strategy: "INDEX_GUIDED"
-
-installed_path: "{project-root}/_bmad/bmm/workflows/4-implementation/correct-course"
-template: false
-instructions: "{installed_path}/instructions.md"
-checklist: "{installed_path}/checklist.md"
-default_output_file: "{planning_artifacts}/sprint-change-proposal-{date}.md"
+# Correct Course - Sprint Change Management Workflow
+name: "correct-course"
+description: 'Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change"'
+
+config_source: "{project-root}/_bmad/bmm/config.yaml"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+user_skill_level: "{config_source}:user_skill_level"
+document_output_language: "{config_source}:document_output_language"
+date: system-generated
+implementation_artifacts: "{config_source}:implementation_artifacts"
+planning_artifacts: "{config_source}:planning_artifacts"
+project_knowledge: "{config_source}:project_knowledge"
+project_context: "**/project-context.md"
+
+# Smart input file references - handles both whole docs and sharded docs
+# Priority: Whole document first, then sharded version
+# Strategy: Load project context for impact analysis
+input_file_patterns:
+  prd:
+    description: "Product requirements for impact analysis"
+    whole: "{planning_artifacts}/*prd*.md"
+    sharded: "{planning_artifacts}/*prd*/*.md"
+    load_strategy: "FULL_LOAD"
+  epics:
+    description: "All epics to analyze change impact"
+    whole: "{planning_artifacts}/*epic*.md"
+    sharded: "{planning_artifacts}/*epic*/*.md"
+    load_strategy: "FULL_LOAD"
+  architecture:
+    description: "System architecture and decisions"
+    whole: "{planning_artifacts}/*architecture*.md"
+    sharded: "{planning_artifacts}/*architecture*/*.md"
+    load_strategy: "FULL_LOAD"
+  ux_design:
+    description: "UX design specification (if UI impacts)"
+    whole: "{planning_artifacts}/*ux*.md"
+    sharded: "{planning_artifacts}/*ux*/*.md"
+    load_strategy: "FULL_LOAD"
+  tech_spec:
+    description: "Technical specification"
+    whole: "{planning_artifacts}/*tech-spec*.md"
+    load_strategy: "FULL_LOAD"
+  document_project:
+    description: "Brownfield project documentation (optional)"
+    sharded: "{project_knowledge}/index.md"
+    load_strategy: "INDEX_GUIDED"
+
+installed_path: "{project-root}/_bmad/bmm/workflows/4-implementation/correct-course"
+template: false
+instructions: "{installed_path}/instructions.md"
+checklist: "{installed_path}/checklist.md"
+default_output_file: "{planning_artifacts}/sprint-change-proposal-{date}.md"

package/src/bmm/workflows/4-implementation/create-story/checklist.md

@@ -1,159 +1,159 @@
-# Story Context Quality Review
-
-You are an independent quality validator in a fresh context. Thoroughly review the story file generated by the create-story workflow and identify any mistakes, omissions, or gaps the original pass missed.
-
-**Focus on preventing:**
-
-- Reinventing existing functionality
-- Wrong libraries, versions, or file locations
-- Breaking regressions or ignoring UX requirements
-- Vague or incomplete acceptance criteria
-- Missing learnings from previous stories
-
-## Required Inputs
-
-- Story file to review (`{story_file_path}`)
-- Workflow variables from `{installed_path}/workflow.yaml` (implementation_artifacts, epics_file, etc.)
-- Source documents: epics, architecture (discovered or provided)
-
----
-
-## Systematic Re-Analysis
-
-Systematically re-do the story creation process with a critical eye for what the original pass missed:
-
-### **Step 1: Load and Understand the Target**
-
-1. Load `{installed_path}/workflow.yaml` for variable inclusion
-2. Load the story file `{story_file_path}`; extract epic_num, story_num, story_key, story_title
-3. Resolve all workflow variables: implementation_artifacts, epics_file, architecture_file, etc.
-
-### **Step 2: Exhaustive Source Document Analysis**
-
-#### **2.1 Epics and Stories Analysis**
-
-- Load `{epics_file}` (or sharded equivalents)
-- Extract **COMPLETE Epic {{epic_num}} context**:
-  - Epic objectives and business value
-  - ALL stories in this epic (for cross-story context)
-  - Our specific story's requirements, acceptance criteria
-  - Technical requirements and constraints
-  - Cross-story dependencies and prerequisites
-
-#### **2.2 Architecture Deep-Dive**
-
-- Load `{architecture_file}` (single or sharded)
-- **Systematically scan for ANYTHING relevant to this story:**
-  - Technical stack with versions (languages, frameworks, libraries)
-  - Code structure and organization patterns
-  - API design patterns and contracts
-  - Database schemas and relationships
-  - Security requirements and patterns
-  - Performance requirements and optimization strategies
-  - Testing standards and frameworks
-  - Deployment and environment patterns
-  - Integration patterns and external services
-
-#### **2.3 Previous Story Intelligence (if applicable)**
-
-- If `story_num > 1`, load the previous story file
-- Extract **actionable intelligence**:
-  - Dev notes and learnings
-  - Review feedback and corrections needed
-  - Files created/modified and their patterns
-  - Testing approaches that worked/didn't work
-  - Problems encountered and solutions found
-  - Code patterns and conventions established
-
-#### **2.4 Git History Analysis (if available)**
-
-- Analyze recent commits for patterns:
-  - Files created/modified in previous work
-  - Code patterns and conventions used
-  - Library dependencies added/changed
-  - Architecture decisions implemented
-  - Testing approaches used
-
-#### **2.5 Latest Technical Research**
-
-- Identify any libraries/frameworks mentioned
-- Research latest versions and critical information:
-  - Breaking changes or security updates
-  - Performance improvements or deprecations
-  - Best practices for current versions
-
-### **Step 3: Gap Analysis**
-
-#### **3.1 Reinvention Gaps**
-
-- Duplicate functionality that could be reused instead
-- Existing solutions not referenced
-
-#### **3.2 Technical Specification Gaps**
-
-- Missing version requirements, API contracts, database schema constraints, security requirements
-
-#### **3.3 File Structure Gaps**
-
-- Wrong file locations, coding standard violations, integration pattern breaks, deployment requirements
-
-#### **3.4 Regression Gaps**
-
-- Breaking changes, test failures, UX violations, learnings from previous stories ignored
-
-#### **3.5 Implementation Gaps**
-
-- Vague acceptance criteria, missing scope boundaries, quality requirements
-
-### **Step 4: LLM Optimization Analysis**
-
-Review the story for token efficiency: remove verbosity, fix ambiguity, ensure critical requirements are surfaced clearly, and structure content for scannable LLM processing.
-
-### **Step 5: Improvement Recommendations**
-
-For each gap identified, provide specific actionable improvements categorized as:
-
-- **Critical (Must Fix):** Missing requirements, security gaps, anti-pattern risks, previous story context that would prevent errors
-- **Enhancement (Should Add):** Architectural guidance, technical specs, code reuse opportunities, testing guidance
-- **Optimization (Nice to Have):** Token-efficient phrasing, clearer structure, reduced verbosity
-
----
-
-## Interactive Improvement Process
-
-### **Step 6: Present Improvement Suggestions**
-
-```
-Story: {{story_key}} - {{story_title}}
-Critical: {{critical_count}} | Enhancements: {{enhancement_count}} | Optimizations: {{optimization_count}}
-
-CRITICAL ISSUES (Must Fix):
-{{list each critical issue}}
-
-ENHANCEMENTS (Should Add):
-{{list each enhancement}}
-
-OPTIMIZATIONS (Nice to Have):
-{{list each optimization}}
-```
-
-### **Step 7: Interactive User Selection**
-
-Ask the user:
-
-```
-Which improvements to apply? [all / critical / select / none / details]
-```
-
-### **Step 8: Apply Selected Improvements**
-
-- Load the story file and apply accepted changes naturally
-- Do not reference the review process or that changes were added
-- Ensure the final story reads as if it was created correctly the first time
-
-### **Step 9: Confirmation**
-
-```
-Updated {{count}} sections in {{story_key}}.
-Next: Run `dev-story` for implementation.
-```
+# Story Context Quality Review
+
+You are an independent quality validator in a fresh context. Thoroughly review the story file generated by the create-story workflow and identify any mistakes, omissions, or gaps the original pass missed.
+
+**Focus on preventing:**
+
+- Reinventing existing functionality
+- Wrong libraries, versions, or file locations
+- Breaking regressions or ignoring UX requirements
+- Vague or incomplete acceptance criteria
+- Missing learnings from previous stories
+
+## Required Inputs
+
+- Story file to review (`{story_file_path}`)
+- Workflow variables from `{installed_path}/workflow.yaml` (implementation_artifacts, epics_file, etc.)
+- Source documents: epics, architecture (discovered or provided)
+
+---
+
+## Systematic Re-Analysis
+
+Systematically re-do the story creation process with a critical eye for what the original pass missed:
+
+### **Step 1: Load and Understand the Target**
+
+1. Load `{installed_path}/workflow.yaml` for variable inclusion
+2. Load the story file `{story_file_path}`; extract epic_num, story_num, story_key, story_title
+3. Resolve all workflow variables: implementation_artifacts, epics_file, architecture_file, etc.
+
+### **Step 2: Exhaustive Source Document Analysis**
+
+#### **2.1 Epics and Stories Analysis**
+
+- Load `{epics_file}` (or sharded equivalents)
+- Extract **COMPLETE Epic {{epic_num}} context**:
+  - Epic objectives and business value
+  - ALL stories in this epic (for cross-story context)
+  - Our specific story's requirements, acceptance criteria
+  - Technical requirements and constraints
+  - Cross-story dependencies and prerequisites
+
+#### **2.2 Architecture Deep-Dive**
+
+- Load `{architecture_file}` (single or sharded)
+- **Systematically scan for ANYTHING relevant to this story:**
+  - Technical stack with versions (languages, frameworks, libraries)
+  - Code structure and organization patterns
+  - API design patterns and contracts
+  - Database schemas and relationships
+  - Security requirements and patterns
+  - Performance requirements and optimization strategies
+  - Testing standards and frameworks
+  - Deployment and environment patterns
+  - Integration patterns and external services
+
+#### **2.3 Previous Story Intelligence (if applicable)**
+
+- If `story_num > 1`, load the previous story file
+- Extract **actionable intelligence**:
+  - Dev notes and learnings
+  - Review feedback and corrections needed
+  - Files created/modified and their patterns
+  - Testing approaches that worked/didn't work
+  - Problems encountered and solutions found
+  - Code patterns and conventions established
+
+#### **2.4 Git History Analysis (if available)**
+
+- Analyze recent commits for patterns:
+  - Files created/modified in previous work
+  - Code patterns and conventions used
+  - Library dependencies added/changed
+  - Architecture decisions implemented
+  - Testing approaches used
+
+#### **2.5 Latest Technical Research**
+
+- Identify any libraries/frameworks mentioned
+- Research latest versions and critical information:
+  - Breaking changes or security updates
+  - Performance improvements or deprecations
+  - Best practices for current versions
+
+### **Step 3: Gap Analysis**
+
+#### **3.1 Reinvention Gaps**
+
+- Duplicate functionality that could be reused instead
+- Existing solutions not referenced
+
+#### **3.2 Technical Specification Gaps**
+
+- Missing version requirements, API contracts, database schema constraints, security requirements
+
+#### **3.3 File Structure Gaps**
+
+- Wrong file locations, coding standard violations, integration pattern breaks, deployment requirements
+
+#### **3.4 Regression Gaps**
+
+- Breaking changes, test failures, UX violations, learnings from previous stories ignored
+
+#### **3.5 Implementation Gaps**
+
+- Vague acceptance criteria, missing scope boundaries, quality requirements
+
+### **Step 4: LLM Optimization Analysis**
+
+Review the story for token efficiency: remove verbosity, fix ambiguity, ensure critical requirements are surfaced clearly, and structure content for scannable LLM processing.
+
+### **Step 5: Improvement Recommendations**
+
+For each gap identified, provide specific actionable improvements categorized as:
+
+- **Critical (Must Fix):** Missing requirements, security gaps, anti-pattern risks, previous story context that would prevent errors
+- **Enhancement (Should Add):** Architectural guidance, technical specs, code reuse opportunities, testing guidance
+- **Optimization (Nice to Have):** Token-efficient phrasing, clearer structure, reduced verbosity
+
+---
+
+## Interactive Improvement Process
+
+### **Step 6: Present Improvement Suggestions**
+
+```
+Story: {{story_key}} - {{story_title}}
+Critical: {{critical_count}} | Enhancements: {{enhancement_count}} | Optimizations: {{optimization_count}}
+
+CRITICAL ISSUES (Must Fix):
+{{list each critical issue}}
+
+ENHANCEMENTS (Should Add):
+{{list each enhancement}}
+
+OPTIMIZATIONS (Nice to Have):
+{{list each optimization}}
+```
+
+### **Step 7: Interactive User Selection**
+
+Ask the user:
+
+```
+Which improvements to apply? [all / critical / select / none / details]
+```
+
+### **Step 8: Apply Selected Improvements**
+
+- Load the story file and apply accepted changes naturally
+- Do not reference the review process or that changes were added
+- Ensure the final story reads as if it was created correctly the first time
+
+### **Step 9: Confirmation**
+
+```
+Updated {{count}} sections in {{story_key}}.
+Next: Run `dev-story` for implementation.
+```