← ClaudeAtlas

delivery-change-contractlisted

Use when implementing a ready spec and about to change something other than the change's own code — a test written before the code, a test that existed before the change, a gap the spec left, the spec's goal or scope, a decision record, or a check that guards the repository such as the architecture test, the linter's configuration or CI. Owns the short list of what is frozen while a spec is implemented and changes only with the person's consent, that everything else is free and read by the review from the diff, that a new decision record or a stricter guarding rule is free, that an environment others use, a shared service or a secret is touched only with the person's consent asked once before the work, with credentials found or created rather than asked for piece by piece, the base commits a change is measured from, and catching an edit to what is frozen by a diff from them rather than by forbidding it. What a spec holds and which of its sections are frozen are `delivery-spec`'s; whether an edit to a test cha
wntic/pyhouse · ★ 3 · Code & Development · score 76
Install: claude install-skill wntic/pyhouse
# Delivery — Change contract While a spec is implemented, a few artifacts are **frozen**: they change only by the person, or with their consent. Everything else is free, and the review reads it in the diff. No tool can stop an edit — a file changes through any command that can write — so freezing is not a ban: an edit to what is frozen is caught by a diff from a fixed commit, and reaches the person as a stop. ## When to use vs. neighbours - What a spec holds, and which of its sections are frozen once it is ready → `delivery-spec`. - Whether a test is strong enough, at which level, and a fix's failing test → `test-principles`. - Whether an edit to a test repaired its form or weakened its meaning → `/pyhouse-universal:change-review`, which classifies every such edit from the diff, and is told the tests' base so that a test written before the code counts as one that existed. - The messages of the change's commits → `git-commit-message`, in the `pyhouse-git` plugin, where installed. - How the branch lands and when its history is folded → `git-branching`, in the `pyhouse-git` plugin, where installed. ## What is frozen - What the checks that guard the repository already enforce — the architecture test, the linter's and type checker's configuration, CI, hooks. A rule added that only makes one stricter is free; an exemption added to one, or a rule changed or removed, loosens it. - The project's decision records as they stand. A new record is free, unless it supersede