siesa-agents 2.1.48 → 2.1.49

package/bmad/_config/workflow-manifest.csv

@@ -17,7 +17,7 @@ name,description,module,path
 "code-review","Perform an ADVERSARIAL Senior Developer code review that finds 3-10 specific problems in every story. Challenges everything: code quality, test coverage, architecture compliance, security, performance. NEVER accepts `looks good` - must find minimum issues and can auto-fix with user approval.","bmm","_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml"
 "correct-course","Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation","bmm","_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml"
 "create-story","Create the next user story from epics+stories with enhanced context analysis and direct ready-for-dev marking","bmm","_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml"
-"dev-story","Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria","bmm","_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml"
+"dev-story","Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria","bmm","_bmad/bmm/workflows/4-implementation/dev-story/workflow.md"
 "retrospective","Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic","bmm","_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml"
 "sprint-planning","Generate and manage the sprint status tracking file for Phase 4 implementation, extracting all epics and stories from epic files and tracking their status through the development lifecycle","bmm","_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml"
 "sprint-status","Summarize sprint-status.yaml, surface risks, and route to the right implementation workflow.","bmm","_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml"

package/bmad/bmm/agents/dev.md

@@ -61,7 +61,7 @@ You must fully embody this agent's persona and follow all activation instruction
   <menu>
     <item cmd="MH or fuzzy match on menu or help">[MH] Redisplay Menu Help</item>
     <item cmd="CH or fuzzy match on chat">[CH] Chat with the Agent about anything</item>
-    <item cmd="DS or fuzzy match on dev-story" workflow="{project-root}/_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml">[DS] Execute Dev Story workflow (full BMM path with sprint-status)</item>
+    <item cmd="DS or fuzzy match on dev-story" workflow="{project-root}/_bmad/bmm/workflows/4-implementation/dev-story/workflow.md">[DS] Execute Dev Story workflow (full BMM path with sprint-status)</item>
     <item cmd="CR or fuzzy match on code-review" workflow="{project-root}/_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml">[CR] Perform a thorough clean context code review (Highly Recommended, use fresh context and different LLM)</item>
     <item cmd="PM or fuzzy match on party-mode" exec="{project-root}/_bmad/core/workflows/party-mode/workflow.md">[PM] Start Party Mode</item>
     <item cmd="DA or fuzzy match on exit, leave, goodbye or dismiss agent">[DA] Dismiss Agent</item>

package/bmad/bmm/workflows/4-implementation/code-review/steps/step-06-jira-sync.md

@@ -9,6 +9,7 @@ workflow_path: '{project-root}/_bmad/bmm/workflows/4-implementation/code-review'
 thisStepFile: '{workflow_path}/steps/step-06-jira-sync.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/review-{story_key}.md'
+nextStepFile: '{workflow_path}/steps/step-07-commit-push.md'
 
 # User Defined References
 storyFile: '{{story_path}}'
@@ -23,6 +24,7 @@ To synchronize the "Done" status with Jira by transitioning the Story and its Su
 - 🛑 ONLY execute if status is 'done'
 - 🧱 Use Pattern B (Cascading Updates) for Jira: Always discover transitions before executing
 - 📄 Update tables in Markdown without breaking format or losing data
+- ⚠️ **NON-BLOCKING**: If any Jira operation fails (Auth, Transitions, API), Log the error and PROCEED to the final transition step. Do NOT stop execution.
 
 ## Sequence of Instructions
 
@@ -36,7 +38,6 @@ To synchronize the "Done" status with Jira by transitioning the Story and its Su
      <action>Call `mcp__atlassian__getAccessibleAtlassianResources` or `mcp__atlassian__atlassianUserInfo`.</action>
 
      <check if="Auth failed or no resources returned">
-        <action>STOP IMMEDIATELY.</action>
         <output>❌ **MCP Authentication Failed.** I cannot connect to Jira. Please ensure you are authenticated with the Atlassian MCP server.</output>
         <output>Run the following command to authenticate (copy and paste into your terminal/chat):</output>
         <display>
@@ -51,10 +52,12 @@ To synchronize the "Done" status with Jira by transitioning the Story and its Su
         <output>After validating in the browser, please choose an option:</output>
         <menu>
            <item cmd="R" action="restart_step2">Retry Authentication (Re-run check)</item>
+           <item cmd="S" action="continue">Skip Jira Sync & Continue</item>
            <item cmd="E" action="exit">Exit Workflow</item>
         </menu>
         <logic>
             <if selection="R">Restart this Step 2 from the beginning.</if>
