dave/storkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 7 Wiki Activity

story-kit: create 67_story_server_drives_pipeline_as_state_machine

Browse Source
This commit is contained in:
Dave
2026-02-23 12:48:13 +00:00
parent 1fe9ea2015
commit 07fe5c2026
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
.story_kit/work/1_upcoming/67_story_server_drives_pipeline_as_state_machine.md
View File

@@ -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 - [ ] 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 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 - [ ] 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 - [ ] 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 - [ ] 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 - [ ] The completion handler in agents.rs reacts to AgentStatus::Completed and triggers the next stage