Pending: Should it auto-fix or just report? (start with report-only)
Resolved: Should it run as a hook after vault edits, or only on demand? → Both. Skill for on-demand, PostToolUse hook for automatic sync after FR file changes.
User Tasks
FR-027: Feature Overview Sync Check
Summary
A skill (/check-features) that verifies FR files and the feature overview are in sync.
Problem / Motivation
The feature overview can drift out of sync with actual FR files — missing entries, wrong statuses, wrong counts. Currently this requires a manual check.
Proposed Solution
Build a /check-features skill and a PostToolUse hook that together keep the dashboard in sync:
Scans all FR files across new/planned/in-progress/done folders
Compares with the feature dashboard table
Reports mismatches: missing FRs, extra rows, wrong status/folder, wrong counts
Auto-fixes the dashboard (Phase 2)
Hook triggers automatically after FR file creates/moves/edits (Phase 2)
Open Questions
Should it auto-fix or just report? (start with report-only)
Should it run as a hook after vault edits, or only on demand?
Phase Overview
Phase
Description
Status
Phase 1
Report-only skill
—
Phase 2
Auto-fix + optional hook
—
Phase 1: Report Only —
Goal: Build a skill that detects mismatches between FR files and the feature overview.
File / Feature
Details
Owner
Status
Create skill
.claude/skills/check-features/SKILL.md
opus
—
Scan FR files
Glob all FR-*.md across lifecycle folders
opus
—
Parse overview
Read feature-dashboard.md table
opus
—
Compare & report
Show mismatches in terminal
opus
—
Phase 2: Auto-fix & Hook —
Goal: Automatically fix the dashboard and keep it in sync via a hook.
File / Feature
Details
Owner
Status
Auto-fix mode
/check-features --fix regenerates the dashboard table
opus
—
Sync script
Python/bash script that scans FR files → updates dashboard
opus
—
PostToolUse hook
Triggers sync script after Write/Edit on vault/10_features/**
opus
—
Hook registration
Add to .claude/settings.json PostToolUse array
opus
—
Acceptance Criteria:
/check-features reports all mismatches between FR files and dashboard
Detects missing FRs, extra rows, status/folder mismatches, wrong counts
No false positives on a clean vault
Hook auto-syncs dashboard after FR file changes (no manual step needed)
Hook is lightweight — only triggers when path matches 10_features/
Notes:
Ideas are intentionally excluded from the feature overview — only FRs are tracked.
Prerequisites / Gap Analysis
Requirements
Requirement
Description
REQ-1
Feature overview dashboard must exist
REQ-2
FR files must follow consistent naming and frontmatter
Current State
Component
Status
Details
Feature overview
done
vault/00_system/dashboards/feature-dashboard.md
FR file naming
done
Consistent FR-XXX pattern
Sync check skill
—
Does not exist
Gap (What’s missing?)
Gap
Effort
Blocker?
/check-features skill
Med
No
Test
Manual tests
Test
Expected
Actual
Last
Clean vault scan
No mismatches reported
pending
-
Missing FR in overview
Detected and reported
pending
-
Wrong status in overview
Detected and reported
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-02-27
Created
2026-02-27
Renumbered
From FR-066 to FR-027
2026-02-28
Reformatted
Aligned to feature-request template
2026-03-12
Updated
Expanded scope: added PostToolUse hook for auto-sync, resolved hook decision, bumped priority to high
References
FR-028 (Feature Workflow Automation) — related overview automation