progressive-harsh-review

Performs adversarial multi-persona review of non-code deliverables with weighted scoring and hard veto.

8|1|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/bordenet/superpowers-plus --skill progressive-harsh-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: progressive-harsh-review
Source: https://github.com/bordenet/superpowers-plus/tree/main/skills/engineering/progressive-harsh-review
Command: npx skills add https://github.com/bordenet/superpowers-plus --skill progressive-harsh-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many non‑code artifacts such as plans, specifications, and designs often lack rigorous review, allowing hidden flaws to reach stakeholders.

Core Features & Use Cases

  • Three critic personas (JuniorDevNitpicker, SeniorArchCritic, ProdOpsHardass) each evaluate correctness, simplicity, testability, edge cases, and security/performance.
  • Weighted aggregation with hard‑veto rules ensures critical defects are caught and cannot be ignored.
  • Correlation detection flags echo‑reasoning and shared blind spots for deeper analysis.
  • Use Cases: before presenting a design document, reviewing a product spec, or finalizing a strategic plan.

Quick Start

Ask the assistant to run the progressive‑harsh‑review skill on your draft plan before sharing it.

Frequently Asked Questions about progressive-harsh-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an adversarial multi-persona review on a product specification?

An adversarial multi-persona review evaluates non-code deliverables like product specifications by deploying three critic personas to score correctness, simplicity, testability, edge cases, and security, aggregating weighted means to enforce hard vetoes for critical defects.

What is a hard-veto rule in design review scoring?

A hard-veto rule in design review scoring automatically fails an artifact if critical defects are detected across weighted dimensions like security or correctness, ensuring stakeholders never see flawed plans.

Can I use a multi-persona critic model to review strategic plans before presentation?

Yes, you can apply a multi-persona critic model to review strategic plans before presentation, utilizing specialized personas to independently flag edge cases, echo-reasoning, and shared blind spots in the document.

How does correlation detection work during a harsh design review?

Correlation detection during a harsh design review flags echo-reasoning and shared blind spots by cross-referencing the individual evaluations of multiple critic personas, highlighting areas needing deeper analysis.

Does multi-persona scoring work for non-code written artifacts and design documents?

Multi-persona scoring works effectively for non-code written artifacts and design documents by applying standardized evaluations across correctness, simplicity, testability, edge cases, and security before stakeholder presentation.

When should I not use an adversarial weighted aggregation review?

You should avoid adversarial weighted aggregation review for simple, low-stakes artifacts that lack complexity, as the rigorous multi-persona process is designed to catch hidden flaws in detailed specifications, designs, and strategic plans.