plan-review
Get Gemini's review of Claude's implementation plans. Trigger when user wants a second opinion on a plan ("have Gemini review this plan", "get second opinion", "critique this plan"), or after Claude creates a plan file that needs validation before implementation.
When & Why to Use This Skill
The Plan Review skill leverages Google's Gemini to provide a rigorous second opinion on Claude's proposed implementation plans. By cross-referencing plans with the existing codebase, it identifies architectural gaps, potential risks, and missing edge cases, ensuring high-quality software development and reducing implementation errors through multi-model validation.
Use Cases
- Risk Assessment: Evaluate complex refactoring or migration plans for potential breaking changes, data loss risks, and rollback complexity.
- Completeness Check: Automatically verify if a new feature plan covers all necessary edge cases, testing requirements, and missing implementation steps.
- Architectural Validation: Use Gemini's codebase investigation tools to ensure a proposed plan aligns with the existing project structure and follows established patterns.
- Alternative Exploration: Get critical feedback on whether a proposed approach is optimal or if better alternatives should be considered before writing code.
| name | plan-review |
|---|---|
| description | Get Gemini's review of Claude's implementation plans. Trigger when user wants a second opinion on a plan ("have Gemini review this plan", "get second opinion", "critique this plan"), or after Claude creates a plan file that needs validation before implementation. |
Plan Review via Gemini
Have Gemini critique Claude's implementation plans for a second perspective.
Quick Start
cat ~/.claude/plans/example-plan.md | gemini "Review this implementation plan:
\$(cat)
Do not make any changes. Provide critique and feedback only." --allowed-tools read_file,codebase_investigator,glob,search_file_content,list_directory,write_todos -o text 2>&1
Pattern
Claude writes plans to ~/.claude/plans/. Pipe plan content via stdin since Gemini cannot read files outside the project directory:
cat ~/.claude/plans/example-plan.md | gemini "Review this implementation plan:
\$(cat)
Consider:
1. Are there gaps or missing steps?
2. Are there risks not addressed?
3. Is the approach optimal?
4. What alternatives should be considered?
Do not make any changes. Respond with feedback only." --allowed-tools read_file,codebase_investigator,glob,search_file_content,list_directory,write_todos -o text 2>&1
With Source Context
Pipe the plan via stdin and let Gemini read source files from the project:
cat ~/.claude/plans/auth-refactor.md | gemini "Review this implementation plan:
\$(cat)
Also read these source files for context:
- src/auth/login.ts
- src/middleware/session.ts
Evaluate if the plan addresses the actual codebase structure. Do not make any changes. Respond with feedback only." --allowed-tools read_file,codebase_investigator,glob,search_file_content,list_directory,write_todos -o text 2>&1
Focused Reviews
Risk assessment:
cat ~/.claude/plans/migration.md | gemini "Review this plan for risks:
\$(cat)
Evaluate:
- Breaking changes
- Data loss potential
- Rollback complexity
- Dependencies that could fail
Do not make any changes. Respond with feedback only." --allowed-tools read_file,codebase_investigator,glob,search_file_content,list_directory,write_todos -o text 2>&1
Completeness check:
cat ~/.claude/plans/feature.md | gemini "Review this plan for completeness:
\$(cat)
Evaluate:
- Are all edge cases covered?
- Is testing addressed?
- Are there missing steps?
Do not make any changes. Respond with feedback only." --allowed-tools read_file,codebase_investigator,glob,search_file_content,list_directory,write_todos -o text 2>&1
Notes
- Gemini must not make any changes, provide feedback ONLY.
- Pipe plan content via stdin using
$(cat)- Gemini cannot read~/.claude/plans/directly - Gemini can explore the project using
--allowed-tools read_file,codebase_investigator,glob,search_file_content,list_directory,write_todos - Gemini respects
.gitignore- it cannot read files matching gitignore patterns - Requires
dangerouslyDisableSandbox: truefor Bash calls - May take 2-3 minutes for thorough review with source analysis
- See
references/setup.mdfor troubleshooting