delivery-speclisted
Install: claude install-skill wntic/pyhouse
# Delivery — Spec
A spec says what one change delivers and what must be true once it is done: what the change adds,
what other code will rely on, and the behaviour its tests are written from. It is written before the
code, with the person who wants the change, and it is short enough to review in one sitting. It is not
a second copy of the code, and it does not carry the reasons for a design.
## When to use vs. neighbours
- Why a design was chosen, and what was rejected → the project's decision record; a spec points at
the section it implements and restates none of it.
- Whether a new service is hexagonal or flat → `architecture-choice`.
- How the tests written from a spec are written — layers, substitution, assert strength, a defect's
failing test → `test-principles`.
- The commit or merge message of the change → `git-commit-message`, in the `pyhouse-git` plugin, where
installed.
- What implementing a ready spec may change besides its own code, and how an edit to what is frozen is
caught → `delivery-change-contract`.
- What a change breaks, read from its diff once it exists → `/pyhouse-universal:change-review`, not a
spec.
## Template(s)
A spec is one Markdown file per change, in the directory the project keeps them in. Section headings
may be in the project's language, worded as the project's earlier specs word them; which sections
exist, and their order, are what the template fixes — never an earlier spec's.
A section the template marks as conditional is left