fidelity-ai-workspace/.opencode/commands/standup.md

description

description
Draft a standup from the latest Fidelity workspace context

Generate a standup update using the latest workspace state.

First, refresh Mattermost context before drafting:

!if [ -n "$FIDELITY_MATTERMOST_SYNC_CMD" ]; then bash -lc "$FIDELITY_MATTERMOST_SYNC_CMD" >/dev/null 2>&1 || true; elif [ -f scripts/mattermost/sync.sh ]; then bash scripts/mattermost/sync.sh >/dev/null 2>&1 || true; fi

Read:

@prompts/standup.md @ai/AGENTS.md @ai/context/index.md @ai/context/project.md @ai/context/workstreams/index.md @ai/context/workstreams/flow-page-references.md @ai/context/process/communication.md @ai/context/process/jira-story-rules.md @ai/context/people/manager.md @ai/work-items/index.md @ai/state/current.md @ai/state/work-items.md @knowledge/communication-rules.md @knowledge/agent-memory-rules.md

Previous workday Mattermost context, if present:

!bash scripts/mattermost/sync.sh --previous-workday --today "$(date +%F)"

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, preferring inbox and falling back to generated JSONL:

!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

Detailed active work item files, if available:

!if [ -d ai/work-items ]; then for f in ai/work-items/*.md; do case "$f" in *README.md|*index.md) continue;; esac; echo "\n### $f"; cat "$f"; done; else echo "No work item files available."; fi

Before drafting:

• update workspace memory if the refreshed context introduced clear high-confidence project facts
• prefer existing memory when the latest context is ambiguous
• treat the previous workday Mattermost context as the source for the Yesterday section, even when the previous calendar day was a weekend, holiday, or OOO day
• mention Jira IDs and approved titles when they map cleanly to previous-work context
• prioritize story-based updates over side questions, memory refreshes, or manager-only context
• if documentation or root cause updates directly support a story, roll them into that story's update instead of listing them separately
• exclude items that are not directly tied to a story unless they are true blockers
• when one Jira item has multiple concrete updates, group them under one top-level JIRA-ID - Title bullet with indented markdown sub-bullets instead of repeating the same Jira line
• use ai/context/workstreams/flow-page-references.md to preserve real flow/page identifiers when shorthand appears in logs or messages

Return a standup that is:

• specific
• concise
• grounded in the latest context
• safe to send without overstating certainty
• written in natural US English that can be sent externally without rewriting
• written as David's progress report
• free of any mention of Jeff by name
• free of any mention of Mattermost, since it is internal-only communication
• uses bullet points for each item
• groups multiple updates for the same Jira item as indented sub-bullets
• uses JIRA-ID - Title or JIRA-ID Title formatting instead of comma-separated ID/title formatting