review-plan

Review plans and architecture decisions for failure points and blind spots.

61|9|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/jonathanmalkin/jules --skill review-plan-jonathanmalkin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-plan
Source: https://github.com/jonathanmalkin/jules/tree/main/.claude/skills/review-plan
Command: npx skills add https://github.com/jonathanmalkin/jules --skill review-plan-jonathanmalkin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill combats confirmation bias by systematically stress-testing plans, architecture decisions, and analysis documents, identifying potential failure points and blind spots before execution.

Core Features & Use Cases

  • Adversarial Review: Simulates failure scenarios (post-mortems, over-engineering critiques) to uncover risks.
  • Assumption Identification: Explicitly lists unstated assumptions and their failure implications.
  • Use Case: Before launching a new feature, use this Skill to "devil's advocate" the implementation plan, ensuring all potential pitfalls are considered and addressed, leading to a more robust launch.

Quick Start

Use the review-plan skill to stress-test the plan outlined in 'new-feature-plan.md'.

Frequently Asked Questions about review-plan

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

FAQPage Schema
How do I stress-test an architecture plan before implementation?▼

To stress-test an architecture plan, perform a multi-phase adversarial review that simulates failure post-mortems, critiques over-engineering, and identifies unstated assumptions. This systematic devil's advocate approach uncovers blind spots and potential failure points before execution begins.

What is an adversarial plan review and how does it work?▼

An adversarial plan review systematically attacks a proposed architecture or analysis document to find flaws. It operates by applying specific analytical lenses—such as failure post-mortems, over-engineering critiques, and red team destruction—to classify and address potential risks.

How do I find unstated assumptions in a project decision document?▼

To find unstated assumptions in a project decision document, use a structured plan review that explicitly lists hidden dependencies and their failure implications. Identifying these blind spots early combats confirmation bias and ensures all conditions for validity are met.

Can I use a devil's advocate review for any size of implementation plan?▼

Yes, you can use a devil's advocate review for any implementation plan by classifying it into Light, Standard, or Deep tiers. This classification adjusts the review depth, with Deep-tier plans optionally receiving an additional cold review by a subagent for maximum scrutiny.

When do I need a red team destruction analysis for my architecture decisions?▼

You need a red team destruction analysis for architecture decisions when preparing for a robust feature launch and wanting to combat confirmation bias. This deep-tier stress test actively simulates failure scenarios to uncover potential pitfalls and ensure plan validity.

What is the best way to review a new feature plan for potential failure points?▼

The best way to review a new feature plan for potential failure points is conducting an adversarial review. It identifies risks through simulated failure post-mortems and over-engineering critiques, systematically addressing all potential pitfalls to facilitate plan improvement.