feat: Add support for Jira-linked work management and enhance standup generation context

This commit is contained in:
2026-04-09 15:18:51 -06:00
parent 22198a6c6f
commit d40d82bacd
12 changed files with 65 additions and 4 deletions

View File

@@ -22,6 +22,7 @@ Then:
- automatically promote explicit, project-relevant, high-confidence facts
- default destination is `ai/logs/$(date +%F).md`
- update `ai/state/current.md` only for facts that materially change the current work window
- update `ai/state/work-items.md` for explicit Jira IDs, approved titles, points, scope, and status notes
- do not write tooling noise, sync status, or generic chat chatter into project memory
- if a fact is ambiguous, skip it rather than asking the user what to do

View File

@@ -9,6 +9,7 @@ Read:
@ai/AGENTS.md
@ai/context/project.md
@ai/state/current.md
@ai/state/work-items.md
@knowledge/workspace-model.md
@knowledge/communication-rules.md
@knowledge/memory-promotion-rules.md
@@ -32,6 +33,7 @@ Instructions:
- Update the smallest correct set of files among:
- `ai/logs/$(date +%F).md`
- `ai/state/current.md`
- `ai/state/work-items.md`
- `ai/context/project.md`
- `ai/context/decisions/*.md`
- Prefer concrete project updates over broad summaries

View File

@@ -4,21 +4,31 @@ 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/project.md
@ai/state/current.md
@ai/state/work-items.md
@knowledge/communication-rules.md
@knowledge/agent-memory-rules.md
Yesterday's log, if present:
!`y=$(date -v-1d +%F 2>/dev/null || python3 - <<'PY'\nfrom datetime import datetime, timedelta\nprint((datetime.now().astimezone() - timedelta(days=1)).strftime('%Y-%m-%d'))\nPY\n); if [ -f "ai/logs/$y.md" ]; then echo "$y"; cat "ai/logs/$y.md"; else echo "No log exists for yesterday."; fi`
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`
If no log exists for today, also inspect the most recent previous log:
Latest Mattermost context, preferring inbox and falling back to generated JSONL:
!`latest=$(ls -1 ai/logs 2>/dev/null | sort | tail -n 1); if [ -n "$latest" ]; then echo "$latest"; cat "ai/logs/$latest"; else echo "No logs available."; fi`
!`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`
Return a standup that is:

View File

@@ -11,6 +11,7 @@ Read:
@ai/context/project.md
@ai/context/people/jeff.md
@ai/state/current.md
@ai/state/work-items.md
@knowledge/workspace-model.md
@knowledge/communication-rules.md
@knowledge/agent-memory-rules.md
@@ -29,6 +30,7 @@ Instructions:
- Decide whether the new information belongs in:
- today's log
- `ai/state/current.md`
- `ai/state/work-items.md`
- `ai/context/project.md`
- `ai/context/people/jeff.md`
- `ai/context/decisions/`