+            <if selection="S">Log warning about skipping Jira sync and proceed directly to Section 6 "Transition to Next Step".</if>
             <if selection="E">Terminate the workflow with a message: "Workflow aborted due to authentication failure."</if>
         </logic>
      </check>
@@ -66,14 +69,18 @@ To synchronize the "Done" status with Jira by transitioning the Story and its Su
      <action>Read `{story_path}`.</action>
      <check if="content does NOT contain '## Jira Information' OR content does NOT contain '## Synced Tasks'">
         <output>
-        ⚠️ **CRITICAL ERROR: Missing Jira Sections**
-        La historia no está vinculada a Jira. Por favor ejecuta el workflow 'sync-epics-stories' primero.
+        ⚠️ **WARNING: Missing Jira Sections**
+        La historia no está vinculada a Jira. Se omitirá la sincronización.
         </output>
-        <action>STOP execution of this step.</action>
+        <action>Proceed directly to Section 6 "Transition to Next Step".</action>
      </check>
 
   ### 3. Jira Transition Execution (Pattern B)
 
+  <check if="Any MCP Exception occurs in this section">
+    <action>Log error "Jira Transition Failed" and PROCEED next instruction.</action>
+  </check>
+
   1. **Extract Key**: Identify the Jira Key (e.g., PIJB-62) from the story content. Let's call it `{{jira_key}}`.
 
   2. **Transition Parent Story**:
@@ -117,7 +124,12 @@ To synchronize the "Done" status with Jira by transitioning the Story and its Su
   <output>Status is '{{new_status}}'. Skipping Jira sync because code review outcome is not 'done'.</output>
 </check>
 
-### 6. Finish Workflow
+### 6. Transition to Next Step
 <action>Update frontmatter of `{outputFile}`: `stepsCompleted: [1, 2, 3, 4, 5, 6]`</action>
-<output>🎉 Code Review Workflow Completed.</output>
-<action>EXIT</action>
+
+<output>Jira sync completed. Ready to commit and push changes.</output>
+
+<menu>
+   <item cmd="C" action="load_step" file="{nextStepFile}">Continue to Commit & Push</item>
+   <item cmd="E" action="exit">Exit Workflow (Skip Commit/Push)</item>
+</menu>

package/bmad/bmm/workflows/4-implementation/code-review/steps/step-07-commit-push.md

