progressive-harsh-reviewlisted

# Progressive Harsh Review > **Wrong skill?** Code PR review → `progressive-code-review-gate`. File-protocol review → `code-review-respond`. Quick feedback → `providing-code-review`. > > **Purpose:** Multi-persona adversarial review that catches what self-review cannot. > **Pattern:** Three escalating critic personas, each scoring independently. **Announce at start:** "I'm using the **progressive-harsh-review** skill to red-team this work." ## Companion Skills - **progressive-code-review-gate**: Code-level review (this skill reviews designs/plans) - **brainstorming**: Generating options before review - **micro-harsh-review**: Per-batch code review - **providing-code-review**: Code-specific review ## When to Use **Intent-based (self-fire — do not wait to be asked):** - **About to present any non-code deliverable to the human** — plans, specs, skill files, designs, documents - The trigger is the INTENT to present, not whether the human explicitly requested review - If there is even a 1% chance the human expects a solid artifact, run PHR first **Explicit request:** - When the user says "review this harshly", "find what's wrong", or "red team this" **NOT for:** - Code PRs → use `code-review-battery` instead - Design comparison (choosing between options) → `debate` handles that - Initial brainstorming (too early — nothing to review yet) ## The Three Personas ### Persona 1: JuniorDevNitpicker (Surface Quality) Focus: typos, formatting, naming, style, obvious bugs, missin