plan-review

Evaluate implementation plans for citation quality, completeness, and actionability.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/dmooney/Rundale --skill plan-review-dmooney
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-review
Source: https://github.com/dmooney/Rundale/tree/main/.opencode/skills/plan-review
Command: npx skills add https://github.com/dmooney/Rundale --skill plan-review-dmooney

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan-review helps teams avoid execution failures by systematically checking whether an implementation plan has solid sourcing, covers necessary details, and translates into clear next steps.

Core Features & Use Cases

  • Citation Quality Checks: Verifies decisions are backed by references using the expected ref:delegation-id format and flags unsubstantiated claims.
  • Completeness Verification: Confirms goals are specific, phases are logically sequenced, edge cases and failure modes are addressed, and key rationale is documented.
  • Actionability Assessment: Ensures tasks clearly state what to change (files/components), dependencies are ordered, and developers can start without ambiguity.

Use cases: reviewing implementation plans before execution, auditing plan quality after creation, and validating that plans meet internal documentation standards.

Quick Start

Load the plan-review skill when reviewing an implementation plan document to produce an APPROVE, REQUEST_CHANGES, or NEEDS_DISCUSSION decision with a severity-tagged issue list.

Frequently Asked Questions about plan-review

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

FAQPage Schema
How do I review an implementation plan for completeness and actionability?

Plan review systematically checks implementation plans for citation quality, completeness, and actionability, producing an APPROVE, REQUEST_CHANGES, or NEEDS_DISCUSSION decision with a severity-tagged issue list.

What is the expected format for citations in software documentation plans?

Citations in software documentation plans must use the verifiable `ref:delegation-id` format to back decisions, ensuring that claims are substantiated and traceable during plan audits before execution.

Can I use this to audit plan quality after creation?

Yes, you can audit plan quality after creation to validate that documentation meets internal standards, confirming that tasks clearly state what files or components to change and that dependencies are logically ordered.

How do I validate that implementation tasks are specific enough for developers?

Actionability assessment validates task-level specificity by ensuring the plan clearly states what files or components to change, addresses failure modes, and sequences dependencies so developers can start immediately.

Does this plan review process check for edge cases and failure modes?

Completeness verification confirms that edge cases and failure modes are addressed, goals are specific, phases are logically sequenced, and key rationale is documented to prevent execution failures.