story-kit: accept 63_story_auto_spawn_mergemaster_on_merge
This commit is contained in:
@@ -1,24 +0,0 @@
|
||||
---
|
||||
name: Auto-Spawn Mergemaster on Move to Merge
|
||||
test_plan: pending
|
||||
---
|
||||
|
||||
# Story 63: Auto-Spawn Mergemaster on Move to Merge
|
||||
|
||||
## User Story
|
||||
|
||||
As an agent completing work on a story, when I call `move_story_to_merge`, the mergemaster agent should start automatically so I don't need to know how to spawn agents or understand the pipeline topology.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] `move_story_to_merge` MCP tool moves the story file to `work/4_merge/` AND starts the mergemaster agent on that story's worktree (same pattern as `request_qa`)
|
||||
- [ ] The tool returns JSON with story_id, agent_name, status, worktree_path, and a message (matching `request_qa` response shape)
|
||||
- [ ] The tool accepts an optional `agent_name` parameter, defaulting to `"mergemaster"`
|
||||
- [ ] The tool description is updated to reflect that it spawns the mergemaster agent
|
||||
- [ ] Existing tests are updated to reflect the new async behavior
|
||||
|
||||
## Out of Scope
|
||||
|
||||
- Changing the `request_qa` tool
|
||||
- Adding new pipeline stages
|
||||
- Changing how `start_agent` works internally
|
||||
Reference in New Issue
Block a user