Menu
Author (or amend) an Architecture Decision Record for a load-bearing architectural decision, in place, with a change log.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Compile the contract set in your head — simulate how the real application would run from the specs, and disprove (or confirm) it works before any source .py is written.
Author test stub files (.pyi) whose signatures express the domain, relationships, and compositions, as the first contract surface.
Funnel level 3 — identify building-block names and rough boundaries only, and run gap analysis.
Funnel level 1 — establish the big picture with seven broad questions, applying CIT, Laddering, and CI Perspective throughout.
Squash-merge the feature commits into dev, regenerate docstrings, and verify the whole suite plus whole-suite stubtest are clean.
Publish the delivered batch as release notes, a PR to main, or a tagged release.
| name | record-decision |
| description | Author (or amend) an Architecture Decision Record for a load-bearing architectural decision, in place, with a change log. |
.templates/docs/decisions/YYYY-MM-DD-<kebab-title>.md.template to docs/decisions/<today>-<slug>.md, replacing the date placeholder with today's ISO date and the slug with a short kebab title for the decision.Context (the forces — link the interview, glossary, existing ADRs, cassettes, and the contract set; do not restate them), Decision (one imperative sentence), Alternatives considered (each alternative + why it was rejected), Consequences (+ / − / neutral, with mitigations for the negatives). Apply the prose bar per [[writing/ai-language-markers]] — scrub AI markers (delve, tapestry, plays a crucial role, rather than); the ADR's authority comes from the decision's forces, not formal-sounding prose.Traceability, link the artefacts the decision touches — tests, source .pyi, migrations, cassettes, glossary terms, related ADRs — by path. Points only; never restate the artefact's content (tests are the source of truth).Change log with one row: <today> | Created | <one-line reason>.Status, Decision, Alternatives considered, and Consequences to the current decision — and append a Change log row (<today> | Amended | <what changed and why>). Do not create a new file; the body always reflects the current decision and the log carries the history.Traceability resolves to a real artefact before finishing.