Files
fidelity-ai-workspace/.opencode/commands/standup.md
david.delagneau 374991a568 Refactor workspace structure and documentation
- Deleted obsolete files: obsidian-vault.md, onboarding.md, workspace-model.md
- Updated opencode.json to remove references to deleted files.
- Revised profile.md to clarify the status of legacy paths and communication evidence.
- Adjusted prompts to reflect new file paths and improve clarity.
- Enhanced daily logs with focus, work-items, and blockers properties.
- Updated work-item notes to include systems, workstreams, people, and related properties.
- Improved context maintenance guidelines to ensure accurate and durable project knowledge.
- Refined base filters to exclude template files and ensure only relevant notes are displayed.
- Updated daily templates to ensure proper formatting and consistency.
- Modified workflows to align with the new vault structure and improve context synchronization.
2026-04-16 16:28:30 -06:00

3.3 KiB

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 @vault/00-start/start-here.md @vault/01-current/current-work.md @vault/01-current/work-items.md @vault/03-context/project.md @vault/03-context/workstreams/index.md @vault/03-context/workstreams/flow-page-references.md @vault/03-context/process/communication.md @vault/03-context/process/jira-story-rules.md @vault/04-people/manager.md

Previous workday Mattermost context, if present:

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

Today's log, if present:

!if [ -f vault/06-daily/$(date +%F).md ]; then cat vault/06-daily/$(date +%F).md; else echo "No daily note 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 vault/02-work-items ]; then for f in vault/02-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:

  • use status-reporting when available
  • 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 vault/03-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