dx-agent-dev

Automate software implementation from requirements specs with self-checks and commits.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end software implementation from a structured requirements spec, enabling teams to translate stories and bug fixes into code, verify changes with automated checks, and commit with traceability.

Core Features & Use Cases

  • Reads requirements specs from .ai/run-context/re.json or .ai/specs/<id>-*/explain.md, creates a focused feature/bugfix branch, and implements the required changes.
  • Runs automated self-checks (compile, tests, lint) and commits results to keep an auditable record.
  • Enforces reuse of existing utilities and project conventions, and provides progress reports and retry guidance if failures occur.

Quick Start

Read the requirements spec, create a feature branch, implement the changes, run self-checks, and commit the results.

Frequently Asked Questions about dx-agent-dev

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

FAQPage Schema
How do I automate end-to-end software implementation from a requirements spec?

You can automate software implementation by reading structured requirements specs from .ai/run-context/re.json or .ai/specs/<id>-*/explain.md, creating a feature branch, and executing a multi-task workflow to generate code changes.

Can I automatically create a feature branch and commit code changes for bug fixes?

Yes, automated branch management creates a focused feature or bugfix branch from the requirements spec, implements required changes, runs self-checks, and commits results to maintain an auditable record.

How do automated self-checks work during code generation?

Automated self-checks run compile, tests, and lint processes after code changes to verify implementation, providing self-check results and retry guidance if failures occur before committing.

Do I need a structured requirements spec to automate code implementation?

Yes, you need a structured requirements spec located at .ai/run-context/re.json or .ai/specs/<id>-*/explain.md to enable the automated workflow to read, interpret, and implement the required software changes.

What is the best way to ensure code automation follows existing project conventions?

Code automation ensures adherence to project conventions by enforcing the reuse of existing utilities throughout the multi-task workflow, reporting progress while maintaining an audit trail of all changes.

Why does automated branch management require structured specs before implementation?

Automated branch management requires structured specs because the workflow reads the requirements to create a focused feature branch and execute the correct multi-task implementation across the repository without manual intervention.