@@ -0,0 +1,160 @@
+---
+name: 'step-07-commit-push'
+description: 'Safely commit and push verified code to the repository'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmm/workflows/4-implementation/code-review'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-07-commit-push.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/review-{story_key}.md'
+
+# Data References
+sprint_status_file: '{implementation_artifacts}/sprint-status.yaml'
+epicsFile: '{output_folder}/planning-artifacts/epics.md'
+---
+
+# Step 7: Commit & Push
+
+## STEP GOAL:
+To securely persist the verified and approved code changes to the repository by validating the development branch and performing a git commit and push operation.
+
+## MANDATORY EXECUTION RULES:
+- 🛑 ONLY execute if the story status is explicitly 'done' or 'completed'
+- 🌳 Ensure development is on the correct `Feature/{Epic_Name}` branch
+- 📝 Commit messages must follow the standard format: "feat: implementation for story {{story_key}}"
+
+## Sequence of Instructions
+
+### 1. Verification of Status
+
+**Goal**: ensure we are authorized to push code.
+
+<action>
+1. Load `{sprint_status_file}`.
+2. Find the entry for `{{story_key}}` under `development_status`.
+3. Check if the value is `done` (or `completed`).
+</action>
+
+<check if="status != 'done' AND status != 'completed'">
+  <output>
+  ⚠️ **COMMIT ABORTED**: Story status is '{{status}}'.
+  Changes are only committed and pushed when the story is marked as 'done'.
+  </output>
+  <action>STOP execution. Do NOT run git commands.</action>
+</check>
+
+### 2. Branch Validation
+
+**Goal**: Ensure code is committed to the correct Epic feature branch.
+
+<check if="status == 'done' OR status == 'completed'">
+
+  <action>
+  1. Extract **Epic ID** from `{{story_key}}` (first number, e.g., '1' from '1-2-user-auth').
+  2. Load and read `{epicsFile}`.
+  3. Find the header matching `### Epic {Epic_ID}:`.
+  4. Extract the Epic Name (e.g., "Project Foundation").
+  5. Sanitize Epic Name (Pascal/Kebab case, replacing spaces with dashes: "Project-Foundation").
+  6. Construct `target_branch` = `Feature/{Sanitized_Epic_Name}`.
+  </action>
+
+  <action>Run command `git branch --show-current` to get `current_branch`.</action>
+
+  <check if="current_branch != target_branch">
+      <output>🔄 Switching branches (Current: {{current_branch}} -> Target: {{target_branch}})...</output>
+
+      <action>Check if target branch exists: `git branch --list {{target_branch}}`.</action>
+
+      <if condition="branch exists">
+          <action>Run `git checkout {{target_branch}}`.</action>
+          <output>✅ Switched to existing branch: {{target_branch}}</output>
+      </if>
+
+      <if condition="branch does NOT exist">
+          <action>Run `git checkout -b {{target_branch}}`.</action>
+          <output>✨ Created and switched to new branch: {{target_branch}}</output>
+      </if>
+  </check>
+
+  <check if="current_branch == target_branch">
+      <output>✅ Already on correct branch: {{target_branch}}</output>
+  </check>
+
+</check>
+
+### 3. Git Operations
+
+**Goal**: Persist changes.
+
+<check if="status == 'done' OR status == 'completed'">
+
+  1. **Stage Changes**:
+     <action>Run command `git add .`</action>
+
+  2. **User Confirmation**:
+     <output>
+     READY TO COMMIT:
+     - Branch: {{target_branch}}
+     - Message: "feat: implementation for story {{story_key}}"
+
+     Do you want to proceed with the commit and push?
+     </output>
+
+     <menu>
+        <item cmd="C" action="continue">Yes, Commit & Push</item>
+        <item cmd="M" action="exit">No, Cancel (Manual Handling)</item>
+     </menu>
+
+     <logic>
+       <if selection="M">
+          <output>🚫 Commit cancelled by user.</output>
+          <output>Changes are staged. You can now commit manually.</output>
+          <action>Update frontmatter of `{outputFile}`: `stepsCompleted: [1, 2, 3, 4, 5, 6, 7]`</action>
+          <action>EXIT</action>
+       </if>
+     </logic>
+
+  3. **Commit Changes**:
+     <action>Run command `git commit -m "feat: implementation for story {{story_key}}"`</action>
+     <check if="Commit failed (no changes?)">
+        <output>ℹ️ No changes to commit.</output>
+     </check>
+
+  4. **Push to Remote**:
+     <action>
+     1. Identify current branch (should be {{target_branch}} now): `git branch --show-current`
+     2. Push: `git push origin {{target_branch}}`
+     </action>
+
+     <check if="Push failed">
+        <output>❌ **Push Failed**. Please check your network or permissions and try pushing manually.</output>
+     </check>
+     <check if="Push success">
+        <output>✅ **Success**: Code pushed to origin.</output>
+     </check>
+
+</check>
+
+### 4. Final Logging
+
+<action>Append to `{outputFile}`:</action>
+<template-output>
+## Repository Sync
+- **Branch**: {{target_branch}}
+- **Commit**: [Performed/Skipped]
+- **Push**: [Performed/Skipped]
+- **Status**: Workflow Completed Successfully
+</template-output>
+
+### 5. Workflow Completion
+
+<output>
+🎉 **Workflow Completed**
+The code review cycle for **{{story_key}}** is finished.
+</output>
+
+<action>Update frontmatter of `{outputFile}`: `stepsCompleted: [1, 2, 3, 4, 5, 6, 7]`</action>
+
+<action>EXIT workflow.</action>

package/bmad/bmm/workflows/4-implementation/dev-story/steps/step-01-find-story.md

