From f5b1103bf643ac88d619677ca6007b37302824d4 Mon Sep 17 00:00:00 2001 From: Dave Date: Fri, 20 Mar 2026 01:26:09 +0000 Subject: [PATCH] story-kit: done 326_story_slack_slash_commands_for_pipeline_management --- ..._slash_commands_for_pipeline_management.md | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 .story_kit/work/5_done/326_story_slack_slash_commands_for_pipeline_management.md diff --git a/.story_kit/work/5_done/326_story_slack_slash_commands_for_pipeline_management.md b/.story_kit/work/5_done/326_story_slack_slash_commands_for_pipeline_management.md new file mode 100644 index 0000000..4aa1214 --- /dev/null +++ b/.story_kit/work/5_done/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