From c0bab1e6718b137ceb31bfa193b49c5dfebf2c58 Mon Sep 17 00:00:00 2001 From: dave Date: Sat, 28 Mar 2026 09:23:45 +0000 Subject: [PATCH] storkit: create 425_story_chat_notification_when_a_story_blocks_with_reason --- ...ication_when_a_story_blocks_with_reason.md | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 .storkit/work/1_backlog/425_story_chat_notification_when_a_story_blocks_with_reason.md diff --git a/.storkit/work/1_backlog/425_story_chat_notification_when_a_story_blocks_with_reason.md b/.storkit/work/1_backlog/425_story_chat_notification_when_a_story_blocks_with_reason.md new file mode 100644 index 00000000..e02dbdd3 --- /dev/null +++ b/.storkit/work/1_backlog/425_story_chat_notification_when_a_story_blocks_with_reason.md @@ -0,0 +1,20 @@ +--- +name: "Chat notification when a story blocks with reason" +--- + +# Story 425: Chat notification when a story blocks with reason + +## User Story + +As a ..., I want ..., so that ... + +## Acceptance Criteria + +- [ ] When a story transitions to blocked state, send a chat notification to all configured transports +- [ ] Notification includes the story ID, story name, and the reason for blocking (e.g. gate failure output, max retries exceeded, empty diff) +- [ ] Notification uses a red or warning icon to distinguish from normal status messages +- [ ] Works across Matrix, WhatsApp, and Slack transports + +## Out of Scope + +- TBD