feat: wire story automator routing

docs/reference/agents.md

@@ -20,7 +20,7 @@ This page lists the default BMM (Agile suite) agents that install with BMad Meth
 | Analyst (Mary)              | `bmad-analyst`       | `BP`, `RS`, `CB`, `DP`             | Brainstorm Project, Research, Create Brief, Document Project                                        |
 | Product Manager (John)      | `bmad-pm`            | `CP`, `VP`, `EP`, `CE`, `IR`, `CC` | Create/Validate/Edit PRD, Create Epics and Stories, Implementation Readiness, Correct Course        |
 | Architect (Winston)         | `bmad-architect`     | `CA`, `IR`                         | Create Architecture, Implementation Readiness                                                       |
-| Scrum Master (Bob)          | `bmad-sm`            | `SP`, `CS`, `ER`, `CC`             | Sprint Planning, Create Story, Epic Retrospective, Correct Course                                   |
+| Scrum Master (Bob)          | `bmad-sm`            | `SP`, `SA`, `CS`, `ER`, `CC`       | Sprint Planning, Story Automator, Create Story, Epic Retrospective, Correct Course                  |
 | Developer (Amelia)          | `bmad-dev`           | `DS`, `CR`                         | Dev Story, Code Review                                                                              |
 | QA Engineer (Quinn)         | `bmad-qa`            | `QA`                               | Automate (generate tests for existing features)                                                     |
 | Quick Flow Solo Dev (Barry) | `bmad-master`        | `QD`, `CR`                          | Quick Dev, Code Review                                                                              |

docs/reference/commands.md

@@ -95,6 +95,7 @@ Workflow skills run a structured, multi-step process without loading an agent pe
 | `bmad-create-prd` | Create a Product Requirements Document |
 | `bmad-create-architecture` | Design system architecture |
 | `bmad-create-epics-and-stories` | Create epics and stories |
+| `bmad-story-automator-go` | Automate the multi-story Phase 4 loop |
 | `bmad-dev-story` | Implement a story |
 | `bmad-code-review` | Run a code review |
 | `bmad-quick-dev` | Unified quick flow — clarify intent, plan, implement, review, present |

docs/reference/workflow-map.md

@@ -50,11 +50,12 @@ Decide how to build it and break work into stories.
 
 ## Phase 4: Implementation
 
-Build it, one story at a time. Coming soon, full phase 4 automation!
+Build it one story at a time, or automate the full loop once sprint planning and the project foundation are stable.
 
 | Workflow                   | Purpose                                                                  | Produces                         |
 | -------------------------- | ------------------------------------------------------------------------ | -------------------------------- |
 | `bmad-sprint-planning` | Initialize tracking (once per project to sequence the dev cycle)         | `sprint-status.yaml`          |
+| `bmad-story-automator-go` | Automate the story loop across create, dev, tests, review, and retro     | Story automator state + commits |
 | `bmad-create-story`    | Prepare next story for implementation                                    | `story-[slug].md`             |
 | `bmad-dev-story`       | Implement the story                                                      | Working code + tests          |
 | `bmad-code-review`     | Validate implementation quality                                          | Approved or changes requested |

src/bmm-skills/4-implementation/bmad-agent-sm/SKILL.md

@@ -31,6 +31,7 @@ When you are in this persona and the user calls a skill, this persona must carry
 | Code | Description | Skill |
 |------|-------------|-------|
 | SP | Generate or update the sprint plan that sequences tasks for the dev agent to follow | bmad-sprint-planning |
+| SA | Automate the multi-story implementation loop after sprint planning is ready | bmad-story-automator-go |
 | CS | Prepare a story with all required context for implementation by the developer agent | bmad-create-story |
 | ER | Party mode review of all work completed across an epic | bmad-retrospective |
 | CC | Determine how to proceed if major need for change is discovered mid implementation | bmad-correct-course |

src/bmm-skills/4-implementation/bmad-story-automator-go/data/agent-fallback-troubleshooting.md

@@ -1,6 +1,6 @@
 # Agent Fallback Troubleshooting
 
-### Issue: Session spawns Claude instead of Codex
+## Issue: Session spawns Claude instead of Codex
 
 **Symptoms:**
 - Output shows Claude-specific messages (e.g., "You've used 84% of your weekly limit")
