to-spec

Invoke the to-spec skill after discussing the feature. It synthesizes the existing conversation and codebase context into a spec with problem statement, user stories, implementation decisions, and testing decisions, then publishes it to the project issue tracker.

No. The skill explicitly avoids interviewing and only synthesizes what has already been discussed. The single checkpoint is confirming the proposed testing seams with the user before writing the spec.

The issue tracker and triage label vocabulary must be configured first by running /setup-matt-pocock-skills. Without that setup, the skill cannot publish the spec or apply the ready-for-agent label.

Testing seams are the boundaries at which a feature will be tested. The skill prefers existing seams at the highest possible level, proposes new ones only when necessary, and aims for as few seams as possible across the codebase.

Specific file paths and code snippets are excluded because they become outdated quickly. The exception is a prototype snippet that encodes a decision more precisely than prose, such as a state machine, schema, or type shape.