Pending: Trigger mechanism — on-demand skill, PostToolUse hook, or both?
Pending: Per-dashboard regeneration or single unified script?
User Tasks
Summary
Keep all dashboards in vault/00_system/dashboards/ accurate and up-to-date automatically, preventing drift as features are implemented and vault state changes.
Problem / Motivation
Six dashboards exist (feature, decision, capabilities, ideas, tasks, review) but nothing ensures they reflect current reality.
As FRs move through lifecycle stages, dashboards go stale within a single session.
Multiple FRs (briefings, kanban, priority scoring) consume dashboard data — stale dashboards cascade into stale briefings.
Manual updates are tedious and will be forgotten.
Proposed Solution
A /sync-dashboards skill that scans vault state and regenerates each dashboard from source data (FR files, decision log, etc.). Optionally triggered automatically via PostToolUse hook when FR files are modified.
Open Questions
1. Trigger Mechanism
Question: How should dashboard sync be triggered?
Option
Description
A) Skill + hook
/sync-dashboards on demand + PostToolUse hook on FR file changes
B) Skill only
Manual trigger, simpler to implement
C) Hook only
Fully automatic but no manual control
Recommendation: Option A — manual for initial rollout, add hook in Phase 2.
Decision:
2. Scope per Dashboard
Question: Should each dashboard have its own generator or one unified script?
Option
Description
A) Per-dashboard generators
Each dashboard has its own logic, easier to maintain independently
B) Unified generator
Single script handles all, less code but more complex
Recommendation: Option A — dashboards have different data sources and formats.
Decision:
Phase Overview
Phase
Description
Status
Phase 1
/sync-dashboards skill — regenerate all dashboards on demand
—
Phase 2
PostToolUse hook to auto-trigger on FR/vault changes
—
Phase 3
Dashboard health check (detect stale data, warn in briefing)
—
Phase 1: Sync Skill —
Goal: A skill that regenerates all dashboards from current vault state.
File / Feature
Details
Owner
Status
.claude/skills/sync-dashboards/SKILL.md
Skill definition
opus
—
Dashboard: feature-dashboard.md
Regenerate from FR files
opus
—
Dashboard: decision-dashboard.md
Regenerate from decision log + FR decisions
opus
—
Dashboard: capabilities-dashboard.md
Regenerate from system state
opus
—
Dashboard: ideas-dashboard.md
Regenerate from ideas/ folder
opus
—
Dashboard: user-tasks-dashboard.md
Regenerate from tasks/todos
opus
—
Dashboard: user-review-dashboard.md
Regenerate from review items
opus
—
Phase 2: Auto-Trigger Hook —
Goal: Automatically regenerate affected dashboards when FR files are created, moved, or edited.
File / Feature
Details
Owner
Status
.claude/hooks/post-dashboard-sync.sh
PostToolUse hook script
opus
—
Hook registration in settings.json
Register the hook
opus
—
Phase 3: Dashboard Health Check —
Goal: Detect stale dashboards and surface warnings in daily briefing.
File / Feature
Details
Owner
Status
Staleness detection
Compare dashboard timestamps vs source data timestamps
opus
—
Briefing integration
Flag stale dashboards in daily briefing (FR-062)
opus
—
Prerequisites / Gap Analysis
Requirements
Requirement
Description
REQ-1
Dashboard files must exist (already do)
REQ-2
Consistent FR frontmatter for parsing
Current State
Component
Status
Details
Dashboards
done
6 dashboards exist in vault/00_system/dashboards/
FR frontmatter
done
All FRs use standard template
Sync mechanism
—
Nothing exists yet
Gap (What’s missing?)
Gap
Effort
Blocker?
Skill definition
Low
No
Dashboard generation logic
Medium
No
Hook integration
Low
No (Phase 2)
Test
Manual tests
Test
Expected
Actual
Last
Check staleness after manual FR edit without sync
Health check flags stale dashboard
pending
-
AI-verified tests
Scenario
Expected behavior
Verification method
…
…
…
E2E tests
Scenario
Assertion
…
…
Integration tests
Component
Coverage
…
…
Unit tests
Component
Tests
Coverage
…
…
…
History
Date
Event
Details
2026-03-12
Created
Identified as gap during FR renumbering review
References
vault/00_system/dashboards/ — the 6 existing dashboards
FR-019 (Kanban Feature Overview) — consumes dashboard data