shipkit-adr

# shipkit-adr - Land a Decision Atomically **Purpose**: Record one architecture decision the moment it's made — as a single atomic transaction across both decision files, with a hard length cap on what enters the always-loaded lean index. **Why this exists**: `architecture.json` is `@`-imported into CLAUDE.md, so every byte of it loads into every session. The moment a decision gets recorded is exactly when a long rationale is freshest and most tempting to paste in. This skill enforces the lean/archive split at that moment: full reasoning is preserved (archive), context stays cheap (lean). **Output**: One entry appended to `.shipkit/architecture-archive.json` (full) + the capped projection in `.shipkit/architecture.json` (lean). --- ## When to Invoke **User triggers**: - "Record this decision" / "log an ADR" - "We decided X" (after a decision is settled in conversation) - "ADR-NNN is superseded by this" / "that replaces the earlier decision" - "Amend ADR-NNN" **Agent triggers**: Any skill or agent that has just made an architecture-level decision mid-work lands it here instead of hand-editing `architecture.json`. --- ## Prerequisites None. If either decision file is missing, this skill initializes it (schemas below). The canonical convention both files follow is `shipkit-engineering-definition/references/architecture-log-schema.md` — read it for edge cases; the operative rules are inlined here. --- ## Hard Caps (non-negotiable) What enters the **lean** file is cap...