From c7846c041cf466b03660b47794301599b99ce6e2 Mon Sep 17 00:00:00 2001 From: Dave Date: Fri, 20 Mar 2026 08:23:10 +0000 Subject: [PATCH] story-kit: create 341_story_rename_story_kit_directory_to_storkit --- ...art_command_to_start_a_coder_on_a_story.md | 23 ----------------- ...d_to_assign_a_specific_agent_to_a_story.md | 24 ------------------ ...top_command_to_stop_an_agent_on_a_story.md | 21 ---------------- ...to_move_stories_between_pipeline_stages.md | 22 ---------------- ...d_to_trigger_server_rebuild_and_restart.md | 20 --------------- ...b_ui_button_to_start_a_coder_on_a_story.md | 21 ---------------- ...b_ui_button_to_stop_an_agent_on_a_story.md | 20 --------------- ...to_move_stories_between_pipeline_stages.md | 21 ---------------- ...agent_assignment_dropdown_on_work_items.md | 21 ---------------- ...story_web_ui_rebuild_and_restart_button.md | 21 ---------------- ...y_rename_story_kit_directory_to_storkit.md | 25 +++++++++++++++++++ 11 files changed, 25 insertions(+), 214 deletions(-) delete mode 100644 .story_kit/work/1_backlog/331_story_bot_start_command_to_start_a_coder_on_a_story.md delete mode 100644 .story_kit/work/1_backlog/332_story_bot_assign_command_to_assign_a_specific_agent_to_a_story.md delete mode 100644 .story_kit/work/1_backlog/333_story_bot_stop_command_to_stop_an_agent_on_a_story.md delete mode 100644 .story_kit/work/1_backlog/334_story_bot_move_command_to_move_stories_between_pipeline_stages.md delete mode 100644 .story_kit/work/1_backlog/335_story_bot_rebuild_command_to_trigger_server_rebuild_and_restart.md delete mode 100644 .story_kit/work/1_backlog/336_story_web_ui_button_to_start_a_coder_on_a_story.md delete mode 100644 .story_kit/work/1_backlog/337_story_web_ui_button_to_stop_an_agent_on_a_story.md delete mode 100644 .story_kit/work/1_backlog/338_story_web_ui_button_to_move_stories_between_pipeline_stages.md delete mode 100644 .story_kit/work/1_backlog/339_story_web_ui_agent_assignment_dropdown_on_work_items.md delete mode 100644 .story_kit/work/1_backlog/340_story_web_ui_rebuild_and_restart_button.md create mode 100644 .story_kit/work/1_backlog/341_story_rename_story_kit_directory_to_storkit.md diff --git a/.story_kit/work/1_backlog/331_story_bot_start_command_to_start_a_coder_on_a_story.md b/.story_kit/work/1_backlog/331_story_bot_start_command_to_start_a_coder_on_a_story.md deleted file mode 100644 index 6f482e5..0000000 --- a/.story_kit/work/1_backlog/331_story_bot_start_command_to_start_a_coder_on_a_story.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -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 diff --git a/.story_kit/work/1_backlog/332_story_bot_assign_command_to_assign_a_specific_agent_to_a_story.md b/.story_kit/work/1_backlog/332_story_bot_assign_command_to_assign_a_specific_agent_to_a_story.md deleted file mode 100644 index 000de6d..0000000 --- a/.story_kit/work/1_backlog/332_story_bot_assign_command_to_assign_a_specific_agent_to_a_story.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -name: "Bot assign command to assign a specific agent to a story" ---- - -# Story 332: Bot assign command to assign a specific agent to a story - -## User Story - -As a project owner in a chat room, I want to type "{bot_name} assign {story_number} {agent_name}" to assign a specific agent to a story, so that I can control which agent works on which story from chat. - -## Acceptance Criteria - -- [ ] '{bot_name} assign {number} {agent}' assigns the specified agent to the story (e.g. 'timmy assign 315 coder-opus') -- [ ] Stops any currently running agent on that story before assigning the new one -- [ ] Updates the story's front matter with agent: {agent_name} -- [ ] Starts the agent immediately -- [ ] Returns confirmation with agent name and story title -- [ ] Returns error if agent name is not valid or story not found -- [ ] Registered in the command registry so it appears in help output -- [ ] Handled at bot level without LLM invocation - -## Out of Scope - -- TBD diff --git a/.story_kit/work/1_backlog/333_story_bot_stop_command_to_stop_an_agent_on_a_story.md b/.story_kit/work/1_backlog/333_story_bot_stop_command_to_stop_an_agent_on_a_story.md deleted file mode 100644 index ec14419..0000000 --- a/.story_kit/work/1_backlog/333_story_bot_stop_command_to_stop_an_agent_on_a_story.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -name: "Bot stop command to stop an agent on a story" ---- - -# Story 333: Bot stop command to stop an agent on a story - -## User Story - -As a project owner in a chat room, I want to type "{bot_name} stop {story_number}" to stop the running agent on a story, so that I can halt work from chat without MCP tools. - -## Acceptance Criteria - -- [ ] '{bot_name} stop {number}' stops the running agent on that story -- [ ] Returns confirmation with agent name, story title, and what stage it was in -- [ ] Returns friendly message if no agent is running on that story -- [ ] Registered in the command registry so it appears in help output -- [ ] Handled at bot level without LLM invocation - -## Out of Scope - -- TBD diff --git a/.story_kit/work/1_backlog/334_story_bot_move_command_to_move_stories_between_pipeline_stages.md b/.story_kit/work/1_backlog/334_story_bot_move_command_to_move_stories_between_pipeline_stages.md deleted file mode 100644 index 6deda7c..0000000 --- a/.story_kit/work/1_backlog/334_story_bot_move_command_to_move_stories_between_pipeline_stages.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -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 diff --git a/.story_kit/work/1_backlog/335_story_bot_rebuild_command_to_trigger_server_rebuild_and_restart.md b/.story_kit/work/1_backlog/335_story_bot_rebuild_command_to_trigger_server_rebuild_and_restart.md deleted file mode 100644 index 3c1602b..0000000 --- a/.story_kit/work/1_backlog/335_story_bot_rebuild_command_to_trigger_server_rebuild_and_restart.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -name: "Bot rebuild command to trigger server rebuild and restart" ---- - -# Story 335: Bot rebuild command to trigger server rebuild and restart - -## User Story - -As a project owner in a chat room, I want to type "{bot_name} rebuild" to rebuild and restart the server, so that I can deploy changes from my phone without terminal access. - -## Acceptance Criteria - -- [ ] '{bot_name} rebuild' triggers the rebuild_and_restart MCP tool -- [ ] Bot sends a confirmation message before rebuilding -- [ ] Handled at bot level — intercepts the command before forwarding to LLM -- [ ] Registered in the command registry so it appears in help output - -## Out of Scope - -- TBD diff --git a/.story_kit/work/1_backlog/336_story_web_ui_button_to_start_a_coder_on_a_story.md b/.story_kit/work/1_backlog/336_story_web_ui_button_to_start_a_coder_on_a_story.md deleted file mode 100644 index aa7ff1b..0000000 --- a/.story_kit/work/1_backlog/336_story_web_ui_button_to_start_a_coder_on_a_story.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -name: "Web UI button to start a coder on a story" ---- - -# Story 336: Web UI button to start a coder on a story - -## User Story - -As a project owner using the web UI, I want to click a button on a work item to start a coder on it, so that I can kick off work without using the terminal or chat bot. - -## Acceptance Criteria - -- [ ] Start button visible on work items in backlog and current stages -- [ ] Clicking start assigns the default coder and moves the story to current if needed -- [ ] Option to select a specific agent (dropdown: coder-1, coder-2, coder-opus) -- [ ] Button disabled when all coders are busy (shows tooltip explaining why) -- [ ] UI updates immediately to show the assigned agent - -## Out of Scope - -- TBD diff --git a/.story_kit/work/1_backlog/337_story_web_ui_button_to_stop_an_agent_on_a_story.md b/.story_kit/work/1_backlog/337_story_web_ui_button_to_stop_an_agent_on_a_story.md deleted file mode 100644 index a709673..0000000 --- a/.story_kit/work/1_backlog/337_story_web_ui_button_to_stop_an_agent_on_a_story.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -name: "Web UI button to stop an agent on a story" ---- - -# Story 337: Web UI button to stop an agent on a story - -## User Story - -As a project owner using the web UI, I want to click a button on a work item to stop its running agent, so that I can halt work without using the terminal or chat bot. - -## Acceptance Criteria - -- [ ] Stop button visible on work items that have a running agent -- [ ] Clicking stop kills the agent and shows confirmation -- [ ] Button only appears when an agent is actively running -- [ ] UI updates immediately to reflect the agent is stopped - -## Out of Scope - -- TBD diff --git a/.story_kit/work/1_backlog/338_story_web_ui_button_to_move_stories_between_pipeline_stages.md b/.story_kit/work/1_backlog/338_story_web_ui_button_to_move_stories_between_pipeline_stages.md deleted file mode 100644 index 0d813a5..0000000 --- a/.story_kit/work/1_backlog/338_story_web_ui_button_to_move_stories_between_pipeline_stages.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -name: "Web UI button to move stories between pipeline stages" ---- - -# Story 338: Web UI button to move stories between pipeline stages - -## User Story - -As a project owner using the web UI, I want to drag or click to move stories between pipeline stages, so that I can manage the pipeline visually. - -## Acceptance Criteria - -- [ ] Move buttons or dropdown on each work item to change stage (backlog, current, done) -- [ ] Uses the existing move_story MCP tool under the hood -- [ ] Shows confirmation with old and new stage -- [ ] UI updates immediately to reflect the move -- [ ] Prevents invalid moves (e.g. moving to QA or merge without an agent) - -## Out of Scope - -- TBD diff --git a/.story_kit/work/1_backlog/339_story_web_ui_agent_assignment_dropdown_on_work_items.md b/.story_kit/work/1_backlog/339_story_web_ui_agent_assignment_dropdown_on_work_items.md deleted file mode 100644 index 2f2fd6e..0000000 --- a/.story_kit/work/1_backlog/339_story_web_ui_agent_assignment_dropdown_on_work_items.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -name: "Web UI agent assignment dropdown on work items" ---- - -# Story 339: Web UI agent assignment dropdown on work items - -## User Story - -As a project owner using the web UI, I want to select which agent to assign to a work item from a dropdown, so that I can control agent assignments visually. - -## Acceptance Criteria - -- [ ] Agent dropdown visible in expanded work item detail panel -- [ ] Shows available agents filtered by appropriate stage (coders for current, QA for qa, mergemaster for merge) -- [ ] Selecting an agent stops any current agent and starts the new one -- [ ] Updates the story front matter with the agent assignment -- [ ] Shows agent status (running, idle) in the dropdown - -## Out of Scope - -- TBD diff --git a/.story_kit/work/1_backlog/340_story_web_ui_rebuild_and_restart_button.md b/.story_kit/work/1_backlog/340_story_web_ui_rebuild_and_restart_button.md deleted file mode 100644 index 4318bec..0000000 --- a/.story_kit/work/1_backlog/340_story_web_ui_rebuild_and_restart_button.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -name: "Web UI rebuild and restart button" ---- - -# Story 340: Web UI rebuild and restart button - -## User Story - -As a project owner using the web UI, I want a rebuild and restart button, so that I can deploy changes without terminal access. - -## Acceptance Criteria - -- [ ] Rebuild button in the web UI header or settings area -- [ ] Shows confirmation dialog before triggering rebuild -- [ ] Triggers the rebuild_and_restart MCP tool -- [ ] Shows build progress or status indicator -- [ ] Handles reconnection after server restarts - -## Out of Scope - -- TBD diff --git a/.story_kit/work/1_backlog/341_story_rename_story_kit_directory_to_storkit.md b/.story_kit/work/1_backlog/341_story_rename_story_kit_directory_to_storkit.md new file mode 100644 index 0000000..e16869a --- /dev/null +++ b/.story_kit/work/1_backlog/341_story_rename_story_kit_directory_to_storkit.md @@ -0,0 +1,25 @@ +--- +name: "Rename .story_kit directory to .storkit" +--- + +# Story 341: Rename .story_kit directory to .storkit + +## User Story + +As a project owner, I want the config directory renamed from .story_kit to .storkit, so that the directory name matches the new binary and product name. + +## Acceptance Criteria + +- [ ] Rename the physical directory from .story_kit to .storkit +- [ ] All server code references to .story_kit paths updated to .storkit +- [ ] All .gitignore references updated +- [ ] bot.toml and project.toml paths updated +- [ ] CLAUDE.md references updated +- [ ] Watcher, worktree, and pipeline code updated +- [ ] MCP tool descriptions updated if they reference .story_kit +- [ ] Agent prompts updated if they reference .story_kit +- [ ] Backwards compatible: if .storkit doesn't exist but .story_kit does, use .story_kit with a deprecation warning + +## Out of Scope + +- TBD