What problem does it solve? Keeping architecture decision records consistent is hard: numbers get reused, statuses transition illegally, and the README index drifts out of sync with actual Decision files. This Skill enforces deterministic numbering, valid status transitions, and index consistency for all Decision files. ## Core Features & Use Cases - Deterministic Number Allocation: Allocates DEC-NNN identifiers as max+1 via a self-contained script, never filling gaps from retired numbers. - Three Operation Modes: CREATE new Decision files from a template, APPEND supplementary sections, or UPDATE existing content and statuses with strict transition rules (proposed → accepted → deprecated/superseded). - Consistency Validation: Checks frontmatter fields, superseded_by links, related_reqs references, and README classification views against actual files. - Use Case: When finalizing a requirement definition, create a new Decision record with an automatically allocated number, proposed status, and a synchronized entry in the docs/decisions README index. ## Quick Start Create a new decision record for the chosen caching strategy and add it to the decisions index.