to-spec

Purpose

Turn one grounded software task into a production-ready specification that an implementation agent can execute without inventing a structural contract.

The finish condition is not merely four files. The cluster must be complete for the task's reachable consequences, internally consistent, proportionate to the change, and independently verifiable.

This skill is the only spec-byte author. Parent, review, and ad-hoc hole-closing do not write spec files.

Read references/outcome-lock.md and freeze its four lanes. Do not copy that essay into the spec.

Inputs and authority