What problem does it solve? Lifecycle specs (requirements, tech-spec, architecture) often accumulate speculative features, premature abstractions, and unused configuration options. This Skill systematically challenges the necessity of every FR, NFR, component, and config in a spec so over-designed elements are flagged for removal before implementation. ## Core Features & Use Cases - 6-Dimension YAGNI Rubric: Scores each spec element against Necessity Now, Abstraction Justification, Extensibility Speculation, Configurability Excess, Premature Optimization, and Scope Drift. - Adversarial Codex Debate: Runs an independent second-opinion classification via the codex-brainstorm skill, then merges verdicts using the stricter of Claude and Codex classifications. - Deterministic Gate: Emits a binary ✅ Audit Clear / ⛔ Audit Revise sentinel backed by 6 deterministic checks, with --override support for justified keeps and --continue for re-auditing revised specs. - Use Case: Before implementing a tech spec, run the audit on docs/features/foo/2-tech-spec.md to identify FRs with no current stakeholder, abstractions with zero consumers, and flags nobody toggles. ## Quick Start Ask the AI to run a necessity audit on your spec file, for example: run /necessity-audit on docs/features/foo/2-tech-spec.md and tell me which elements should be cut.
