dx-plan

Generate a structured implement.md plan from explain.md and research.md.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams and engineers generate a structured implementation plan from explain.md and research.md, converting scattered requirements into a concrete, auditable rollout.

Core Features & Use Cases

  • Generate an implement.md from explain.md and research.md to capture steps, owners, and dependencies.
  • Ensure steps are ordered by dependency and start with a pending status for safe autonomous execution.
  • Integrate hub mode and cross-repo planning if the repository configuration enables it, and reference figma conventions or prototypes when present.
  • Adapt to prototype guidance and design references (if available) to align with project conventions.

Quick Start

Provide a work item ID to generate a complete, status-tracked implement.md from explain.md and research.md.

Frequently Asked Questions about dx-plan

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

FAQPage Schema
How do I generate an implementation plan from research and requirements documents?

To generate an implementation plan, you provide a work item ID so the system can consume your explain.md and research.md files to produce a concrete implement.md with ordered, pending-status steps.

What is the best way to track implementation status for autonomous execution steps?

Tracking implementation status is handled by assigning a pending status to all generated steps, ensuring safe autonomous execution and providing an auditable rollout for product teams and engineers.

How does cross-repo planning work when generating an implementation plan?

Cross-repo planning integrates automatically if your repository configuration enables hub mode, allowing the generated implementation plan to span multiple repositories and reference exact file changes.

Do I need exact file references and line numbers to create a structured rollout?

You need research.md to provide the context, and the planning tool ensures all generated steps reference exact files and line numbers from that research to create a concrete, auditable rollout.

Can I align generated implementation steps with Figma prototypes and design conventions?

You can align steps with design conventions because the planning process adapts to prototype guidance and references Figma prototypes when present, ensuring implementation matches project conventions.

Why are implementation steps ordered by dependency in the generated plan?

Implementation steps are ordered by dependency to ensure safe autonomous execution, preventing runtime errors by processing foundational file changes before subsequent tasks in the implement.md output.