What problem does it solve? Specs often reach implementation without adversarial scrutiny, so flawed premises, scope errors, and ambiguities surface only after code exists. This Skill acts as a dedicated devil's advocate that challenges a spec with steel-manned, evidence-backed objections before any implementation artefacts are produced. ## Core Features & Use Cases - Six objection categories: Classifies every challenge as premise, scope, implementation, risk, alternatives, or specification quality, each requiring quoted evidence from the spec. - Severity and disposition workflow: Assigns critical/high/medium/low severity and emits a YAML objection record with pending dispositions that a human adjudicates as accepted, deferred, or rejected. - Dual dispatch modes: Weights categories differently at spec time (premise, alternatives, scope) versus code time (risk, implementation), with a routing rule that partitions findings against a decision-archaeology agent. - Use Case: Before approving a design spec for a new CLI feature, run this Skill to produce an objection record at docs/superpowers/objections/<spec-slug>.md containing up to 12 evidence-cited objections plus an "Explicitly not objecting to" section exposing what was deliberately left unchallenged. ## Quick Start Ask the agent to adversarially review the spec at docs/superpowers/specs/2026-04-19-my-feature.md and write the objection record with categorized, evidence-backed objections.
