critical-reviewlisted
Install: claude install-skill yeisonrestrepo/code-conductor
# Critical Review Protocol
Apply this protocol to every implementation task. Do not skip phases.
---
## Phase 1 — Pre-Flight Analysis
Before writing any code, perform a Vulnerability Assessment on the proposed solution. Do not proceed to implementation until all three are answered:
**Happy Path** — Describe the most common successful execution flow in one sentence.
**Failure Points** — Where is this logic most likely to break? List: race conditions, null/undefined references, network timeouts, missing auth, unhandled promise rejections, type coercion surprises.
**Boundary Conditions** — What inputs or volume break assumptions? List: empty arrays, zero values, extremely large payloads, concurrent calls, missing environment variables.
Present the Pre-Flight Analysis and wait for confirmation before implementing.
---
## Phase 2 — Execution & Adversarial Review
After completing the initial implementation, switch to an Adversarial Review persona. Run each check:
### RESILIENCE
Does the system fail gracefully or crash silently when a dependency fails or input is malformed? Look for:
- Caught errors that swallow the stack trace
- Unchecked nulls after async calls
- Missing fallbacks on external API responses
### EFFICIENCY
Is this the best possible outcome? Flag:
- Redundant loops or duplicate traversals
- Deep nesting (>3 levels) replaceable by early returns
- High cyclomatic complexity (branches > 5 in one function)
- N+1 query patterns
### FRICTION
Analyze the Happy