From 224d2699712ee1d5c3c6beab40e907afb15198cd Mon Sep 17 00:00:00 2001 From: dave Date: Tue, 24 Mar 2026 22:01:58 +0000 Subject: [PATCH] storkit: create 385_story_slack_markdown_to_mrkdwn_formatting_conversion --- ...arkdown_to_mrkdwn_formatting_conversion.md | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 .storkit/work/1_backlog/385_story_slack_markdown_to_mrkdwn_formatting_conversion.md diff --git a/.storkit/work/1_backlog/385_story_slack_markdown_to_mrkdwn_formatting_conversion.md b/.storkit/work/1_backlog/385_story_slack_markdown_to_mrkdwn_formatting_conversion.md new file mode 100644 index 0000000..298b17e --- /dev/null +++ b/.storkit/work/1_backlog/385_story_slack_markdown_to_mrkdwn_formatting_conversion.md @@ -0,0 +1,23 @@ +--- +name: "Slack markdown-to-mrkdwn formatting conversion" +--- + +# Story 385: Slack markdown-to-mrkdwn formatting conversion + +## User Story + +As a Slack user, I want bot messages to use Slack-native mrkdwn formatting instead of raw markdown, so that headers, bold text, and links render properly. + +## Acceptance Criteria + +- [ ] Headers (# ## ### etc.) are converted to bold text (*Header*) in Slack messages +- [ ] Markdown bold (**text**) is converted to Slack bold (*text*) +- [ ] Markdown strikethrough (~~text~~) is converted to Slack strikethrough (~text~) +- [ ] Markdown links [text](url) are converted to Slack format: +- [ ] Code blocks and inline code are preserved as-is (already compatible) +- [ ] WhatsApp and Matrix bot formatting are completely unaffected (conversion only applied in Slack send paths) +- [ ] Conversion is applied to all Slack send paths: command responses, LLM streaming, htop snapshots, delete responses, and slash command responses + +## Out of Scope + +- TBD