From 7c9b86c31b5ffdc15140b3b2859a656e89e08837 Mon Sep 17 00:00:00 2001 From: Dave Date: Thu, 19 Mar 2026 10:44:14 +0000 Subject: [PATCH] story-kit: create 304_story_mcp_tool_to_move_stories_between_pipeline_stages --- ...304_story_mcp_tool_to_move_stories_between_pipeline_stages.md | 1 + 1 file changed, 1 insertion(+) diff --git a/.story_kit/work/1_backlog/304_story_mcp_tool_to_move_stories_between_pipeline_stages.md b/.story_kit/work/1_backlog/304_story_mcp_tool_to_move_stories_between_pipeline_stages.md index 1c001d7..152452b 100644 --- a/.story_kit/work/1_backlog/304_story_mcp_tool_to_move_stories_between_pipeline_stages.md +++ b/.story_kit/work/1_backlog/304_story_mcp_tool_to_move_stories_between_pipeline_stages.md @@ -16,6 +16,7 @@ As a bot operator (Timmy), I want an MCP tool that moves stories between pipelin - [ ] Returns a confirmation message with the old and new stage - [ ] Works for stories, bugs, spikes, and refactors - [ ] Replaces the need for shell mv commands to move story files +- [ ] Tool description tells bots to prefer specific tools (accept_story, move_story_to_merge, request_qa) when available, and use move_story only for arbitrary moves that lack a dedicated tool (e.g. moving to backlog, moving ghost stories back to current) ## Out of Scope