From 4fe61c643b024bf881cb040ce1844d43e4bce98d Mon Sep 17 00:00:00 2001 From: Dave Date: Fri, 20 Mar 2026 01:07:19 +0000 Subject: [PATCH] story-kit: create 327_story_bot_overview_command_shows_implementation_summary_for_a_story --- ..._slack_bot_integration_for_bot_commands.md | 24 ------------------- ...hows_implementation_summary_for_a_story.md | 23 ++++++++++++++++++ 2 files changed, 23 insertions(+), 24 deletions(-) delete mode 100644 .story_kit/work/1_backlog/324_story_slack_bot_integration_for_bot_commands.md create mode 100644 .story_kit/work/1_backlog/327_story_bot_overview_command_shows_implementation_summary_for_a_story.md diff --git a/.story_kit/work/1_backlog/324_story_slack_bot_integration_for_bot_commands.md b/.story_kit/work/1_backlog/324_story_slack_bot_integration_for_bot_commands.md deleted file mode 100644 index a41edbd..0000000 --- a/.story_kit/work/1_backlog/324_story_slack_bot_integration_for_bot_commands.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -name: "Slack bot integration for bot commands" ---- - -# Story 324: Slack bot integration for bot commands - -## User Story - -As a project owner, I want to interact with the bot via Slack using the Slack Events API, so that I can manage the pipeline from Slack alongside Matrix and WhatsApp. - -## Acceptance Criteria - -- [ ] Implement SlackTransport using the ChatTransport trait from refactor 316 -- [ ] Webhook endpoint at /webhook/slack receives incoming messages via Slack Events API -- [ ] URL verification handshake (challenge response) implemented -- [ ] Outbound replies sent via chat.postMessage using Bot token -- [ ] Message editing supported via chat.update (htop works natively) -- [ ] Slack config in bot.toml: slack_bot_token, slack_signing_secret, slack_channel_ids, enabled flag -- [ ] bot.toml.example documents the Slack fields -- [ ] All bot commands work (help, status, cost, git, show, delete, ambient, htop with native editing) - -## Out of Scope - -- TBD diff --git a/.story_kit/work/1_backlog/327_story_bot_overview_command_shows_implementation_summary_for_a_story.md b/.story_kit/work/1_backlog/327_story_bot_overview_command_shows_implementation_summary_for_a_story.md new file mode 100644 index 0000000..a218073 --- /dev/null +++ b/.story_kit/work/1_backlog/327_story_bot_overview_command_shows_implementation_summary_for_a_story.md @@ -0,0 +1,23 @@ +--- +name: "Bot overview command shows implementation summary for a story" +--- + +# Story 327: Bot overview command shows implementation summary for a story + +## User Story + +As a project owner in a Matrix room, I want to type "{bot_name} overview {story_number}" and see a summary of what was implemented for that story, so that I can understand the scope of changes without reading code or asking the bot to investigate. + +## Acceptance Criteria + +- [ ] '{bot_name} overview {number}' finds the story's merge commit or feature branch on master +- [ ] Shows git diff --stat (files changed with line counts) +- [ ] Extracts key function/struct/type names added or modified from the diff +- [ ] Shows a compact summary formatted for Matrix chat +- [ ] Returns a friendly message if no implementation found (story still in backlog or ghost) +- [ ] Registered in the command registry so it appears in help output +- [ ] Handled at bot level without LLM invocation — uses git commands only + +## Out of Scope + +- TBD