critiquelisted

## Intent Systematically analyze a target (plan, code, design, document) to identify failure modes, edge cases, ambiguities, and potential exploits. Produce actionable findings with severity ratings and mitigation recommendations. **Success criteria:** - All major failure modes identified - Edge cases documented with reproduction scenarios - Ambiguities flagged with clarification requests - Security/exploit risks rated appropriately - Each finding has actionable recommendation **Compatible schemas:** - `schemas/output_schema.yaml` ## Inputs | Parameter | Required | Type | Description | |-----------|----------|------|-------------| | `target` | Yes | string or object | Plan, code, design, or document to critique | | `focus_areas` | No | array | Specific areas to examine (security, performance, logic, etc.) | | `severity_threshold` | No | string | Minimum severity to report: low, medium, high, critical | | `context` | No | object | Additional context about the target | | `adversarial` | No | boolean | Enable adversarial/red-team thinking (default: true) | ## Procedure 1) **Understand the target**: Analyze what is being critiqued - Read and comprehend the target fully - Identify the purpose and intended behavior - Note stated assumptions and constraints - Understand success criteria 2) **Identify failure modes**: Find ways the target could fail - What happens under unexpected inputs? - What if dependencies are unavailable? - What if timing assumption