dx-plan-validate

Cross-check explain.md against implement.md to verify requirement coverage and detect scope creep.

6|3|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/easingthemes/dx-aem-flow --skill dx-plan-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dx-plan-validate
Source: https://github.com/easingthemes/dx-aem-flow/tree/main/plugins/dx-core/skills/dx-plan-validate
Command: npx skills add https://github.com/easingthemes/dx-aem-flow --skill dx-plan-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-checks the implementation plan (explain.md) against the requirements (implement.md) to ensure every requirement has at least one corresponding step and prevent scope creep.

Core Features & Use Cases

  • Requirement coverage verification: detects missing mappings between explain.md and implement.md.
  • Scope control: flags steps that do not map to any requirement.
  • Dependency validation: checks that steps respect the execution order and reference files when research.md exists.
  • Plan reuse: identifies opportunities to reuse existing utilities or patterns in the codebase.

Quick Start

Use /dx-plan-validate <id> to validate the most recent plan or a specified one and view a detailed report.

Frequently Asked Questions about dx-plan-validate

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

FAQPage Schema
How do I validate an implementation plan against software requirements?

To validate an implementation plan against software requirements, cross-check the plan to ensure every requirement has at least one corresponding step and identify discrepancies to prevent scope creep.

What is scope creep detection in requirement coverage verification?

Scope creep detection in requirement coverage verification is the process of flagging implementation steps that do not map to any defined requirement, ensuring the plan stays within the original project scope.

Can I check dependency execution order and referenced files in a plan?

Yes, you can check dependency execution order and referenced files by validating the plan against a research document, ensuring steps respect the execution sequence and correctly reference necessary files.

How do I identify plan reuse opportunities for existing codebase patterns?

To identify plan reuse opportunities, analyze the structured verdict of the plan validation to discover existing utilities or patterns in the codebase that can be reused for current implementation steps.

What does a structured plan validation verdict include?

A structured plan validation verdict includes the requirement coverage status, the execution ordering validity, and potential reuse opportunities found within the codebase.