From b71e8dd2bee7ebf9b1dec6dd47f414725f797e11 Mon Sep 17 00:00:00 2001 From: Dave Date: Thu, 19 Mar 2026 15:43:11 +0000 Subject: [PATCH] story-kit: create 310_story_bot_delete_command_removes_a_story_from_the_pipeline --- ...mmand_removes_a_story_from_the_pipeline.md | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 .story_kit/work/1_backlog/310_story_bot_delete_command_removes_a_story_from_the_pipeline.md diff --git a/.story_kit/work/1_backlog/310_story_bot_delete_command_removes_a_story_from_the_pipeline.md b/.story_kit/work/1_backlog/310_story_bot_delete_command_removes_a_story_from_the_pipeline.md new file mode 100644 index 0000000..530d8f3 --- /dev/null +++ b/.story_kit/work/1_backlog/310_story_bot_delete_command_removes_a_story_from_the_pipeline.md @@ -0,0 +1,24 @@ +--- +name: "Bot delete command removes a story from the pipeline" +--- + +# Story 310: Bot delete command removes a story from the pipeline + +## User Story + +As a project owner in a Matrix room, I want to type "{bot_name} delete {story_number}" to remove a story/bug/spike from the pipeline, so that I can clean up obsolete or duplicate work items from chat. + +## Acceptance Criteria + +- [ ] '{bot_name} delete {number}' finds the story/bug/spike by number across all pipeline stages and deletes the file +- [ ] Confirms deletion with the story name and stage it was in +- [ ] Returns a friendly message if no story with that number exists +- [ ] Stops any running agent on the story before deleting +- [ ] Removes the worktree if one exists for the story +- [ ] Registered in the command registry so it appears in help output +- [ ] Handled at bot level without LLM invocation +- [ ] Commits the deletion to git + +## Out of Scope + +- TBD