plan-review

Review technical plans for risks, assumptions, and scope problems.

310|45|Updated Feb 22, 2026

Search Tags:#design #audit #engineering #assumptions #scope #risk-assessment #plan-review

Ready to run

npx skills add https://github.com/Mathews-Tom/armory --skill plan-review-mathews-tom

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-review
Source: https://github.com/Mathews-Tom/armory/tree/main/skills/plan-review
Command: npx skills add https://github.com/Mathews-Tom/armory --skill plan-review-mathews-tom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-implementation audits surface risks, bad assumptions, missing pieces, and scope problems before any code is written, reducing rework and costly reversions.

Core Features & Use Cases

Plan Comprehension: Read and summarize a plan to confirm goals, constraints, and non-goals.
Assumption Challenge: Identify implicit assumptions and map consequences if they fail.
Risk & Failure Mapping: Enumerate failure modes, blast radii, and recovery strategies across components.
Scope & Integration Review: Assess dependencies, interfaces, and integration points to avoid dead-ends.
Verdict & Guidance: Produce a final ship/rethink/reject verdict with actionable next steps.

Quick Start

Provide the plan document to review and confirm the desired review lens to run the full audit sequence.

Frequently Asked Questions about plan-review

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

FAQPage Schema

How do I audit a technical design document for bad assumptions and scope problems before coding?▼

Pre-implementation audits surface risks, bad assumptions, missing pieces, and scope problems by applying a structured, multi-step review process to design documents, producing a severity-tagged verdict to reduce costly rework.

What is the best way to assess risk and failure modes in an engineering plan?▼

Risk and failure mapping enumerates failure modes, blast radii, and recovery strategies across components in an engineering plan, ensuring you identify missing pieces and map consequences if implicit assumptions fail.

How do I review scope and integration points to avoid dead-ends in a software proposal?▼

Scope and integration review assesses dependencies, interfaces, and integration points in a software proposal to identify scope problems and avoid dead-ends before any implementation begins.

Can I get a ship or reject verdict from evaluating a product plan?▼

Evaluating a product plan produces a final severity-tagged verdict of Ship, Ship with changes, Rethink, or Reject, providing actionable next steps based on the identified risks and assumption challenges.

When do I need to stress-test a technical plan?▼

You need to stress-test a technical plan when you want to confirm goals, constraints, and non-goals before implementation, ensuring implicit assumptions are challenged and failure modes are mapped to prevent rework.