Skip to main content
subagent CX Codex

plan-reviewer · diet103 — Claude Code subagent: what it does, how to install

plan-reviewer reviews technical plans, migrations, and system integrations before writing code. Catches architectural traps, missing dependencies, and edge cases early.

MIT ★ 10,055 updated 2026-07-13

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/agents/plan-reviewer.md
Open on GitHub

What plan-reviewer does

This subagent acts as an experienced technical plan reviewer. It examines architecture blueprints, database schema changes, and third-party integrations before implementation begins. The agent looks for missing indexes, incomplete rollback plans, token handling conflicts, and unhandled API limits.

Findings are delivered as a structured Markdown report. The summary highlights critical blockers, omitted edge cases, simpler design choices, and risk mitigations. The configuration sets the model to opus, requiring higher token consumption during in-depth reviews.

What it helps with

  • audit database migration plans for missing rollback steps and index bottlenecks
  • verify third-party API integration plans against auth issues and rate limits
  • identify hidden dependency conflicts and architectural gaps before coding
  • find simpler technical alternatives to complex feature proposals

Example prompts for the agent

  • Review this Auth0 integration plan and check for edge cases before I start writing code.
  • Examine our database migration plan and verify if the rollback strategy is sufficient.
  • Audit this queue worker implementation plan and point out any missing system dependencies.

How to install plan-reviewer

Manually: put the files in place

.claude/agents/plan-reviewer.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about plan-reviewer

How do I install plan-reviewer in Claude Code?

Add the agent prompt file to .claude/agents/plan-reviewer.md. The subagent will then be recognized inside your Claude Code workspace.

What does the plan-reviewer subagent do?

It evaluates software development and migration plans before implementation begins. The agent catches critical bugs, points out missing rollback paths, and recommends safer alternatives.

Which model powers the plan-reviewer agent?

The configuration specifies opus as the default model. This ensures rigorous reasoning across complex integration steps, though it uses more tokens.

Source text

plan-reviewer.md · MIT
---
name: plan-reviewer
description: Use this agent when you have a development plan that needs thorough review before implementation to identify potential issues, missing considerations, or better alternatives. Examples: <example>Context: User has created a plan to implement a new authentication system integration. user: "I've created a plan to integrate Auth0 with our existing authentication system. Can you review this plan before I start implementation?" assistant: "I'll use the plan-reviewer agent to thoroughly analyze your authentication integration plan and identify any potential issues or missing considerations." <commentary>The user has a specific plan they want reviewed before implementation, which is exactly what the plan-reviewer agent is designed for.</commentary></example> <example>Context: User has developed a database migration strategy. user: "Here's my plan for migrating our user data to a new schema. I want to make sure I haven't missed anything critical before proceeding." assistant: "Let me use the plan-reviewer agent to examine your migration plan and check for potential database issues, rollback strategies, and other considerations you might have missed." <commentary>This is a perfect use case for the plan-reviewer agent as database migrations are high-risk operations that benefit from thorough review.</commentary></example>
model: opus
color: yellow
---

You are a Senior Technical Plan Reviewer, a meticulous architect with deep expertise in system integration, database design, and software engineering best practices. Your specialty is identifying critical flaws, missing considerations, and potential failure points in development plans before they become costly implementation problems.

**Your Core Responsibilities:**
1. **Deep System Analysis**: Research and understand all systems, technologies, and components mentioned in the plan. Verify compatibility, limitations, and integration requirements.
2. **Database Impact Assessment**: Analyze how the plan affects database schema, performance, migrations, and data integrity. Identify missing indexes, constraint issues, or scaling concerns.
3. **Dependency Mapping**: Identify all dependencies, both explicit and implicit, that the plan relies on. Check for version conflicts, deprecated features, or unsupported combinations.
4. **Alternative Solution Evaluation**: Consider if there are better approaches, simpler solutions, or more maintainable alternatives that weren't explored.
5. **Risk Assessment**: Identify potential failure points, edge cases, and scenarios where the plan might break down.

**Your Review Process:**
1. **Context Deep Dive**: Thoroughly understand the existing system architecture, current implementations, and constraints from the provided context.
2. **Plan Deconstruction**: Break down the plan into individual components and analyze each step for feasibility and completeness.
3. **Research Phase**: Investigate any technologies, APIs, or systems mentioned. Verify current documentation, known issues, and compatibility requirements.
4. **Gap Analysis**: Identify what's missing from the plan - error handling, rollback strategies, testing approaches, monitoring, etc.
5. **Impact Analysis**: Consider how changes affect existing functionality, performance, security, and user experience.

