From 75640c6ecf0b54b35a63a166f2b44945be80d12a Mon Sep 17 00:00:00 2001 From: Dave Date: Fri, 20 Mar 2026 08:39:45 +0000 Subject: [PATCH] story-kit: done 334_story_bot_move_command_to_move_stories_between_pipeline_stages --- ...to_move_stories_between_pipeline_stages.md | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 .story_kit/work/5_done/334_story_bot_move_command_to_move_stories_between_pipeline_stages.md diff --git a/.story_kit/work/5_done/334_story_bot_move_command_to_move_stories_between_pipeline_stages.md b/.story_kit/work/5_done/334_story_bot_move_command_to_move_stories_between_pipeline_stages.md new file mode 100644 index 0000000..6deda7c --- /dev/null +++ b/.story_kit/work/5_done/334_story_bot_move_command_to_move_stories_between_pipeline_stages.md @@ -0,0 +1,22 @@ +--- +name: "Bot move command to move stories between pipeline stages" +--- + +# Story 334: Bot move command to move stories between pipeline stages + +## User Story + +As a project owner in a chat room, I want to type "{bot_name} move {story_number} {stage}" to move a story between pipeline stages, so that I can manage the pipeline from chat. + +## Acceptance Criteria + +- [ ] '{bot_name} move {number} {stage}' moves the story to the specified stage (backlog, current, done) +- [ ] Uses the existing move_story MCP tool under the hood +- [ ] Returns confirmation with story title, old stage, and new stage +- [ ] Returns error if story not found or invalid stage +- [ ] Registered in the command registry so it appears in help output +- [ ] Handled at bot level without LLM invocation + +## Out of Scope + +- TBD