story-kit: done 327_story_bot_overview_command_shows_implementation_summary_for_a_story

.story_kit/work/1_backlog/325_story_slack_llm_passthrough_for_conversational_queries.md

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

.story_kit/work/1_backlog/326_story_slack_slash_commands_for_pipeline_management.md

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