skills.rest
dcosson
dcossonCOMMUNITY
Explore all skills by this author →
GitHub

plan-review

Evaluate plan documents and test harnesses, producing severity-rated findings.

157|12|Updated Feb 2, 2026
Search Tags:#automation#documentation#governance#quality-assurance#plan-review#review-process
One-click install
npx skills add https://github.com/dcosson/h2 --skill plan-review-dcosson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-review
Source: https://github.com/dcosson/h2/tree/main/internal/config/templates/styles/opinionated/skills/plan-review
Command: npx skills add https://github.com/dcosson/h2 --skill plan-review-dcosson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Independently review a plan document and its test harness, producing a findings doc rated P0-P3 and enabling independent perspectives for plan governance.

Core Features & Use Cases

  • Independent plan-review workflow that reads docs/plans/$0.md and the optional docs/plans/$0-test-harness.md (if present) and emits a structured findings document.
  • Enforces a fixed evaluation rubric across correctness, completeness, consistency, acceptance criteria, connected components, testability, performance, security, URP/EO/AA, and scope justification.
  • Supports multiple reviewers (e.g., reviewer-1, reviewer-2) and outputs a review doc named docs/plans/$0-review-$1.md for traceability.

Quick Start

Execute a plan review on docs/plans/$0 and generate a findings document rated P0-P3.

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 plan document and generate structured findings?▼

To review a plan document, you can evaluate the plan file and its test harness for correctness, completeness, and security, then output a structured findings document with severity-rated P0-P3 issues.

What is an independent plan review process for software engineering governance?▼

An independent plan review process evaluates a plan document against a fixed rubric covering acceptance criteria, testability, and scope justification, producing a traceable findings document to enable governance.

How do I get multiple independent perspectives on a technical plan?▼

You can obtain multiple independent perspectives by running separate review instances that output individual findings documents named with reviewer identifiers, ensuring traceability for each reviewer.

Can I evaluate a test harness alongside a plan document for completeness?▼

Yes, you can evaluate a test harness alongside a plan document by targeting both the plan file and its optional test harness file, assessing acceptance criteria and testability within the same review workflow.

What severity ratings are used when reviewing a software plan?▼

Severity ratings from P0 to P3 are used to categorize issues found in a plan document, covering dimensions like correctness, consistency, performance, security, and scope justification.

Does plan review require any external dependencies to run?▼

No external dependencies are required to run the plan review process, as it independently reads plan and test harness files and outputs findings without relying on external components.

Related Skills

Explore More Software Engineering Skills→
dcossondcosson
157

plan-draft

Draft a component plan and test harness documentation.

Community
Advanced
hypeJunctionhypeJunction
1

review

Review current branch code against the base branch with severity ratings.

Community
Advanced
auerbachbauerbachb
3

check-acceptance-criteria

Verify acceptance-criteria checkboxes in GitHub pull requests against repository code.

Community
Advanced
ExuberantWitnessExuberantWitness
1

flux-verify-paper-plan

Validate JSON research paper plans via schema checks and LLM rubric evaluation.

Community
Intermediate