What problem does it solve? Generated artefacts — ICEA requirement drafts, Tech Specs, and implementation code — can carry structural gaps, scope creep, or hidden assumptions that only surface after they are committed. This Skill evaluates each artefact at the moment it is produced, while both the spec and the output are still in context, catching intent misalignment before anything touches disk. ## Core Features & Use Cases - Three critique modes: ICEA mode checks conformance, completeness, testability, B-series sensitivity coverage, and scope; TECH mode checks ICEA↔design traceability, coverage-matrix completeness, and D-option fidelity; CODE mode checks traceability, simplicity, rules compliance, decision transparency, and hidden assumptions. - Bounded auto-revise loop: On a REVISE verdict, the parent skill regenerates the artefact and re-runs the critic up to 2 times before writing; unresolved cases surface to the developer with ACCEPT AS-IS, GUIDE, or HALT options. - Automatic and standalone invocation: Fires inside icea-feature (Steps 5 and 8) and icea-implement (Step 4a), or runs independently via /critic icea or /critic code. - Use Case: While generating a feature for ADO-1234, the critic flags that AC-4 has no planned file in the Tech Spec's AC→File table and that the code defaults pagination to 50/page without flagging the assumption — both fixed before any file is written. ## Quick Start Ask the assistant to run /critic icea ADO-1234 to critique the ICEA draft for that work item before approving it.
