From 87fb98821b6d3b55f6ed8f66445bd6c68695292e Mon Sep 17 00:00:00 2001
From: Sahil Tandon <sahil.tandon@live.com>
Date: Sat, 20 Jun 2026 10:10:14 -0400
Subject: [PATCH] fix(commands): use standard markdown for bold in command
 output

Capturing a /slack:channel-digest into a markdown file, the digest's
bold headers (the Channel Digest title and the #channel names) rendered
as italic. The commands emit single-asterisk bold (*text*), which is
Slack's older mrkdwn convention, but standard markdown reads a single
asterisk as italic and needs double asterisks for bold. This affects
every standard-markdown surface the output lands in: markdown files and
the Slack MCP server, which expects standard markdown (so
draft-announcement writes a malformed-bold draft into Slack).

While fixing channel-digest, found the same single-asterisk bold pattern
in draft-announcement and standup, so all three commands are corrected to
standard markdown.
---
 commands/channel-digest.md     | 6 +++---
 commands/draft-announcement.md | 2 +-
 commands/standup.md            | 8 ++++----
 3 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/commands/channel-digest.md b/commands/channel-digest.md
index 9280cfe..f30861d 100644
--- a/commands/channel-digest.md
+++ b/commands/channel-digest.md
@@ -14,13 +14,13 @@ Given the comma-separated channel names provided in $ARGUMENTS (strip leading `#
 3. Present the digest in this format:
 
    ```
-   *Channel Digest — <today's date>*
+   **Channel Digest — <today's date>**
 
-   *#channel-1*
+   **#channel-1**
    - Summary point 1
    - Summary point 2
 
-   *#channel-2*
+   **#channel-2**
    - Summary point 1
    - Summary point 2
 
diff --git a/commands/draft-announcement.md b/commands/draft-announcement.md
index d3eea64..5a24e9b 100644
--- a/commands/draft-announcement.md
+++ b/commands/draft-announcement.md
@@ -12,7 +12,7 @@ Given the topic or context provided in $ARGUMENTS:
    - What tone is appropriate — formal, casual, or urgent?
 
 2. Compose the announcement following Slack formatting best practices:
-   - Use Slack's mrkdwn syntax: `*bold*` for emphasis (not `**bold**`), `_italic_` for secondary emphasis, `>` for callouts.
+   - Use standard markdown: `**bold**` for emphasis, `_italic_` for secondary emphasis, `>` for callouts.
    - Lead with the most important information — don't bury the point.
    - Use a clear, descriptive opening line that works as a headline.
    - Keep paragraphs short (2-3 sentences max).
diff --git a/commands/standup.md b/commands/standup.md
index 143e118..5ce8060 100644
--- a/commands/standup.md
+++ b/commands/standup.md
@@ -15,16 +15,16 @@ description: Generate a standup update based on your recent Slack activity
 
 5. Format the standup as:
    ```
-   *Standup for <display name> — <today's date>*
+   **Standup for <display name> — <today's date>**
 
-   *Done:*
+   **Done:**
    - Item 1
    - Item 2
 
-   *Doing:*
+   **Doing:**
    - Item 1
 
-   *Blockers:*
+   **Blockers:**
    - None / Item 1
    ```