Part

Spec

You might say: specification, PRD, intent

A written description of the shared design concept: what a piece of work must do and how anyone will know it is done. It carries the intent across sessions, so the author run, the verifier and the person all work toward the same target.

What it does
Gives verification a target that exists before the code does.
Ask
Does the spec say what must be true when the work is done, in terms a scenario can check?

What to look for

  1. A spec or PRD file linked from the ticket
  2. Acceptance criteria written as statements a test can check
  3. Out-of-scope notes and open questions

Catalogue: Spec technique

Sources

  1. Matt Pocock, AI Coding Dictionary, SpecA handoff artifact describing a multi-session piece of work
  2. Justin McCarthy (StrongDM), Software Factories And The Agentic Moment, Software Factories And The Agentic Momentnon-interactive development where specs + scenarios drive agents that write code, run harnesses, and converge without human review.
  3. Delinea, The Delinea Software Factory: Building Software with AI, The Delinea Software FactoryHumans define intent: what the system should do, the scenarios it needs to handle, the constraints that matter.
  4. Dan Shapiro, The Five Levels: from Spicy Autocomplete to the Dark Factory, Level 4You write a spec. You argue with it about the spec. … Then you leave for 12 hours, and check to see if the tests pass.
  5. Matt Pocock, AI Coding Dictionary, Design conceptThe shared understanding of what's being built, held in common between user and agent but separate from any asset.

Use it on your project

teardown-apply: hold "Spec" (spec) from the teardown at https://teardownatlas.com/software-factory/ against my project

Paste it into a coding agent that has the teardown skills.

An AI agent wrote this map with the teardown skill. It can contain errors: check the sources before you rely on a part. About and legal