feature-status-sync

To keep project documentation and code status in sync, this Skill verifies code and test file existence against a central CONTEXT.json single source of truth, automatically updating feature progress and regenerating index.md files to reflect the validated status changes.

The best way to automate feature status updates is to verify file existence against CONTEXT.json, log status transitions for auditability, and automatically generate top-level feature-registry.json and index.md files to ensure a comprehensive project overview.

Yes, you need a CONTEXT.json file to synchronize feature progress because it acts as the single source of truth that the Skill checks against to verify code and test file existence before updating documentation and logging status history.

Generating index.md files from a central registry improves project management by recreating individual feature documentation and a top-level overview, ensuring developers have a consistent, updated view of feature progress and code alignment without manual tracking.

Yes, you can track feature status history and audit transitions because the documentation sync process logs status transitions and history against the CONTEXT.json single source of truth, providing a clear audit trail of development progress.