@@ -28,7 +28,7 @@ session=$("$scripts" tmux-wrapper spawn dev "$epic" "$story_id" \
   --command "$("$scripts" tmux-wrapper build-cmd dev "$story_id" --agent codex)")
 ```
 
-### Issue: Monitor reports "stuck" but Codex is active
+## Issue: Monitor reports "stuck" but Codex is active
 
 **Symptoms:**
 - `story-automator monitor-session` returns `stuck` state after 4 polls
@@ -50,7 +50,7 @@ tmux show-environment -t "session-name" AI_AGENT
 "$scripts" tmux-status-check "session-name" --project-root "$PWD"
 ```
 
-### Issue: log command error when using --agent flag
+## Issue: log command error when using --agent flag
 
 **Symptoms:**
 ```
@@ -61,7 +61,7 @@ log: Unknown subcommand 'Codex agent detected - applying 1.5x timeout (90min)'
 
 **Fixed in v1.4.0:** The `log()` function is now defined before argument parsing in `story-automator monitor-session`.
 
-### Issue: Manual polling required as workaround
+## Issue: Manual polling required as workaround
 
 **If monitoring still fails**, use this manual polling approach:
 ```bash

src/bmm-skills/4-implementation/bmad-story-automator-go/data/tmux-commands.md

@@ -25,7 +25,7 @@
 project_slug=$(basename "$PWD" | tr '[:upper:]' '[:lower:]' | tr -cd '[:alnum:]' | cut -c1-8)
 ```
 
-**Example:** Project at `/home/user/my-awesome-project` → `project_slug="myawesom"`
+**Example:** Project at `./my-awesome-project` → `project_slug="myawesom"`
 
 **Why timestamps with seconds (v2.1):**
 - Prevents collisions when multiple sessions spawn in same minute

src/bmm-skills/4-implementation/bmad-story-automator-review/instructions.xml

@@ -1,5 +1,4 @@
 <workflow>
-  <critical>The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml</critical>
   <critical>You MUST have already loaded and processed: ./workflow.yaml</critical>
   <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>

src/bmm-skills/4-implementation/bmad-story-automator-review/workflow.yaml

@@ -16,4 +16,4 @@ sprint_status: "{implementation_artifacts}/sprint-status.yaml"
 # Workflow components
 instructions: "./instructions.xml"
 validation: "./checklist.md"
-standalone: true
+standalone: true

src/bmm-skills/module-help.csv

@@ -21,6 +21,7 @@ BMad Method,bmad-create-architecture,Create Architecture,CA,Guided workflow to d
 BMad Method,bmad-create-epics-and-stories,Create Epics and Stories,CE,,,3-solutioning,bmad-create-architecture,,true,planning_artifacts,epics and stories
 BMad Method,bmad-check-implementation-readiness,Check Implementation Readiness,IR,Ensure PRD UX Architecture and Epics Stories are aligned.,,3-solutioning,bmad-create-epics-and-stories,,true,planning_artifacts,readiness report
 BMad Method,bmad-sprint-planning,Sprint Planning,SP,Kicks off implementation by producing a plan the implementation agents will follow in sequence for every story.,,4-implementation,,,true,implementation_artifacts,sprint status
+BMad Method,bmad-story-automator-go,Story Automator,SA,Automate the Phase 4 story loop across create dev automate review and retrospective using tmux-managed child sessions.,,4-implementation,bmad-sprint-planning,,false,implementation_artifacts,story automator state
 BMad Method,bmad-sprint-status,Sprint Status,SS,Anytime: Summarize sprint status and route to next workflow.,,4-implementation,bmad-sprint-planning,,false,,
 BMad Method,bmad-create-story,Create Story,CS,"Story cycle start: Prepare first found story in the sprint plan that is next or a specific epic/story designation.",create,,4-implementation,bmad-sprint-planning,bmad-create-story:validate,true,implementation_artifacts,story
 BMad Method,bmad-create-story,Validate Story,VS,Validates story readiness and completeness before development work begins.,validate,,4-implementation,bmad-create-story:create,bmad-dev-story,false,implementation_artifacts,story validation report