← ClaudeAtlas

delivery-speclisted

Use when writing, splitting or checking the spec for one change before it is implemented — a feature or a fix, what it names as contracts, and the behaviour its tests are written from. Owns the spec's sections and which of them exist only where the project has them, the shorter form a fix takes, contracts limited to what other code depends on, the sign that one spec is several, behaviour stated as what each path leaves behind, an optional note in words on how to see a change that shows only in a running process, a step the person must take written as the command they run, the spec's claims about today's system checked before any code is written, and which sections are frozen once the spec is ready — the goal, the scope and the contracts, a fix's symptom — and which may be refined during the work, and the status it carries from draft to implemented, set by the change itself so the mainline reads implemented only once it has landed. Not why a design was chosen — that is the project's own decision record, which
wntic/pyhouse · ★ 3 · Code & Development · score 79
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