Plan review is a step you take before building anything. It checks your plan file and makes sure it is ready. A panel of reviewers looks at your plan and gives feedback.
The panel is made up of different agents. They look for problems and mark them as high, medium, or low priority. Each agent gives a verdict like approve, revise, or drop.
If all reviewers approve, you can proceed to build. If there are problems, you fix them and the panel reviews again. This helps you catch issues early and avoid mistakes.
Global
mkdir -p ~/.claude/skills/plan-reviewProject
mkdir -p .claude/skills/plan-reviewImprove Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Codebase Designmattpocock/skills
Create deep modules with tiny interfaces and lots of hidden logic for testability
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective