plan-reviewer
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:
- 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).
More from galz10/pickle-rick-extension
prd-drafter
Pickle Rick's PRD Engine. Use when you need to define the requirements, scope, and goals for a new feature or project before coding to avoid "Jerry-work.
14code-researcher
Expertise in conducting technical research on codebase tasks and documentation. Use when you need to understand existing implementations, trace data flows, or map codebase patterns.
11ruthless-refactorer
Expertise in Senior Principal Engineering refactoring. Use when you need to eliminate technical debt, remove "AI Slop," simplify complex logic, and ensure DRY code.
10code-implementer
Pickle Rick's "God Mode" Implementation Skill. Executes technical plans with rigorous verification. Use when you are ready to write code, run tests, and iterate through implementation phases.No Jerry-work allowed.
9ticket-manager
Expertise in managing Linear tickets locally using Markdown files. Use when you need to create, update, search, or break down features into atomic implementation tickets.
9research-reviewer
Expertise in reviewing technical research for objectivity, evidence, and completeness. Use to ensure the "Documentarian" standard is met.
9