@@ -0,0 +1,109 @@
+---
+name: 'step-01-find-story'
+description: 'Find next ready story and load it'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmm/workflows/4-implementation/dev-story'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-01-find-story.md'
+nextStepFile: '{workflow_path}/steps/step-02-check-branch.md'
+configSource: '{project-root}/_bmad/bmm/config.yaml'
+
+# Context References
+sprintStatusFile: '{implementation_artifacts}/sprint-status.yaml'
+---
+
+# Step 1: Find Next Ready Story
+
+## STEP GOAL:
+
+To identify, locate, and load the correct story file for development, either from the sprint status or by direct search.
+
+## MANDATORY EXECUTION RULES:
+
+- 🛑 NEVER proceed without a valid story file
+- 📖 Read the entire step file first
+- 💾 Store `story_path` and `story_key` in memory for subsequent steps
+
+## EXECUTION PROTOCOLS:
+
+### 1. Check for Provided Story Path
+
+If `story_path` variable is already provided (e.g., passed by user):
+
+1.  Use `story_path` directly.
+2.  Read the COMPLETE story file.
+3.  Extract `story_key` from filename or metadata.
+4.  Proceed to **Completion**.
+
+### 2. Sprint-Based Discovery (Priority)
+
+Check if `{sprintStatusFile}` exists.
+
+**IF EXISTS:**
+
+1.  Load the FULL file `{sprintStatusFile}`.
+2.  Read all lines to understand story order.
+3.  Find the **FIRST** story where:
+    *   Key matches pattern: `number-number-name` (e.g., `1-2-user-auth`).
+    *   NOT an epic key (`epic-X`) or retrospective.
+    *   Status value equals `ready-for-dev`.
+
+**IF NO ready-for-dev story found:**
+
+1.  Display:
+    ```
+    📋 No ready-for-dev stories found in sprint-status.yaml
+    Current Sprint Status: [Summary]
+    ```
+2.  Ask user to choose:
+    *   [1] Run `create-story` (HALT and suggest command).
+    *   [2] Run `validate-create-story` (HALT and suggest command).
+    *   [3] Specify story file path manually.
+    *   [4] Review detailed sprint status.
+3.  **HALT** and wait for input.
+
+**IF ready-for-dev story found:**
+
+1.  Store `story_key` (e.g., "1-2-user-auth").
+2.  Find matching story file in `{story_dir}` (from config) using pattern `{{story_key}}.md`.
+3.  Read COMPLETE story file.
+4.  Proceed to **Completion**.
+
+### 3. Non-Sprint Discovery (Fallback)
+
+If `{sprintStatusFile}` does **NOT** exist:
+
+1.  Search `{story_dir}` for markdown files `*-*-*.md`.
+2.  Read files to find one with Status: `ready-for-dev`.
+3.  If none found, Ask user to specify path or run creation tools.
+4.  If found, use that file, extract `story_key`, and read content.
+
+### 4. Story Context Extraction
+
+Once story file is loaded (from any method above):
+
+1.  Parse sections: Story, Acceptance Criteria, Tasks/Subtasks, Dev Notes, Dev Agent Record, File List, Change Log, Status.
+2.  Load comprehensive context from Dev Notes (architecture, learnings, specs).
+3.  Identify first incomplete task (unchecked `[ ]`).
+    *   If no incomplete tasks: Inform user story seems complete.
+    *   If incomplete task found: Proceed.
+
+### 5. Completion and Next Step
+
+Once story is identified and loaded:
+
+1.  Display:
+    ```
+    ✅ Story Selected: {{story_key}}
+    Task: {{first_incomplete_task}}
+    ```
+2.  Load, read entire file, then execute `{nextStepFile}` (`step-02-check-branch.md`).
+
+---
+
+## CRITICAL:
+
+- Do NOT load next step if story is not found or file is unreadable.
+- If user input is required to pick a story, wait for it.

package/bmad/bmm/workflows/4-implementation/dev-story/steps/step-02-check-branch.md

