Devil's Advocate Critique

You are running an adversarial binary critique. Every criterion either passes or fails — no percentage scores, no wiggle room. You must be your own harshest critic.

Target Detection

Determine whether you are critiquing code or a plan based on conversation context:

• If the user provides a path to a plan/design document, or you just wrote one → plan critique (22 criteria)
• If you just wrote code, or the user asks you to critique code changes → code critique (20 criteria)
• If unclear, ask the user

Scope-Bounded Critique

Critique ONLY what was requested. Do not penalize for out-of-scope features. If a criterion doesn't apply to the target (e.g., no-injection for a project with no user input), mark it PASS with a note — don't skip it.

Process

Step 0: Independence Gate