validate-feature
Validate Feature
Green unit tests prove that the assertions someone wrote pass. They do not prove
the feature works. The gap between the two — an API that returns 201 where the
client reads 200, a checkbox that flips in memory but never reaches the store,
a form that clears on a failed submit — is where features ship broken. This
skill closes it: drive the running system, not the test suite.
Run this after inspect-change, before land-branch.
Cold-start control. IF docs/agents/verify.md exists, Launch and Doctor
from that file before any checklist item (it owns how a later agent boots this
app). Drive each item with its Feature section when one matches; Evidence must
include the persist/reload check that file names. IF it is missing, continue
from project.md Run locally (dev) as today, and name /configure-repo
once so the user can generate the recipe (Decision M) — do not invoke it.