plan-critique

Analyze plan files for risks, assumptions, completeness, schema conformance, and wave overlaps.

1|Updated Jun 19, 2026
One-click install
npx skills add https://github.com/9thLevelSoftware/legion-ascended --skill plan-critique
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-critique
Source: https://github.com/9thLevelSoftware/legion-ascended/tree/main/skills/plan-critique
Command: npx skills add https://github.com/9thLevelSoftware/legion-ascended --skill plan-critique

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pypdf, pdfplumber, pdf2image, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill performs a pre-mortem analysis and assumption hunting to stress-test plans before execution, identifying risks, blind spots, and over-optimism.

Core Features & Use Cases

  • Pre-mortem Analysis: Assumes the project has already failed and identifies causes.
  • Assumption Hunting: Extracts foundational beliefs embedded in the plan and flags weak ones.
  • Completeness Check: Evaluates the plan's coverage for error handling, edge cases, and state management.
  • Decision Completeness Check: Ensures each plan is decision-complete and not open to interpretation.
  • Schema Conformance Check: Validates plan frontmatter against the v6.0 schema.
  • Wave File Overlap Detection: Detects overlapping files_modified entries in plans within the same wave.
  • Agent Selection: Identifies agents best suited to perform critique passes.
  • Critique Report and Routing: Synthesizes findings and routes to user action.

Quick Start

Run the plan-critique skill on your plan file to get a detailed critique report.

Frequently Asked Questions about plan-critique

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

FAQPage Schema
How do I perform a pre-mortem analysis on a software development plan?

Pre-mortem analysis assumes your software development plan has already failed and identifies root causes, blind spots, and over-optimism. It stress-tests foundational assumptions and flags weak embedded beliefs to resolve risks before execution begins.

Can I check if my plan is decision-complete and not open to interpretation?

Yes, a decision completeness check evaluates your plan to ensure every decision is fully resolved and unambiguous. It prevents open-to-interpretation gaps by validating schema conformance and verifying complete state management coverage.

Do I need Python libraries to run a plan critique and completeness check?

Yes, running a plan critique requires Python libraries including pypdf, pdfplumber, and pdf2image. These dependencies enable automated document extraction, schema conformance validation, and wave file overlap detection on your plan files.

What is the best way to detect overlapping files modified in plan waves?

Wave file overlap detection scans your plan files to identify overlapping files_modified entries within the same wave. This prevents execution conflicts and ensures your software development workflows remain robust and structurally isolated.

How does assumption hunting identify risks in project plans?

Assumption hunting extracts foundational beliefs embedded in your project plan and flags the weak ones. By isolating unverified assumptions, it exposes blind spots and over-optimism before execution, producing a synthesized critique report for routing.