df-plan-review

Review implementation plans for internal consistency, factual accuracy, and goal coverage before execution.

3|1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/wopal-cn/wopal-space-ontology --skill df-plan-review-wopal-cn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: df-plan-review
Source: https://github.com/wopal-cn/wopal-space-ontology/tree/main/skills/df-plan-review
Command: npx skills add https://github.com/wopal-cn/wopal-space-ontology --skill df-plan-review-wopal-cn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Plans that pass automated format checks can still fail in execution: symbols nobody creates, stale file paths, unowned acceptance criteria, or goals with no covering task. This Skill performs a correctness review of a Plan before execution, catching defects that regex-based form validators cannot detect. ## Core Features & Use Cases - Three-question review model: Q1 checks whether plan parts fit together (symbol producers, AC ownership, dependency order), Q2 verifies every factual claim against the repository at a stated revision, Q3 confirms the plan actually delivers the stated goal without silent scope shrinkage. - Structured verdicts and reports: Produces PASS, REVISE, or BLOCK verdicts with severity-calibrated findings (Blocker, Warning, Info, Unverified), each citing both the plan location and the contradicting reality. - Use Case: Before approving a risky migration or cross-module refactoring plan, ask for a plan review to catch a task that references an error code no task registers, or a premise about the codebase that is no longer true. ## Quick Start Ask the agent to review the plan at a given path before execution, for example: review this implementation plan and tell me whether it will work if followed literally.

Frequently Asked Questions about df-plan-review

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

FAQPage Schema
How do I review an implementation plan before executing it?

Invoke this review with the plan path and workspace root. It reads the plan once, builds lists of facts, symbols, and files, then verifies claims against the repository and returns a PASS, REVISE, or BLOCK verdict with cited findings.

What does a plan correctness review check that automated validation misses?

It checks whether symbols used by tasks have producers, whether acceptance criteria have owners, whether claims about the codebase are true at a stated revision, and whether executing the plan delivers the stated goal. Form checks like field presence are left to automated validators.

When should I use plan review versus code review?

Use plan review before execution starts, to validate that a written plan will work if followed literally. Use code review after implementation to inspect the actual changes. This skill explicitly excludes reviewing code and writing plans.

Does plan review work with git worktrees?

Yes. When a plan declares a worktree, the review reads status and probes code at the worktree's HEAD rather than the integration branch, and every finding states the revision it was verified against.

What are the limitations of automated plan review?

Claims that cannot be settled from the workspace are marked Unverified and never become findings. The review is limited to two rounds per plan, does not authorize plan approval or edits, and does not judge product intent or design taste.