@@ -0,0 +1,74 @@
+---
+name: 'step-02-check-branch'
+description: 'Validate and enforce Git branch naming convention'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmm/workflows/4-implementation/dev-story'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-02-check-branch.md'
+nextStepFile: '{workflow_path}/steps/step-03-load-context.md'
+epicsFile: '{output_folder}/planning-artifacts/epics.md'
+---
+
+# Step 2: Git Branch Validation
+
+## STEP GOAL:
+
+Ensure development occurs on the correct feature branch (`Feature/{Epic_Name}`) corresponding to the selected story's Epic.
+
+## MANDATORY EXECUTION RULES:
+
+- 🛑 NEVER start development on `main` or `develop` directly
+- 📖 Read `epics.md` to resolve Epic names
+- 🔄 Create or checkout the branch automatically
+
+## EXECUTION PROTOCOLS:
+
+### 1. Identify Epic
+
+Using the `story_key` identified in Step 1 (e.g., `1-2-user-auth`):
+
+1.  Extract the **Epic ID** (the first number).
+    *   Example: `1-2-user-auth` -> Epic ID = `1`.
+2.  Load and read `{epicsFile}`.
+3.  Find the Epic section matching this ID (e.g., `### Epic 1: Project Foundation & Configuration`).
+4.  Extract the **Epic Name** (e.g., `Project Foundation & Configuration`).
+
+### 2. Construct Branch Name
+
+1.  Sanitize the Epic Name to create a valid Git branch name:
+    *   Replace spaces with dashes `-`.
+    *   Remove special characters.
+    *   Use PascalCase or Kebab-Case as per project standard (Default to `Feature/Epic-Name-Sanitized`).
+    *   Example: `Feature/Project-Foundation-Configuration`.
+
+### 3. Check Current Branch
+
+1.  Run `git branch --show-current`.
+2.  Compare current branch with constructed `target_branch`.
+
+### 4. Enforce Branch
+
+**IF Current Branch == Target Branch:**
+-   Output: `✅ Already on correct branch: {{target_branch}}`
+-   Proceed to Next Step.
+
+**IF Current Branch != Target Branch:**
+1.  Check if `target_branch` exists: `git branch --list {{target_branch}}`.
+2.  **IF Exists:**
+    *   Run `git checkout {{target_branch}}`.
+    *   Output: `🔄 Switched to existing branch: {{target_branch}}`.
+3.  **IF Not Exists:**
+    *   Run `git checkout -b {{target_branch}}`.
+    *   Output: `✨ Created and switched to new branch: {{target_branch}}`.
+
+### 5. Validation Fallback
+
+If `epics.md` is missing or Epic cannot be identified:
+1.  Ask user: "Could not detect Epic name for Story {{story_key}}. Please provide the target branch name or Epic name."
+2.  Wait for input and create/switch manually.
+
+### 6. Next Step
+
+Load, read entire file, then execute `{nextStepFile}` (`step-03-load-context.md`).

package/bmad/bmm/workflows/4-implementation/dev-story/steps/step-03-load-context.md

@@ -0,0 +1,46 @@
+---
+name: 'step-03-load-context'
+description: 'Load project context and story information'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmm/workflows/4-implementation/dev-story'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-03-load-context.md'
+nextStepFile: '{workflow_path}/steps/step-04-env-readiness.md'
+projectContext: '{project-root}/_bmad-output/project-context.md'
+---
+
+# Step 3: Load Context
+
+## STEP GOAL:
+
+Load all available context to inform implementation, including coding standards, project-wide patterns, and specific story requirements.
+
+## EXECUTION PROTOCOLS:
+
+### 1. Load Project Context
+
+1.  Load `{projectContext}` (if exists) for coding standards and project-wide patterns.
+2.  Review architectural guidelines, tech stack details, and implementation patterns.
+
+### 2. Deep Dive Story Context
+
+1.  Re-read the **Dev Notes** section of the Story file.
+2.  Extract developer guidance:
+    *   Architecture requirements.
+    *   Previous learnings.
+    *   Technical specifications.
+3.  Use this enhanced context to inform implementation decisions.
+
+### 3. Output Status
+
+Display:
+```
+✅ Context Loaded
+Story and project context available for implementation.
+```
+
+### 4. Next Step
+
+Load, read entire file, then execute `{nextStepFile}` (`step-04-env-readiness.md`).

package/bmad/bmm/workflows/4-implementation/dev-story/steps/step-04-env-readiness.md

@@ -0,0 +1,45 @@
+---
+name: 'step-04-env-readiness'
+description: 'Analyze dependencies and ensure environment readiness'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmm/workflows/4-implementation/dev-story'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-04-env-readiness.md'
+nextStepFile: '{workflow_path}/steps/step-05-review-check.md'
+---
+
+# Step 4: Environment Readiness & UI Kit Check
+
+## STEP GOAL:
+
+Analyze tasks for UI requirements and ensure `siesa-ui-kit` is properly installed and configured if needed.
+
+## EXECUTION PROTOCOLS:
+
+### 1. Analyze for UI Requirements
+
+Scan the Story's Tasks and Acceptance Criteria for UI-related keywords:
+*   `table`, `form`, `view`, `css`, `style`, `component`
+*   `dark mode`, `modal`, `button`, `input`, `grid`, `layout`
+*   `theme`, `icon`, `frontend`, `interface`, `screen`
+*   `dialog`, `popup`, `widget`, `dashboard`, `chart`, `visualization`
+
+### 2. UI Kit Enforcement
+
+**IF NO UI keywords found:**
+1.  Output: `ℹ️ No specific UI tasks detected. Skipping siesa-ui-kit check.`
+
+**IF UI keywords found:**
+1.  **Install/Update**: Run `npm install siesa-ui-kit@latest`.
+    *   Output: `✅ siesa-ui-kit ensured at latest version.`
+2.  **Verify Import**:
+    *   Locate project main entry file (`src/app/layout.tsx`, `src/main.jsx`, etc.).
+    *   Read content to check for `siesa-ui-kit/styles.css`.
+    *   **If missing**: Add `import 'siesa-ui-kit/styles.css'` (or equivalent).
+    *   Output: `✅ Verified/Added 'siesa-ui-kit/styles.css' import.`
+
+### 3. Next Step
+
+Load, read entire file, then execute `{nextStepFile}` (`step-05-review-check.md`).

