diff --git a/.storkit/work/1_backlog/401_bug_whatsapp_and_slack_missing_start_command_handler.md b/.storkit/work/1_backlog/401_bug_whatsapp_and_slack_missing_start_command_handler.md
new file mode 100644
index 00000000..8984dd75
--- /dev/null
+++ b/.storkit/work/1_backlog/401_bug_whatsapp_and_slack_missing_start_command_handler.md
@@ -0,0 +1,26 @@
+---
+name: "WhatsApp and Slack missing start command handler"
+---
+
+# Bug 401: WhatsApp and Slack missing start command handler
+
+## Description
+
+The start command has a fallback handler in chat/commands/mod.rs that returns None. Only Matrix has pre-dispatch handling for this command. On WhatsApp and Slack, the command falls through to the LLM path.
+
+## How to Reproduce
+
+1. Configure bot with transport = "whatsapp" or "slack"\n2. Send "start <story_id>" to the bot\n3. Check server logs
+
+## Actual Result
+
+Command falls through to LLM instead of starting an agent.
+
+## Expected Result
+
+The bot starts an agent for the specified story and replies with confirmation.
+
+## Acceptance Criteria
+
+- [ ] WhatsApp transport handles start command: starts agent and replies with confirmation
+- [ ] Slack transport handles start command: starts agent and replies with confirmation