plan-review

Review PRDs and technical plans for clarity, completeness, specificity, and YAGNI.

22|2|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/tmchow/tmc-marketplace --skill plan-review-tmchow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-review
Source: https://github.com/tmchow/tmc-marketplace/tree/main/plugins/iterative-engineering/skills/plan-review
Command: npx skills add https://github.com/tmchow/tmc-marketplace --skill plan-review-tmchow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Planning and design documents often lack clarity, structure, or concrete next steps. This skill provides a systematic four-reviewer evaluation to surface issues early and guide improvements.

Core Features & Use Cases

  • Four-reviewer framework: clarity, completeness, specificity, and YAGNI checks the plan for readability, gaps, actionable detail, and scope creep.
  • Structured feedback: each reviewer returns their top 5 issues with line references and concrete suggestions.
  • Workflow integration: can be invoked standalone or embedded in brainstorming or tech-planning flows to ensure planning quality before execution.

Quick Start

Provide the planning document (PRD or tech plan) to review, and the four reviewers will return a structured, prioritized feedback report.

Frequently Asked Questions about plan-review

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

FAQPage Schema
How do I get structured feedback on a technical plan or PRD?

Structured feedback on technical plans and PRDs is generated using a four-reviewer framework evaluating clarity, completeness, specificity, and YAGNI. Each reviewer returns top 5 issues with line references and concrete suggestions, plus an integrated synthesis.

What does a YAGNI check evaluate in a planning document?

A YAGNI check in planning documents evaluates scope creep by identifying unnecessary features. It acts as one of four expert reviewers, returning prioritized issues with line references to ensure scope remains strictly aligned with immediate requirements.

Can I review a draft PRD or does the plan need to be final?

Draft PRDs and technical plans can be reviewed at any planning stage, from initial draft to final. The four-reviewer evaluation surfaces gaps and scope issues early, providing line references and concrete suggestions to guide improvements before execution.

How do I identify gaps and missing details in a product requirement document?

Gaps and missing details in product requirement documents are identified through a completeness review. This reviewer checks the PRD for actionable detail, returning the top 5 prioritized issues with line references and concrete suggestions to fill structural holes.

What is the best way to check a technical plan for clarity and scope creep?

Checking technical plans for clarity and scope creep requires a structured four-reviewer framework. It evaluates readability and YAGNI principles, returning an integrated synthesis of the top issues across all reviewers with line references and suggestions.

Does plan-review work with brainstorming or tech-planning workflows?

Plan-review can be invoked standalone or embedded in brainstorming and tech-planning workflows. This integration ensures planning quality and applies the four-reviewer evaluation to PRDs and technical plans before moving to execution.