How to Write Specs Coding Agents Can Build Without Guessing

You hand a coding agent a spec and it builds something you never asked for. Most of the time the spec was the problem, not the model.

This share is about a plugin for Claude Code and Codex that drafts the spec with you, then sends it to fresh read-only subagents before a single line of code exists. The rule it enforces is blunt: a spec is not ready until an agent that never saw the discussion can explain it back. It is Apache-2.0 and sits at 10.3k stars.

What You Need

• Claude Code or Codex, since the plugin runs inside one of them.

Tutorial

1. Draft the spec with the plugin inside Claude Code or Codex. It works the spec out alongside you instead of leaving you to write it alone.

1. Hand the finished draft to fresh read-only subagents before any code exists. They carry no memory of the discussion that shaped the spec, so they read it cold, the way a stranger would.

1. Make one reviewer paraphrase the spec before it does anything else. A wrong paraphrase counts as a finding, so the review opens with one question: can this be explained back at all?

Wrapping Up

You now have a spec that survived a reader who never sat in on the conversation that produced it, which is the closest thing to a guarantee the build will not guess. Keep the paraphrase check first, because it is the cheapest failure you will ever catch. If the spec comes back mangled, fix the spec, not the reviewer.