skills.rest
vatsal2210
vatsal2210COMMUNITY
Explore all skills by this author →
Websiteđť•Ź@vatsal_n_shahGitHub

plan-review

Review plan documents for gaps, risks, and missing edge cases.

Updated Apr 12, 2026
Search Tags:#codebase#review#plan#software#gap-analysis#go-no-go
One-click install
npx skills add https://github.com/vatsal2210/claude-skills --skill plan-review-vatsal2210
Or copy as Structured Prompt for Agentâ–Ľ
Please help me install this Agent Skill.
Skill: plan-review
Source: https://github.com/vatsal2210/claude-skills/tree/main/plan-review
Command: npx skills add https://github.com/vatsal2210/claude-skills --skill plan-review-vatsal2210

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It catches missing requirements, risks, and incomplete edge cases in a project plan before any code is written, preventing downstream bugs and wasted effort.

Core Features & Use Cases

  • Classification of plan type to apply the appropriate review checklist.
  • Four‑phase review process (read, codebase cross‑reference, gap checklist, structured report).
  • Produces a detailed blocker, priority gaps, questions, and a go/no‑go verdict for plans shared via paste, file path, or generated by the write‑plan skill.

Quick Start

Ask the plan‑review skill to evaluate my project plan and return a go/no‑go verdict.

Frequently Asked Questions about plan-review

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

FAQPage Schema
How do I review a software project plan for missing requirements before implementation?â–Ľ

Reviewing a software project plan requires cross-referencing the plan against the codebase to identify gaps, classify the plan type, and apply a structured checklist to catch missing requirements and edge cases before coding begins.

What is the best way to perform a go/no-go gap analysis on a project plan?â–Ľ

A go/no-go gap analysis evaluates a project plan through a four-phase process: reading the plan, cross-referencing the codebase, applying a gap checklist, and producing a structured report with blockers and a final go/no-go verdict.

How do I identify edge cases and risks in a software development plan?â–Ľ

Identifying edge cases and risks involves applying a structured review checklist to the plan document, cross-referencing existing codebase structures, and classifying the plan type to ensure all potential downstream bugs are caught.

Can I review a pasted plan document or do I need to provide a file path?â–Ľ

You can review a plan document shared via pasted text, a file path, or generated by a planning skill, and the review process will classify the plan type and return a structured gap analysis report.

When should I conduct a plan review and gap analysis in the software lifecycle?â–Ľ

A plan review and gap analysis should be conducted before implementation starts to catch missing requirements, risks, and incomplete edge cases, preventing downstream bugs and wasted development effort.

Does the plan review process classify different types of software plans?â–Ľ

Yes, the plan review process classifies the plan type to apply the appropriate review checklist, ensuring the gap analysis accurately targets the specific structural and functional requirements of the software plan.

Related Skills

Explore More Software Engineering Skills→
jjub0217jjub0217

study-roadmap

Analyze job postings and resumes to generate gap analysis and dual study roadmaps.

Community
Intermediate
ozan-fnozan-fn

golang-troubleshooting

Debug Go applications to resolve bugs, crashes, deadlocks, and unexpected behavior.

Community
Advanced
thecomputer07thecomputer07

qsd-map-codebase

Generate seven structured codebase documents under .planning/codebase/ using four parallel mapper agents.

Community
Intermediate
dieguscldieguscl

go-test-analysis

Analyze Go module test coverage and suggest missing test cases.

Community
Advanced