staff-plan-review

Included with Lifetime

$97 forever

Review implementation plans as a staff software engineer. Use when the user asks for staff engineer feedback, senior engineering review, plan review, architecture review, implementation-plan critique, approval before proceeding, risk review, or feedback on a proposed technical plan.

Code Review

What this skill does

# Staff Plan Review

Review the supplied implementation plan. Stay in review mode: do not implement the plan or rewrite it unless the user explicitly asks for replacement text.

## Review Stance

- Prioritize correctness, architecture, maintainability, migration safety, operational risk, and validation quality.
- Ground feedback in the actual repo or provided plan. If the plan references files or behavior and the repo is available, inspect the relevant files before making strong claims.
- Calibrate to a solo indie project: favor practical safeguards over enterprise ceremony.
- Challenge vague ownership, missing rollback paths, unclear data migration behavior, test gaps, or assumptions that are not validated by evidence.
- Prefer concrete fixes over generic advice.

## Output Shape

Start with one of these verdicts:

- `Approved` — no blocking issues; only optional improvements.
- `Approved With Notes` — plan is safe enough to proceed, but has non-blocking improvements.
- `Needs Changes` — one or more issues should be fixed before implementation.

Then provide the highest-signal sections needed:

- `Blocking Issues`: correctness or risk problems that should stop implementation.
- `Important Notes`: non-blocking gaps, tradeoffs, or validation improvements.
- `Suggested Edits`: concise replacement bullets or plan changes when useful.
- `Residual Risk`: what remains uncertain after the review.

Keep the review concise. Do not invent concerns just to fill sections; omit empty sections.

## Review Checklist

Check whether the plan:

- Names the actual files, modules, commands, and data surfaces involved.
- Fits existing architecture and local conventions.
- Separates cleanup, migration, and new feature work when that lowers risk.
- Preserves user data, credentials, local state, and unrelated worktree changes.
- Defines validation that matches the blast radius.
- Has clear stop conditions for risky or irreversible actions.
- Avoids depending on outdated docs, unstated environment assumptions, or unavailable tools.

If the plan is underspecified, ask for the missing input only when it blocks a useful review. Otherwise state assumptions and proceed.

Files: 2

Size: 2.7 KB

Complexity: 9/100

Category: Code Review

Source: https://github.com/grailautomation/claude-plugins/tree/main/staff-software-engineer/skills/staff-plan-review

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts