dx-plan-resolve

Resolve plan validation risks by researching codebase patterns and updating implement.md with fixes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan validation often surfaces risks and blocked steps that halt progress. dx-plan-resolve automates the risk-resolution workflow by researching the repository for concrete fixes and updating the implement.md with precise instructions.

Core Features & Use Cases

  • Locate the Spec Directory and read core spec files (implement.md, research.md, explain.md) to surface actionable issues.
  • Identify Risks and Blocked Steps in implement.md and transform vague items into concrete tasks.
  • Research and propose concrete solutions by pattern-matching the codebase and existing patterns, then document exact changes.
  • Update implement.md with concrete fixes, including file paths, suggested changes, and verification steps; add new steps if necessary to mitigate risks.
  • Produce a concise execution summary for the next validation and plan execution.

Quick Start

Run /dx-plan-validate to surface risks, then run /dx-plan-resolve with the plan ID to enact concrete fixes.

Frequently Asked Questions about dx-plan-resolve

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

FAQPage Schema
How do I resolve plan validation risks and blocked steps in my codebase?

To resolve plan validation risks, run the plan resolution workflow after validation to research the codebase for concrete solutions and update implement.md with specific file paths, code changes, and verification steps.

What is the best way to turn vague plan validation warnings into concrete implementation tasks?

Turning vague plan validation warnings into concrete tasks involves analyzing spec files like implement.md, research.md, and explain.md, pattern-matching the codebase, and documenting exact code changes to close each risk.

How do I update implement.md with concrete fix instructions after finding codebase risks?

You update implement.md by researching existing codebase patterns for actionable solutions, then appending precise fix instructions including specific file paths, suggested code changes, and verification steps to mitigate the identified risks.

When do I need to run plan resolution after validating my project implementation spec?

You need to run plan resolution immediately after plan validation reports warnings or risks, ensuring you pass the plan ID so the workflow can locate the spec directory and automatically enact concrete fixes.

Does the plan resolution workflow require specific spec files to function properly?

Yes, the plan resolution workflow requires core spec files including implement.md, research.md, and explain.md within the spec directory to surface actionable issues and produce a concise execution summary for the next validation.