What problem does it solve? In a markdown-based project pipeline, requirements in PRDs, epics, and features can silently lose coverage or diverge from the stories that implement them, and nobody notices until late. This Skill audits both directions of the traceability chain and surfaces gaps and drift as an advisory report. ## Core Features & Use Cases - Requirement-to-story coverage mapping: Inventories every PRD key requirement, epic In-scope bullet, and feature acceptance criterion, then checks each has at least one covering story. - Story-to-requirement fidelity check: Compares each story's acceptance criteria against its linked source requirement and flags scope-adds, scope-drops, reinterpretations, and stale requirement sources. - Dated advisory report: Writes a single PLAN-DRIFT-<date>.md report under 41-Reports/audits/ without ever editing stories, requirements, or status fields. - Use Case: Before closing a PRD-backed epic, run a plan-drift pass over the whole repo to confirm every requirement is traced to a story and no story has drifted from its source. ## Quick Start Ask the assistant to run a plan-drift check over the whole repo to audit requirement coverage and story fidelity.