plan-critic

Review development plans for feasibility, risk, and quality gaps.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/abranjith/spec-lite --skill plan-critic-abranjith
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-critic
Source: https://github.com/abranjith/spec-lite/tree/main/skills/plan-critic
Command: npx skills add https://github.com/abranjith/spec-lite --skill plan-critic-abranjith

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams catch weak assumptions, hidden risks, and missing decisions in a plan before implementation begins, reducing rework and avoidable defects.

Core Features & Use Cases

  • Feasibility Review: Checks whether the proposed approach can realistically be delivered with the stated scope, sequence, and constraints.
  • Risk and Quality Critique: Surfaces technical hazards, integration gaps, and product-quality issues that could slow execution or create churn.
  • Adaptiveness Check: Identifies design choices that would make the product easier to extend, maintain, or repurpose later.
  • Use Case: A developer asks for a critical review of a feature plan before coding starts so they can tighten scope, add missing decisions, and avoid implementation surprises.

Quick Start

Ask the Plan Critic to review .spec-lite/plan.md and return blocking findings, important findings, optional improvements, and a verdict.

Frequently Asked Questions about plan-critic

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

FAQPage Schema
How do I review a software development plan for feasibility and technical risks before implementation?

Reviewing a software development plan for feasibility and technical risks requires an independent engineering critique of scope, sequence, and constraints. This process surfaces hidden hazards and missing decisions, returning structured findings, concrete revisions, and a final readiness verdict.

What is the best way to pressure-test a feature specification to identify product quality gaps?

Pressure-testing a feature specification to identify product quality gaps involves critically analyzing the proposed delivery sequence and design choices. This reveals integration gaps and adaptiveness issues, ensuring the product is easier to maintain and extend before coding begins.

When do I need a pre-implementation plan review for my feature delivery sequence?

A pre-implementation plan review is needed when teams require an independent engineering assessment of a feature delivery sequence. It catches weak assumptions and missing decisions early, reducing rework and avoidable defects by providing a clear implementation readiness verdict.

How do I get structured findings and a readiness verdict from a plan critique?

Getting structured findings and a readiness verdict from a plan critique involves submitting a development plan for independent review. The critique returns blocking findings, important findings, optional improvements, and optional TODO captures to tighten scope and prevent execution surprises.

Can I use a critical analysis process to check implementation readiness for complex software designs?

Yes, a critical analysis process checks implementation readiness for complex software designs by evaluating feasibility and technical risk. It examines whether the proposed approach can realistically be delivered with stated constraints, identifying design choices that impact extensibility and maintenance.

What are the limitations of relying solely on a plan review before coding starts?

Relying solely on a plan review before coding starts limits detection to pre-implementation design flaws, missing decisions, and technical risks. It does not cover runtime defects or integration failures that emerge during actual execution, requiring subsequent testing phases.