package/bmad/bmm/workflows/4-implementation/dev-story/steps/step-05-review-check.md

@@ -0,0 +1,57 @@
+---
+name: 'step-05-review-check'
+description: 'Detect review continuation and extract review context'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmm/workflows/4-implementation/dev-story'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-05-review-check.md'
+nextStepFile: '{workflow_path}/steps/step-06-mark-in-progress.md'
+---
+
+# Step 5: Review Context Check
+
+## STEP GOAL:
+
+Determine if this execution is a continuation after a code review or a fresh start.
+
+## EXECUTION PROTOCOLS:
+
+### 1. Check for Review Section
+
+Inspect the story file for:
+1.  Section: `Senior Developer Review (AI)`
+2.  Subsection in Tasks: `Review Follow-ups (AI)`
+
+### 2. Extract Review Context
+
+**IF Review Section EXISTS:**
+1.  Set `review_continuation = true`.
+2.  Extract:
+    *   Review Outcome (Approve/Changes Requested/Blocked).
+    *   Review Date.
+    *   Action Items (Count checked vs unchecked).
+    *   Severity Breakdown.
+3.  Count unchecked `[ ]` tasks in `Review Follow-ups (AI)`.
+4.  Store `pending_review_items` list.
+5.  Output:
+    ```
+    ⏯️ Resuming Story After Code Review
+    Outcome: {{review_outcome}}
+    Action Items: {{unchecked_review_count}} remaining
+    Strategy: Prioritize review follow-ups [AI-Review] first.
+    ```
+
+**IF Review Section DOES NOT EXIST:**
+1.  Set `review_continuation = false`.
+2.  Set `pending_review_items = empty`.
+3.  Output:
+    ```
+    🚀 Starting Fresh Implementation
+    Story: {{story_key}}
+    ```
+
+### 3. Next Step
+
+Load, read entire file, then execute `{nextStepFile}` (`step-06-mark-in-progress.md`).

package/bmad/bmm/workflows/4-implementation/dev-story/steps/step-06-mark-in-progress.md

@@ -0,0 +1,52 @@
+---
+name: 'step-06-mark-in-progress'
+description: 'Mark story in-progress in sprint status'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmm/workflows/4-implementation/dev-story'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-06-mark-in-progress.md'
+nextStepFile: '{workflow_path}/steps/step-07-implement.md'
+sprintStatusFile: '{implementation_artifacts}/sprint-status.yaml'
+---
+
+# Step 6: Update Sprint Status
+
+## STEP GOAL:
+
+Update the project's sprint status tracking to reflect that work has started on this story.
+
+## EXECUTION PROTOCOLS:
+
+### 1. Check Sprint Status File
+
+**IF `{sprintStatusFile}` EXISTS:**
+1.  Load the FULL file.
+2.  Find entry for `{{story_key}}` in `development_status`.
+3.  Check current status.
+
+### 2. Update Status
+
+**IF Current Status == 'ready-for-dev' OR `review_continuation == true`:**
+1.  Update status to `in-progress`.
+2.  Save file.
+3.  Output:
+    ```
+    🚀 Status updated: ready-for-dev → in-progress
+    ```
+
+**IF Current Status == 'in-progress':**
+1.  Output: `⏯️ Story already in-progress.`
+
+**IF Status Unknown/Other:**
+1.  Output: `⚠️ Unexpected status: {{current_status}}. Continuing...`
+
+### 3. Non-Sprint Tracking
+
+**IF `{sprintStatusFile}` DOES NOT EXIST:**
+1.  Output: `ℹ️ No sprint status file. Progress tracked in story file only.`
+
+### 4. Next Step
+
+Load, read entire file, then execute `{nextStepFile}` (`step-07-implement.md`).