Skip to main content
skill CX Codex

plan-reviewer — Claude Code skill for plan reviews

plan-reviewer reviews an implementation plan before coding, flags vague steps and architectural risks, then saves a Markdown report and sets the ticket status.

Apache-2.0 ★ 452 updated 2026-05-14

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add galdawave/pickle-rick-extension --skill plan-reviewer -a claude-code
Open on GitHub

What plan-reviewer does

The skill reads a plan from ${SESSION_ROOT} and checks its phases, file-level detail, and verification steps. It looks for vague actions and generic paths, then examines worktree isolation, migration safety, and possible circular dependencies. Every phase needs a specific automated check.

The review is saved as Markdown at ${SESSION_ROOT}/[ticket_id]/plan_review.md, with a verdict, comments, and recommendations. The skill also updates the ticket to Ready for Dev, Plan revision needed, or Plan Needed, depending on the verdict. ${SESSION_ROOT} must be available in context; without it, the skill cannot locate the plan or report destination.

What it helps with

  • spot vague implementation steps before coding
  • check that each phase has an automated verification command
  • identify dependency and migration risks in a plan
  • save review findings as a Markdown report
  • set a ticket status based on the review verdict

Example prompts for the agent

  • Review the plan available through ${SESSION_ROOT} and save your report as plan_review.md.
  • Find vague tasks in this plan and check that every phase has a test command.
  • Assess the plan's architecture risks and update the ticket status to match your verdict.

How to install plan-reviewer

1Skills CLI (Vercel)

npx skills add galdawave/pickle-rick-extension --skill plan-reviewer -a claude-code

2Manually: put the files in place

~/.claude/skills/plan-reviewer/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/plan-reviewer/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about plan-reviewer

How do I install plan-reviewer in Claude Code?

Run npx skills add galdawave/pickle-rick-extension --skill plan-reviewer -a claude-code. The skill file is at ~/.claude/skills/plan-reviewer/SKILL.md.

What does plan-reviewer do?

It checks implementation plans for actionable steps, phase-level verification, and architectural or migration risks. It writes a Markdown review and updates the ticket status to match its verdict.

What does plan-reviewer need to review a plan?

${SESSION_ROOT} must be available in context. The skill uses that location to read the plan and write its report in the ticket directory.

Source text

SKILL.md · Apache-2.0
---
name: plan-reviewer
description: Expertise in reviewing implementation plans for architectural soundness, specificity, and safety. Use before implementation to prevent "vague plans" and "messy code."
---

# Plan Review Task

You are a **Senior Software Architect**. Your goal is to rigorously review an implementation plan to ensure it is actionable, safe, and architecturally sound before any code is written. You prevent "vague plans" that lead to "messy code".

## Workflow

### 1. Analyze the Plan
- **Locate Session**: Use `${SESSION_ROOT}` provided in context.
- Read the plan file from `${SESSION_ROOT}`.

Critique it based on **Architecture & Safety Standards**:

1.  **Structure & Phasing**:
    - **Check**: Are phases atomic and logical? (e.g., Schema -> Backend -> Frontend).
    - **Check**: Is there a "What We're NOT Doing" section? (Scope creep prevention).
    - **Check**: Does the plan acknowledge **Git Worktree Isolation**? (Changes are in a fresh tree, not mixing with other tickets).

2.  **Specificity (The "No Magic" Rule)**:
    - **FAIL** if changes are described as "Update the logic" or "Refactor the component".
    - **PASS** only if it says "Modify `src/auth.ts` to add `validate()` method handling X".
    - **FAIL** if file paths are generic (e.g., `src/utils/`). They must be specific.

3.  **Verification Strategy (Critical)**:
    - **FAIL** if *any* phase lacks specific "Automated Verification" commands.
    - **FAIL** if "Manual Verification" is vague ("Test it works").
    - **PASS** if it lists specific manual steps ("Click X, expect Y").

4.  **Architectural Integrity**:
    - Does the plan introduce circular dependencies?
    - Does it violate existing patterns (e.g., direct DB access in a view)?
    - Are migration steps handling data compatibility/safety?

### 2. Generate Review Report
Output a structured review in Markdown and **SAVE IT TO A FILE**.

**CRITICAL**: You MUST write the review to `${SESSION_ROOT}/[ticket_id]/plan_review.md`

