review-plan

Audit implementation plans for gaps across six review categories.

5|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/tomzx/agents --skill review-plan-tomzx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-plan
Source: https://github.com/tomzx/agents/tree/main/skills/review-plan
Command: npx skills add https://github.com/tomzx/agents --skill review-plan-tomzx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill audits an implementation plan to detect gaps in completeness, feasibility, dependencies, risk coverage, timeline realism, and reversibility, enabling teams to raise quality earlier in the SDLC.

Core Features & Use Cases

  • Completeness checks: verifies that the plan covers required artifacts (plan.md, specification.md if available) and aligns with the SDLC context.
  • Risk and feasibility assessment: evaluates effort estimates, constraints, mitigating strategies, and provides actionable recommendations.
  • Governance and traceability: produces a structured review with status updates, questions for clarification, and the ability to formalize assumptions.

Quick Start

Review the implementation plan at the provided path and report findings across completeness, feasibility, dependencies, risk coverage, timeline realism, and reversibility.

Frequently Asked Questions about review-plan

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

FAQPage Schema
How do I audit a software implementation plan for completeness and risk?

Auditing a software implementation plan involves checking it across six categories: completeness, feasibility, dependencies, risk coverage, timeline realism, and reversibility to identify gaps. It compiles issues to raise quality earlier in the SDLC.

What is timeline realism in an SDLC implementation plan?

Timeline realism evaluates whether the effort estimates and deadlines in an implementation plan are achievable. It checks constraints and mitigating strategies to ensure the schedule aligns with available resources and technical feasibility.

How do I review dependencies and feasibility for a software feature plan?

Reviewing dependencies and feasibility requires evaluating the plan's effort estimates, constraints, and mitigating strategies. This assessment verifies required artifacts are covered and provides actionable recommendations for risk mitigation.

Can I review a plan if my specification.md file is missing?

Yes, you can review a plan if specification.md is missing. The audit applies to plans defined in plan.md or provided in context, using the optional specification.md file only to enhance completeness checks when available.

How do I formalize assumptions and unresolved questions during a plan review?

During a plan review, unresolved questions are appended to questions.md and formal assumptions are created as needed. This governance process produces a structured review with status updates and traceability for clarification.

What are the limitations of automated risk coverage checks for implementation plans?

Automated risk coverage checks are limited to evaluating effort estimates, constraints, and mitigating strategies documented in the plan. They cannot predict unforeseen external blockers and rely on the accuracy of the provided implementation details.