From 07fe5c20267f247fe029e3dcaed7ed6f09ab3798 Mon Sep 17 00:00:00 2001 From: Dave Date: Mon, 23 Feb 2026 12:48:13 +0000 Subject: [PATCH] story-kit: create 67_story_server_drives_pipeline_as_state_machine --- .../67_story_server_drives_pipeline_as_state_machine.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.story_kit/work/1_upcoming/67_story_server_drives_pipeline_as_state_machine.md b/.story_kit/work/1_upcoming/67_story_server_drives_pipeline_as_state_machine.md index 01e7eb9..8b1a4b6 100644 --- a/.story_kit/work/1_upcoming/67_story_server_drives_pipeline_as_state_machine.md +++ b/.story_kit/work/1_upcoming/67_story_server_drives_pipeline_as_state_machine.md @@ -14,7 +14,8 @@ As a Story Kit user, I want the server to automatically advance stories through - [ ] When a coder agent completes, the server automatically runs script/test in the worktree - [ ] If script/test passes (exit 0), the server moves the story to work/3_qa/ and starts the QA agent - [ ] If script/test fails (non-zero), the server restarts the coder with failure output -- [ ] When the QA agent completes, the server moves the story to work/4_merge/ and starts the mergemaster +- [ ] When the QA agent completes, the server runs script/test in the worktree — if non-zero, restarts the QA agent with failure output +- [ ] If script/test passes after QA, the server moves the story to work/4_merge/ and starts the mergemaster - [ ] When the mergemaster completes successfully, the server moves the story to work/5_archived/ and cleans up the worktree - [ ] Agents no longer need to call move_story_to_merge, request_qa, or any pipeline-advancing MCP tools — the server handles all transitions - [ ] The completion handler in agents.rs reacts to AgentStatus::Completed and triggers the next stage