plan-review

Validate executable plans against template contracts and user requests.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/SeoJaeWan/try-claude-code --skill plan-review-seojaewan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-review
Source: https://github.com/SeoJaeWan/try-claude-code/tree/main/.codex/skills/plan-review
Command: npx skills add https://github.com/SeoJaeWan/try-claude-code --skill plan-review-seojaewan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Validate executable plans against template contracts and user requests to prevent ambiguity and drift into execution.

Core Features & Use Cases

  • Template-compliance auditing to ensure plan.md matches the active contract.
  • Parity checks between plan.md and linked phase detail files for consistency.
  • One-hop prerequisite parity audit for local prerequisites to prevent misalignment.
  • Owner routing and scenario-level input/output contract validation to improve traceability.
  • Read-only review with a single writable artifact at plans/_orchestrator/review/{task-slug}/review.md.

Quick Start

Review the latest plan at ./plans/**/plan.md along with its linked phase details to produce an execution-readiness assessment.

Frequently Asked Questions about plan-review

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

FAQPage Schema
How do I validate executable plans against template contracts to prevent ambiguity?

Validating executable plans against template contracts requires auditing plan.md files for compliance and checking parity with linked phase detail files to prevent ambiguity before execution. This ensures architecture plans align with user requests and template requirements.

What is execution-readiness assessment for architecture plans?

Execution-readiness assessment is a cold, artifact-focused review that validates plan.md files and their linked phase details against template contracts. It performs parity checks and owner routing validation to ensure plans are fully prepared for materialization.

How do I check parity between plan.md and phase detail files?

Checking parity between plan.md and phase detail files involves auditing their consistency across the planning workflow. You enforce one-hop prerequisite parity for local prerequisites and validate scenario-level input and output contracts to improve traceability.

Does the plan review process modify the original architecture plans?

The plan review process does not modify original architecture plans. It enforces a strict read-only policy, generating a single writable review artifact at the designated orchestrator review path to ensure source plans remain untouched.

Can I use artifact-focused review for UI scope considerations in plan materialization?

Yes, artifact-focused review applies to UI scope considerations within the planning workflow. It validates scenario-level input and output contracts and checks plan-materialize readiness to ensure architecture plans are fully prepared for execution.