From a2ea1d65aa6b0739e1b4d98ffdbba4579c9a6d2a Mon Sep 17 00:00:00 2001 From: Dave Date: Fri, 20 Mar 2026 08:30:20 +0000 Subject: [PATCH] story-kit: done 331_story_bot_start_command_to_start_a_coder_on_a_story --- ...art_command_to_start_a_coder_on_a_story.md | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 .story_kit/work/5_done/331_story_bot_start_command_to_start_a_coder_on_a_story.md diff --git a/.story_kit/work/5_done/331_story_bot_start_command_to_start_a_coder_on_a_story.md b/.story_kit/work/5_done/331_story_bot_start_command_to_start_a_coder_on_a_story.md new file mode 100644 index 0000000..6f482e5 --- /dev/null +++ b/.story_kit/work/5_done/331_story_bot_start_command_to_start_a_coder_on_a_story.md @@ -0,0 +1,23 @@ +--- +name: "Bot start command to start a coder on a story" +--- + +# Story 331: Bot start command to start a coder on a story + +## User Story + +As a project owner in a chat room, I want to type "{bot_name} start {story_number}" to start a coder on a story, so that I can kick off work without needing the MCP tools or web UI. + +## Acceptance Criteria + +- [ ] '{bot_name} start {number}' finds the story and starts the default coder agent on it +- [ ] '{bot_name} start {number} opus' starts coder-opus specifically +- [ ] Returns confirmation with agent name and story title +- [ ] Returns error if story not found or all coders busy +- [ ] Moves story from backlog to current if needed +- [ ] Registered in the command registry so it appears in help output +- [ ] Handled at bot level without LLM invocation + +## Out of Scope + +- TBD