The to-spec Skill: What It Writes and When to Skip It
How Matt Pocock's /to-spec skill turns a planning conversation into a spec issue, what its template leaves out, and when a spec is not worth the step.
A focused archive of Spec Writing articles for spec-first teams.
How Matt Pocock's /to-spec skill turns a planning conversation into a spec issue, what its template leaves out, and when a spec is not worth the step.
A copy-ready packet for giving AI coding tools a bounded task, acceptance criteria, file ownership, tests, and review evidence before code generation starts.
Review AI-generated pull requests against acceptance criteria: inspect the diff, run evidence checks, and catch failures a quick skim misses.
Use test-evidence gates for AI-generated code: require meaningful tests before merge and catch hallucinated implementations before release.
Avoid ten specification mistakes that hide decisions, blur acceptance criteria, skip failure paths, and push scope arguments into implementation.
Use this pre-coding review checklist to separate blockers from preferences, record accepted risks, and attach test evidence before implementation begins.