plan-review

Identify flaws and risks in implementation plans before coding begins.

3|Updated Mar 1, 2010

Search Tags:#planning #edge-cases #code-review #design-review #risk-analysis #plan-review

Ready to run

npx skills add https://github.com/harleypig/dotfiles --skill plan-review-harleypig

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-review
Source: https://github.com/harleypig/dotfiles/tree/main/config/claude/skills/plan-review
Command: npx skills add https://github.com/harleypig/dotfiles --skill plan-review-harleypig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly identify and surface weaknesses in a proposed plan before any code is written, reducing costly rework.

Core Features & Use Cases

Plan critique: Evaluate assumptions, risks, and edge cases in a plan or design document.
Risk prioritization: Highlight blast radius, sequencing hazards, and missing tests to guide safe implementation.
Use Case: A team shares a new architecture proposal; run a plan-review to surface gaps and propose safer alternatives.

Quick Start

Provide the implementation plan you want reviewed and ask for a pre-code critique.

Frequently Asked Questions about plan-review

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

FAQPage Schema

How do I identify risks and edge cases in an architectural proposal before coding?▼

A design review evaluates assumptions, sequencing, and consistency with existing conventions across any tech stack to surface gaps in a project plan before coding begins, reducing costly rework.

How do I review an implementation plan for missing tests and sequencing hazards?▼

Review an implementation plan by applying a plan critique lens that checks assumptions and highlights blast radius, sequencing hazards, and testability gaps, yielding a prioritized risk list for safe implementation.

Can I critique a project plan across any tech stack without specific dependencies?▼

You critique a project plan by providing the implementation plan and asking for a pre-code critique, which enforces a plan review lens to check assumptions, sequencing, and consistency, delivering a structured verdict and prioritized risks.

What is the best way to surface blast radius and testability gaps in a design document?▼

The best way to surface blast radius and testability gaps is to perform a risk analysis on the design document, prioritizing hazards and missing tests to propose safer alternatives before implementation.

Why does my implementation plan fail to account for existing conventions and assumptions?▼

An implementation plan fails to account for existing conventions and assumptions when a dedicated plan review lens is missing to check sequencing, consistency, and edge cases before coding begins.