Reviewer 2 Hat

Identify fatal flaws in early-stage ideas via hostile review.

393|34|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/Pthahnix/De-Anthropocentric-Research-Engine --skill reviewer-2-hat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Reviewer 2 Hat
Source: https://github.com/Pthahnix/De-Anthropocentric-Research-Engine/tree/main/skills/sop/reviewer2-hat
Command: npx skills add https://github.com/Pthahnix/De-Anthropocentric-Research-Engine --skill reviewer-2-hat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Apply a hostile reviewer perspective to identify fatal flaws in ideas, helping teams harden proposals and avoid costly missteps.

Core Features & Use Cases

  • Structured critique: returns a clear set of critiques, a fatal flaw, and improved variants.
  • Deterministic workflow: uses a standardized process that can be repeated across ideas.
  • Use case: during early-stage ideation, product proposals, or strategy plans to stress-test assumptions and risks.

Quick Start

Provide an idea and context to the Reviewer 2 Hat SOP to obtain a structured critique and suggested improvements.

Frequently Asked Questions about Reviewer 2 Hat

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

FAQPage Schema
How do I identify fatal flaws in early-stage product ideas?

To identify fatal flaws in early-stage product ideas, apply a hostile reviewer perspective that stress-tests assumptions and risks. This approach returns a structured set of critiques, highlights the primary fatal flaw, and suggests improved variants to harden your proposal.

What is a hostile reviewer critique and when do I need it for risk analysis?

A hostile reviewer critique is a structured evaluation that targets hidden assumptions and risks in early-stage concepts. You need it during product design, proposal creation, or strategy planning to expose fatal flaws and avoid costly missteps before committing resources.

How do I stress-test assumptions in a strategy plan or proposal?

You can stress-test assumptions in a strategy plan by providing your idea and context to a standardized hostile reviewer process. This deterministic workflow enforces structured evaluation requirements to consistently uncover critiques and generate improved variants across multiple ideas.

Can I use this hostile reviewer perspective for early-stage ideation across different proposals?

Yes, you can use this hostile reviewer perspective for early-stage ideation across different product proposals and strategy plans. It applies a deterministic, repeatable workflow that outputs a consistent set of critiques, a fatal flaw identification, and improved variants for any submitted concept.

What are the limitations of using a hostile reviewer lens for idea evaluation?

The limitation of using a hostile reviewer lens for idea evaluation is that it focuses strictly on critique and risk rather than constructive validation. It targets early-stage concepts to expose fatal flaws, meaning it may not suit ideas needing positive reinforcement or advanced late-stage development.

Does the Reviewer 2 Hat critique process require any specific dependencies or components?

The Reviewer 2 Hat critique process requires no external dependencies or components, but it relies on the dare-agents tool when invoked. You simply provide your idea and context to the standardized SOP to obtain a structured critique and suggested improvements.