plan-review

Review implementation plans for sizing, dependencies, and completeness.

20|Updated Oct 13, 2025
One-click install
npx skills add https://github.com/malhashemi/dotfiles --skill plan-review-malhashemi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-review
Source: https://github.com/malhashemi/dotfiles/tree/main/dot_config/opencode/skill/plan-review
Command: npx skills add https://github.com/malhashemi/dotfiles --skill plan-review-malhashemi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents wasted development effort by identifying and flagging oversized or incomplete implementation plans before any code is written.

Core Features & Use Cases

  • Phase Sizing Assessment: Evaluates file changes, new code, test additions, and estimated context for each phase.
  • Dependency Analysis: Verifies phase order, build dependencies, and checks for circular dependencies.
  • Completeness & Gap Analysis: Ensures phases have clear descriptions, success criteria, and addresses missing elements or edge cases.
  • Use Case: After a complex feature is planned, use this skill to ensure each implementation phase is manageable and logically sound, preventing scope creep and rework.

Quick Start

Use the plan-review skill to validate the implementation plan for the new user authentication module.

Frequently Asked Questions about plan-review

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

FAQPage Schema
How do I validate an implementation plan before coding begins?

To validate an implementation plan before coding, review its phases for sizing, dependencies, and completeness to identify phases requiring decomposition. This process analyzes file changes, new functions, test counts, and estimated context to prevent scope creep and rework.

What is implementation plan decomposition in software development?

Implementation plan decomposition is the process of breaking down oversized development phases into manageable parts. It evaluates file changes, new code, and test additions to ensure each phase has clear descriptions and success criteria before coding starts.

How do I check for missing dependencies in a software development plan?

To check for missing dependencies in a software development plan, analyze the phase order and verify build dependencies. This includes checking for circular dependencies and ensuring all necessary elements and error cases are addressed in the plan.

Why does my implementation plan fail gap analysis for edge cases?

Your implementation plan fails gap analysis when it lacks completeness checks for missing elements or edge cases. A thorough review ensures all phases have clear descriptions, success criteria, and addresses error cases to prevent wasted development effort.

Can I assess phase sizing using estimated context and test counts?

Yes, you can assess phase sizing by evaluating estimated context, file changes, new code, and test counts for each phase. This verifies that implementation phases remain manageable and logically sound before any code is written.