dx-agent-re

Extract work item goals and generate a requirements spec saved as re.json.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes an ADO or Jira User Story and outputs a structured requirements spec with a task breakdown for the Dev Agent, enabling faster and safer handoffs from planning to execution.

Core Features & Use Cases

  • Parse the input work item (ID or URL) to capture Title, Description, Acceptance Criteria, Type, State, and relationships.
  • Fetch parent/child context to enrich the requirements with project scope.
  • Research codebase context by locating relevant components, services, and tests to ground the spec.
  • Generate a comprehensive requirements spec (RE) and a detailed task breakdown, then save as re.json.
  • Present a summary and optionally post back to the work item and create child tasks after user confirmation.

Quick Start

Provide an ADO Work Item ID or Jira issue key to start the RE analysis and the agent will produce a structured requirements spec.

Frequently Asked Questions about dx-agent-re

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

FAQPage Schema
How do I break down a Jira user story into actionable development tasks?

To break down a Jira user story, this Skill parses the work item's title, description, and acceptance criteria, then analyzes your codebase context to map changes into a structured requirements specification saved as re.json.

Can I automatically generate child work items from an ADO user story?

Yes, you can generate child work items from an ADO user story. After producing a detailed task breakdown and requirements spec, the Skill prompts for confirmation before optionally posting a summary back to the work item and creating child tasks.

How do I analyze codebase context to map risks for a new feature?

Analyzing codebase context involves locating relevant components, patterns, tests, and utilities across involved repos. This grounds the user story requirements by mapping proposed changes to concrete development tasks and identifying potential risks.

What is the best way to create structured requirements for developer handoff?

The best way to create structured requirements for handoff is extracting project scope and acceptance criteria from parent and child work items, then generating a comprehensive RE specification with a detailed task breakdown for the Dev Agent.

Do I need to provide a work item URL to start requirements analysis?

You do not need a full URL; providing an ADO Work Item ID or Jira issue key is sufficient to start the requirements analysis and generate the structured specification.

How does the agent handle posting summaries back to Jira or ADO?

The agent handles posting summaries by presenting a confirmation prompt before taking action. After generating the requirements spec and task breakdown, it requires your explicit approval to optionally post the summary back to the work item and create child tasks.