story-kit: accept 324_story_slack_bot_integration_for_bot_commands

.story_kit/work/6_archived/324_story_slack_bot_integration_for_bot_commands.md

@@ -0,0 +1,24 @@
+---
+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

.story_kit/work/6_archived/325_story_slack_llm_passthrough_for_conversational_queries.md

@@ -0,0 +1,21 @@
+---
+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/6_archived/326_story_slack_slash_commands_for_pipeline_management.md

@@ -0,0 +1,21 @@
+---
+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