---
description: Draft or polish a Mattermost update for the current manager or stakeholder
---

Draft a concise Mattermost message for the current manager or stakeholder in natural, manager-ready US English.

Use `professional-communication` when available.

Read:

@prompts/manager-update.md
@workspaces/fidelity/project-knowledge/01-current/current-work.md
@workspaces/fidelity/project-knowledge/01-current/work-items.md
@workspaces/fidelity/project-knowledge/03-context/project.md
@workspaces/fidelity/project-knowledge/03-context/process/communication.md
@workspaces/fidelity/project-knowledge/04-people/manager.md
@workspaces/fidelity/project-knowledge/04-people/index.md

Today's log, if present:

!`if [ -f workspaces/fidelity/project-knowledge/06-daily/$(date +%F).md ]; then cat workspaces/fidelity/project-knowledge/06-daily/$(date +%F).md; else echo "No daily note exists for today yet."; fi`

Latest Mattermost context, if available:

!`python3 scripts/mattermost-proxy/read-context.py --mode latest`

Detailed active work item files, if available:

!`python3 - <<'PY'
import re
from pathlib import Path

summary = Path("workspaces/fidelity/project-knowledge/01-current/work-items.md")
if not summary.is_file():
    print("No work item files available.")
    raise SystemExit(0)

text = summary.read_text()
paths = re.findall(r"Detail: `(workspaces/fidelity/project-knowledge/02-work-items/[^`]+)`", text)
if not paths:
    print("No work item files available.")
    raise SystemExit(0)

for rel in paths:
    path = Path(rel)
    if not path.is_file():
        continue
    print(f"\n### {rel}")
    print(path.read_text())
PY`

User draft or rough notes:

$ARGUMENTS

Requirements:

- Use Context, Observation, Action
- Clarify scope
- Preserve technical meaning
- Rewrite fully when needed so the result sounds like a fluent senior engineer wrote it
- Separate the current issue from unrelated bugs, workarounds, and follow-up work unless the user clearly wants them combined
- Prefer evidence-backed wording over intuition when context includes concrete findings
- Make ownership explicit when relevant: XFlow vs consumer app vs service/configuration vs another framework
- Mention auth state when relevant
- Mention Jira IDs and approved titles when they materially improve clarity
- Do not label something a regression unless the context supports it
- Keep the result short enough for Mattermost

Return:

1. Final message
2. One-line note with any assumption you had to make