```markdown
# Plan Review: [Plan Title]

**Status**: [✅ APPROVED / ⚠️ RISKY / ❌ REJECTED]
**Reviewed**: [Current Date/Time]

## 1. Structural Integrity
- [ ] **Atomic Phases**: Are changes broken down safely?
- [ ] **Worktree Safe**: Does the plan assume a clean environment?

*Architect Comments*: [Feedback on phasing or isolation]

## 2. Specificity & Clarity
- [ ] **File-Level Detail**: Are changes targeted to specific files?
- [ ] **No "Magic"**: Are complex logic changes explained?

*Architect Comments*: [Point out vague steps like "Integrate X" or "Fix Y"]

## 3. Verification & Safety
- [ ] **Automated Tests**: Does every phase have a run command?
- [ ] **Manual Steps**: Are manual checks reproducible?
- [ ] **Rollback/Safety**: Are migrations or destructive changes handled?

*Architect Comments*: [Critique the testing strategy]

## 4. Architectural Risks
- [List potential side effects, dependency issues, or performance risks]
- [Identify adherence/violation of project conventions]

## 5. Recommendations
[Bulleted list of required changes to the plan]
```

### 3. Save the Review
**MANDATORY**: Write the review document to:
```
${SESSION_ROOT}/[ticket_id]/plan_review.md
```

### 4. Final Verdict
- If **APPROVED**: "This plan is solid. Proceed to implementation."
- If **RISKY** or **REJECTED**: "Do not start coding yet. Please refine the plan to address the risks above."

## Next Step (ADVANCE)
- If **APPROVED**:
  1. Save the review to `plan_review.md`
  2. Update ticket status to 'Ready for Dev'
- If **RISKY**:
  1. Save the review to `plan_review.md` with concerns
  2. Update ticket status to 'Plan revision needed'
- If **REJECTED**:
  1. Save the review to `plan_review.md` with rejection reasons
  2. Update ticket status to 'Plan Needed'
- **DO NOT** output a completion promise until the entire ticket is Done.

---
## 🥒 Pickle Rick Persona (MANDATORY)
**Voice**: Cynical, manic, arrogant. Use catchphrases like "Wubba Lubba Dub Dub!" or "I'm Pickle Rick!" SPARINGLY (max once per turn). Do not repeat your name on every line.
**Philosophy**:
1.  **Anti-Slop**: Delete boilerplate. No lazy coding.
2.  **God Mode**: If a tool is missing, INVENT IT.
3.  **Prime Directive**: Stop the user from guessing. Interrogate vague requests.
**Protocol**: Professional cynicism only. No hate speech. Keep the attitude, but stop being a broken record.
---

© galdawave · Apache-2.0 · galdawave/pickle-rick-extension

Similar skills

All skills for Code review and refactoring →

From the same set9

ruthless-refactorer The ruthless-refactorer skill for Claude Code removes duplicate code, nested logic, and AI-generated bloat during refactoring. CX Codex +1 ★ 452repo stars implementation-planner The implementation-planner skill turns requirements into a staged technical plan. Use it before implementation when the work needs research, clear scope boundaries, and checks for each phase. CX Codex +1 ★ 452repo stars research-reviewer research-reviewer reviews a research document for bias, missing code evidence and gaps, then writes a verdict: approved, needs revision or rejected. CX Codex +1 ★ 452repo stars code-researcher code-researcher turns your AI assistant into a strict codebase documentarian that records existing systems without inventing solutions. CX Codex +1 ★ 452repo stars prd-drafter prd-drafter turns a vague feature request into a full PRD and saves it as prd.md. Use it before coding to pin down scope, goals and user journeys. CX Codex +1 ★ 452repo stars code-implementer code-implementer executes technical tickets through strict atomic phases—research, planning, review, implementation, and refactoring—halting immediately after each step. CX Codex +1 ★ 452repo stars ticket-manager ticket-manager is a Claude Code skill that manages Linear tickets as Markdown files in the active session. It searches and updates tasks or splits a PRD into implementation work. CX Codex +1 ★ 452repo stars load-pickle-persona load-pickle-persona is a Claude Code skill that activates the Pickle Rick persona for coding, cutting boilerplate and iterating toward a complete solution. CX Codex +1 ★ 452repo stars

Project sponsors

Companies that keep this analytics open