What problem does it solve? In an NCS firmware project, the PRD, engineering specs, and source code can silently drift out of sync — a hand-edit here, a declined doc-sync prompt there — and no single session notices. This Skill provides a full project status dashboard and a forensic drift audit that compares document Changelog versions against the sync pins declared in prj.conf and the git commit history of src/. ## Core Features & Use Cases - Status Dashboard: Shows which lifecycle artifacts exist (PRD, specs, code, verification, validation) with their versions, and recommends the next phase to enter. - Drift Audit (Check 0-2, Cases A-D): Detects undeclared src/ commits since the last pin bump, PRD-vs-specs version mismatches, and pins bumped ahead of their documents, then prescribes the exact remediation flow. - Lifecycle Reference: Documents the four-phase cycle (PRD → Specs → Implementation → V&V), document ownership, Changelog conventions, and quick-entry routing rules. - Use Case: Before a release, run the audit to confirm no code commits landed without a corresponding spec or PRD update, then follow the recommended Case A/B/C/D flow to resync. ## Quick Start Ask Claude to run the NCS workflow audit on this project and show the status dashboard with any drift findings.
