plan-review

Ground implementation plans against the real codebase to identify flaws and gaps.

23|Updated Jul 4, 2025
One-click install
npx skills add https://github.com/jimmyff/nixfiles --skill plan-review-jimmyff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-review
Source: https://github.com/jimmyff/nixfiles/tree/main/dotfiles/ai/skills/plan-review
Command: npx skills add https://github.com/jimmyff/nixfiles --skill plan-review-jimmyff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Grounds an implementation plan against the real codebase to identify flaws and gaps.

Core Features & Use Cases

  • Ground-truths plans by cross-referencing with the actual codebase.
  • Provides multi-lens critique (correctness, architecture, risk) and a prioritized verdict.
  • Generates concrete, actionable fixes and a handoff-ready summary for execution.

Quick Start

Perform a plan-review on <plan-file> to begin the grounding and critique.

Frequently Asked Questions about plan-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review an implementation plan against my existing codebase?

To review an implementation plan against your codebase, you can ground the plan's assumptions by cross-referencing design docs with real code. This process identifies architectural flaws, verifies correctness, and generates a prioritized, actionable verdict.

What is code grounding for design critiques?

Code grounding for design critiques is the process of verifying a proposal's assumptions by cross-referencing it with the actual codebase. This identifies hidden risks and architectural gaps to ensure the plan is technically feasible.

How do I identify architectural risks in a software proposal?

You identify architectural risks in a software proposal by applying a multi-lens analysis that checks correctness, architecture, and risk against the real codebase. This grounds objections in code evidence rather than theoretical assumptions.

Can I generate actionable fixes during a plan review?

Yes, you can generate actionable fixes during a plan review by grounding the critique in code evidence. The process delivers concrete fixes and a handoff-ready summary for execution, prioritizing the most critical flaws first.

Does plan review work for design documents and technical proposals?

Yes, plan review works for design documents and technical proposals. It verifies assumptions, architecture, and risk by cross-referencing the documents directly with the actual codebase to deliver a prioritized verdict.

What's the best way to verify assumptions in an architecture review?

The best way to verify assumptions in an architecture review is to ground the design critique against the real codebase. This multi-lens analysis identifies flaws and gaps, ensuring objections are backed by concrete code evidence.