review-plan

Guide structured plan reviews before implementation to catch design flaws.

Updated Aug 23, 2026

Search Tags:#workflow #architecture #quality #plan #guidelines #code-review

Ready to run

npx skills add https://github.com/srednoff888-art/4 --skill review-plan-srednoff888-art

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-plan
Source: https://github.com/srednoff888-art/4/tree/main/examples/skills/review-plan
Command: npx skills add https://github.com/srednoff888-art/4 --skill review-plan-srednoff888-art

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines risk-aware planning by ensuring a thorough, structured plan review occurs before any code is written, reducing design flaws and rework.

Core Features & Use Cases

Structured review checklist across architecture, code quality, tests, and performance to catch issues early.
Pause-for-feedback workflow requiring stakeholder input between sections to align decisions.
Guided decision gates with explicit tradeoffs and risk considerations before coding starts.

Quick Start

Instruct the AI to run a structured review workflow on the current project before writing any code.

Frequently Asked Questions about review-plan

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

FAQPage Schema

What is a plan review before coding and why do I need one?▼

A plan review is a structured evaluation of architecture, code quality, tests, and performance before implementation begins. You need it to catch design flaws early, align stakeholders, and reduce costly rework.

How do I run a structured code review plan for my project architecture?▼

Run a structured review workflow by applying an evaluation checklist across architecture, modules, and pipelines. Pause for stakeholder feedback between sections to document tradeoffs and pass decision gates before coding.

Can I use this plan review workflow for existing code changes and modules?▼

Yes, the plan review workflow applies to software projects and code changes across architecture and modules. It evaluates design decisions and assesses risks for modifications before you implement the actual coding.

What's the best way to document design tradeoffs during a project planning review?▼

The best way to document design tradeoffs is using guided decision gates that require explicit risk considerations and stakeholder input. This ensures documented quality gaps and architectural choices are reviewed before development starts.

What happens if stakeholders skip the feedback pauses in the plan review workflow?▼

Skipping stakeholder feedback pauses removes the alignment mechanism for design decisions. The workflow requires stakeholder input between sections to ensure documented tradeoffs are evaluated before passing decision gates and starting coding.