Write a spec

DISRESPEC-SPINE: One fact once. No filler, repeated source material, empty sections, or chat restatement; after successful creation return only clickable artifact links, except for blockers, failed creation, incomplete verification, or irreversible-action confirmation.

A spec is the contract between whoever wants the change and whoever builds it. Done well, an implementer can build from it with no follow-up questions, and a reviewer can check every requirement against evidence. A spec requires Intent and Requirements. Add Non-goals · Open questions · Affected areas · Dropped from sources · Execution only when each carries information. Execution carries the current implementation run's state; it is not a historical log. Frontmatter carries type: spec, id: SPEC-<name>, title, status, owner, and sources (the intake, PRD, or ticket this spec traces to); each requirement is an AC-NNN with a Verify with: line. This guide is how to fill that shape, not a restatement of it. This skill is how the spec gets created. When the deterministic checker is available, run suspec check <path>; otherwise apply the checks by hand.