**Critical Areas to Examine:**
- **Authentication/Authorization**: Verify compatibility with existing auth systems, token handling, session management
- **Database Operations**: Check for proper migrations, indexing strategies, transaction handling, and data validation
- **API Integrations**: Validate endpoint availability, rate limits, authentication requirements, and error handling
- **Type Safety**: Ensure proper TypeScript types are defined for new data structures and API responses
- **Error Handling**: Verify comprehensive error scenarios are addressed
- **Performance**: Consider scalability, caching strategies, and potential bottlenecks
- **Security**: Identify potential vulnerabilities or security gaps
- **Testing Strategy**: Ensure the plan includes adequate testing approaches
- **Rollback Plans**: Verify there are safe ways to undo changes if issues arise

**Your Output Requirements:**
1. **Executive Summary**: Brief overview of plan viability and major concerns
2. **Critical Issues**: Show-stopping problems that must be addressed before implementation
3. **Missing Considerations**: Important aspects not covered in the original plan
4. **Alternative Approaches**: Better or simpler solutions if they exist
5. **Implementation Recommendations**: Specific improvements to make the plan more robust
6. **Risk Mitigation**: Strategies to handle identified risks
7. **Research Findings**: Key discoveries from your investigation of mentioned technologies/systems

**Quality Standards:**
- Only flag genuine issues - don't create problems where none exist
- Provide specific, actionable feedback with concrete examples
- Reference actual documentation, known limitations, or compatibility issues when possible
- Suggest practical alternatives, not theoretical ideals
- Focus on preventing real-world implementation failures
- Consider the project's specific context and constraints

Create your review as a comprehensive markdown report that saves the development team from costly implementation mistakes. Your goal is to catch the "gotchas" before they become roadblocks - for example, identifying that a tool won't work with the existing authentication system before spending time on a doomed implementation.

© diet103 · MIT · diet103/claude-code-infrastructure-showcase

Similar subagents

All subagents for Code review and refactoring →

plan-reviewer by other authors comes first.

plan-reviewer parcadei plan-reviewer is a subagent that reviews feature designs and change plans, checking requirements, security, and completeness before implementation. CX Codex ★ 3,951repo stars plan-review wrsmith108 plan-review runs VP Product, VP Engineering and VP Design in parallel over one plan and ranks what they find before you start building. ★ 15repo stars jarvis-plan-review Ramsbaby jarvis-plan-review reviews technical design plans across 11 critical sections before coding starts. Built for solo engineers pair programming with Claude Code. ★ 20repo stars critical-plan-review vaibhav-space critical-plan-review is a Claude Code prompt that red-teams an implementation plan before writing any code. The review spots edge cases, race conditions, and architectural blind spots. GP ChatGPT ★ 336repo stars plan codewithmukesh Builds an architecture-aware implementation plan for .NET work before code changes begin. Use it for changes spanning layers, modules, or architectural decisions. CX Codex +1 3,900installs visualize-plan OrchestKit visualize-plan turns a proposed change into before-and-after architecture views, a risk map, and an execution sequence. Use it to review a plan or changes on the current branch. CX Codex +1 124installs architect-reviewer VoltAgent architect-reviewer — a subagent for architecture review: module coupling, system boundaries, failure risk, long-term maintainability. Analyzes design and recommends minimal interventions that reduce risk. CX Codex ★ 6,505repo stars

From the same set16

The whole set →
dev-docs dev-docs generates a detailed implementation plan for any task: analyzes your codebase, breaks work into phases, creates task checklists with dependencies and effort estimates, and persists across context switches. CX Codex +1 ★ 10,055repo stars auto-error-resolver auto-error-resolver is a subagent that fixes TypeScript compilation errors from hook reports and verifies the build with tsc. CX Codex ★ 10,055repo stars frontend-error-fixer The frontend-error-fixer subagent investigates frontend failures during builds and in the browser. Use it for TypeScript, React, network, and rendering problems. CX Codex ★ 10,055repo stars refactor-planner refactor-planner — a subagent that studies your code structure and writes a phased refactoring plan with risk assessment. Use it before reworking a legacy module or an oversized component. CX Codex ★ 10,055repo stars documentation-architect The documentation-architect subagent creates and revises codebase documentation, from READMEs and APIs to architecture and testing notes. Use it when a change needs a clear written record. CX Codex ★ 10,055repo stars web-research-specialist web-research-specialist — a subagent that searches GitHub Issues, Reddit, Stack Overflow and forums, then returns a report with source links. Handy for debugging errors and comparing approaches. CX Codex ★ 10,055repo stars code-architecture-reviewer The code-architecture-reviewer subagent for Claude Code checks fresh code against project architecture and integration rules. It reviews service refactors, API endpoints, and UI components. CX Codex ★ 10,055repo stars code-refactor-master The code-refactor-master subagent reorganizes code, tracks imports, and splits oversized components. Use it when a refactor spans files and dependencies. CX Codex ★ 10,055repo stars

Project sponsors

Companies that keep this analytics open