dave/storkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 7 Wiki Activity

story-kit: done 327_story_bot_overview_command_shows_implementation_summary_for_a_story

Browse Source
This commit is contained in:
Dave
2026-03-20 01:22:13 +00:00
parent 14cab448cb
commit ff1705f26c
3 changed files with 23 additions and 42 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
.story_kit/work/1_backlog/325_story_slack_llm_passthrough_for_conversational_queries.md
View File

@@ -1,21 +0,0 @@
---
name: "Slack LLM passthrough for conversational queries"
---
# Story 325: Slack LLM passthrough for conversational queries
## User Story
As a project owner using Slack, I want messages that aren't bot commands to be forwarded to Claude for conversational responses, so that I can ask questions about the project naturally from Slack.
## Acceptance Criteria
- [ ] Messages that don't match any bot command are forwarded to Claude via the existing LLM pipeline
- [ ] Responses sent back as Slack messages
- [ ] Conversation history maintained per channel
- [ ] Long responses chunked to fit Slack's message size limits (4000 chars per block)
- [ ] Bot only responds when mentioned or in DMs (not every channel message)
## Out of Scope
- TBD

21
.story_kit/work/1_backlog/326_story_slack_slash_commands_for_pipeline_management.md
View File

@@ -1,21 +0,0 @@
---
name: "Slack slash commands for pipeline management"
---
# Story 326: Slack slash commands for pipeline management
## User Story
As a Slack user, I want to use slash commands like /storkit-status and /storkit-cost as an alternative to mentioning the bot, so that I can quickly access pipeline info with minimal typing.
## Acceptance Criteria
- [ ] Slash command endpoint at /webhook/slack/command handles Slack slash command payloads
- [ ] Supports /storkit-status, /storkit-cost, /storkit-show, /storkit-git, /storkit-htop
- [ ] Slash command responses are ephemeral by default (only visible to the caller)
- [ ] Slash commands documented in setup guide with Slack app configuration steps
- [ ] Registered in the command registry so they share handlers with the mention-based commands
## Out of Scope
- TBD

23
.story_kit/work/5_done/327_story_bot_overview_command_shows_implementation_summary_for_a_story.md Normal file
View File

@@ -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