Implement a feature

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.

Features fail when the builder improvises around the spec — building past it, smuggling in "while I'm here" cleanup, or declaring done on a green suite that never exercised the new behavior. This guide carries the feature discipline standalone: build exactly what the requirements name, reuse before you invent, and let nothing leave your hand unverified. When runs are parallel, isolate each in its own worktree or branch so their writes stay disjoint. These are conventions the review packet inspects — nothing enforces them at edit time.

A feature adds capability that did not exist. Repairing a defect, restructuring without a behavior change, deliberately changing existing behavior, moving between APIs, and tuning a bottleneck are different kinds with their own guides in this catalog.

Before editing, open references/task-template.md and instantiate it as run notes. Record its path separately from any input task packet and fill it as you go. These notes are private execution state, not a Suspec task packet.