Sync a Spec

Realign one feature's spec triad (docs/specs/<date>-<feature>/{requirements,design,tasks}.md) with what is actually true — in the code, the tests, and the tasks. Specs that are not resynced after change become fiction, and fiction is worse than no spec.

Work one feature at a time. Identify the spec directory first (from the user, the current branch, or docs/specs/INDEX.md).

Iron rules

• Never renumber requirement IDs. IDs are immutable once approved; everything downstream cites them.
• Never delete a requirement. Retire it: ~~**CODE-N.M**~~ <reason> — struck-through IDs stop counting as defined, but the history stays legible.
• New requirements get the next free number under their story; new tasks match the existing task format exactly.
• Never write Status: Shipped. That transition is cut-release step i on the release cohort. This skill realigns one triad; it does not stamp a release.
• Never write Status: In-progress. That transition is execute-common session preflight.

Steps

a. Baseline. Run the audit-trace check (REQUIRED SUB-SKILL: use audit-trace) and capture the finding set — this is the "before" picture.

b. Requirements ↔ tasks. Compare requirements.md against tasks.md: