skill-plan-document-reviewer

Reviews specifications and implementation plans for correctness and execution readiness before approval.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/longdang193/project-OS-starter --skill skill-plan-document-reviewer-longdang193
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-plan-document-reviewer
Source: https://github.com/longdang193/project-OS-starter/tree/main/generated_agents/claude/skills/skill-plan-document-reviewer
Command: npx skills add https://github.com/longdang193/project-OS-starter --skill skill-plan-document-reviewer-longdang193

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Flawed specifications and implementation plans create hidden risk when other sessions, agents, or teams execute them. This Skill catches incorrect, contradictory, underspecified, unprovable, or execution-unsafe proposals before approval, handoff, or costly execution. ## Core Features & Use Cases - Evidence-Based Review: Verifies material claims against actual repository state, checking that named files, symbols, commands, and scripts exist. - Severity-Classified Findings: Classifies issues as P1 (blocks approval), P2 (material weakness), or P3 (optional improvement) with root-cause grouping. - Readiness Verdicts: Produces one explicit verdict: not ready, ready with required fixes, or implementation-ready. - Use Case: Before handing an implementation plan to a separate execution agent, run this review to confirm every task names concrete owners, dependencies, edits, and task-local proof, and that a fresh controller can recover state from the plan plus Git alone. ## Quick Start Review the attached implementation plan for correctness and execution readiness before I hand it off to another agent.

Frequently Asked Questions about skill-plan-document-reviewer

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

FAQPage Schema
How do I review an implementation plan before execution?▼

Plan review verifies material claims against repository state, checks task order, dependencies, ownership, and task-local proof, then classifies findings by severity. The output is a readiness verdict: not ready, ready with required fixes, or implementation-ready.

What should a specification review check before approval?▼

A specification review checks goal and scope clarity, contract and identity definitions, consistency across requirements and acceptance criteria, ownership boundaries, validation quality, and unnecessary complexity. Findings are grouped by root cause rather than repeated across sections.

When should I skip a formal plan document review?▼

Skip the review for tiny, local, reversible tasks with settled behavior and obvious proof. The review cost is justified when work is cross-cutting, operational, data-sensitive, or expensive to reverse.

Does plan review rewrite or fix the document it reviews?▼

No, the review identifies readiness defects and proposes the smallest safe correction for each finding without silently rewriting the artifact. It does not author replacement documents, implement code, or claim behavior passes before execution.

What is the difference between plan review and code review?▼

Plan review evaluates proposed specifications and implementation plans before execution, while code review evaluates implementation diffs after changes exist. This Skill reviews proposed documents only and does not assess returned code review findings.