1.8 KiB
description
| 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.
Read:
@prompts/manager-update.md @ai/AGENTS.md @ai/context/index.md @ai/context/project.md @ai/context/workstreams/index.md @ai/context/process/communication.md @ai/context/people/manager.md @ai/context/people/index.md @ai/state/current.md @ai/state/work-items.md @knowledge/communication-rules.md @knowledge/agent-memory-rules.md
Today's log, if present:
!if [ -f ai/logs/$(date +%F).md ]; then cat ai/logs/$(date +%F).md; else echo "No log exists for today yet."; fi
Latest Mattermost context, if available:
!if [ -s ai/inbox/mattermost-latest.md ]; then cat ai/inbox/mattermost-latest.md; elif [ -s scripts/mattermost/generated/mattermost_context.jsonl ]; then cat scripts/mattermost/generated/mattermost_context.jsonl; else echo "No Mattermost context available."; fi
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:
- Final message
- One-line note with any assumption you had to make