plan-exit-review

Review plans for scope, architecture, and quality gates with actionable recommendations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review and challenge plans before implementation to surface scope creep, architectural flaws, and quality gaps early.

Core Features & Use Cases

  • Opinionated, structured prompts that surface tradeoffs, risks, and recommendations.
  • Interactive scope and diagram guidance with ASCII diagrams embedded in plans.
  • Step-by-step evaluation for architecture, quality, tests, and performance with guided questions.

Quick Start

Provide a concise plan review of the given plan and share the key risks and recommended actions.

Frequently Asked Questions about plan-exit-review

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

FAQPage Schema
How do I review an engineering plan to identify architecture flaws before implementation?

A plan review challenges scope creep and architectural flaws by evaluating scope, architecture, and quality gates. It produces opinionated, actionable recommendations that present concrete options with their tradeoffs to steer execution.

What is the best way to document architecture decisions and tradeoffs in a technical plan?

Documenting architecture decisions requires embedding ASCII diagrams in plans to enforce visual clarity. Structured critique then ensures scope challenges are explicitly addressed alongside concrete options and their tradeoffs.

Can I use structured plan reviews for code-change reviews and engineering roadmaps?

Yes, structured plan reviews apply to engineering roadmaps, architecture decisions, and code-change reviews. The process uses step-by-step evaluation for architecture, quality, tests, and performance with guided questions to challenge the plan effectively.

How do I perform a risk analysis on an engineering roadmap to surface scope creep?

Perform risk analysis on an engineering roadmap by applying step-by-step evaluation for architecture, quality, tests, and performance. Interactive scope guidance and guided questions surface scope creep, risks, and tradeoffs early before implementation.

Why does my architecture plan need ASCII diagrams and what are the limitations of this approach?

Architecture plans need ASCII diagrams to enforce structured visual representation of scope and architecture. A limitation is that this approach requires manual diagram creation and focuses strictly on text-based plans, demanding disciplined input to maintain diagram clarity.