What problem does it solve? Code reviews often conflate style conformance with requirement fidelity, letting one concern mask the other and allowing unrequested scope or missing behavior to slip through before Feature or Risky Bounded completion. ## Core Features & Use Cases - Two-Axis Review: Evaluates Standards (repository rules, code-smell heuristics) and Spec (task card, stories/AC, architecture contract) as strictly separate passes that are never merged or reranked. - Required Review Input Contract: Blocks the review unless baseline revision, owned changed areas, task card, stories/AC, architecture contract, standards sources, and required checks are all provided. - Parallel or Sequential Execution: Dispatches Standards and Spec subagents in parallel when available, or runs two isolated sequential passes as a fallback. - Use Case: Before marking a feature complete, run this review to receive separate standards and spec verdicts with findings citing severity, source, location, risk, and concrete correction. ## Quick Start Review my current change against the repository standards and the approved task specification, reporting standards and spec findings as two separate verdicts.
