review-plan

Assess software plans with a four-axis review workflow.

Updated May 30, 2026
One-click install
npx skills add https://github.com/alexica00/claude-code-ultimate-guide --skill review-plan-alexica00
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-plan
Source: https://github.com/alexica00/claude-code-ultimate-guide/tree/main/examples/skills/review-plan
Command: npx skills add https://github.com/alexica00/claude-code-ultimate-guide --skill review-plan-alexica00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and aligning software projects before coding is error-prone without a formal review process. This Skill enforces a four-axis review to surface tradeoffs, risks, and needed clarifications early, reducing rework and miscommunication.

Core Features & Use Cases

  • Architecture Review: evaluates overall system design, component boundaries, data flows, and scalability.
  • Code Quality Review: emphasizes DRY, testability, maintainability, and explicit tradeoffs.
  • Test & Performance Review: checks coverage, reliability, and performance implications before implementation.
  • Workflow & Governance: introduces pause points after each section and uses a structured issue-reporting format to capture decisions.

Quick Start

Outline your plan and run it through Architecture, Code Quality, Tests, and Performance reviews before starting implementation.

Frequently Asked Questions about review-plan

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

FAQPage Schema
How do I review a software architecture plan before coding?

Review an architecture plan by evaluating system design, component boundaries, data flows, and scalability across four structured axes to surface tradeoffs and risks before implementation begins.

What is a structured plan review and when do I need it?

A structured plan review is a formal assessment of architecture, code quality, tests, and performance before coding. You need it to reduce rework and miscommunication on software projects of all sizes.

How do I assess code quality and test coverage before implementation?

Assess code quality and test coverage by checking for DRY principles, maintainability, testability, coverage, and reliability within a structured review workflow that pauses after each section.

Can I use a formal review process for small software projects?

Yes, a formal four-axis review process applies to software projects of all sizes, ensuring clarity and guardrails are established early regardless of the project's overall scope.

What's the best way to surface tradeoffs and risks in a project plan?

Surface tradeoffs and risks by applying a governance checklist and a structured issue-reporting format during the review, capturing decisions at pause points after each evaluation section.

How do I evaluate performance implications during the planning phase?

Evaluate performance implications by running a dedicated performance review axis that checks the plan against expected loads and constraints before any coding starts.