dx-req

Fetch ADO or Jira work items, validate DoR, and generate a structured requirements plan.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

dx-req automates the full lifecycle from ticket intake to a structured, governance-ready requirements plan. It fetches ADO/Jira stories, validates DoR readiness, distills requirements, and orchestrates codebase research to produce a repeatable workflow that reduces handoffs and rework.

Core Features & Use Cases

  • Fetches ADO/Jira work items and validates their DoR, then distills requirements for the team.
  • Researches the codebase to surface context, patterns, and existing implementations to accelerate delivery.
  • Generates and writes phase artifacts (raw-story, dor-report, explain, research, share-plan) to drive implementation and governance.

Quick Start

Invoke /dx-req with a work item ID to start the end-to-end pipeline and generate all phase artifacts.

Frequently Asked Questions about dx-req

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

FAQPage Schema
How do I automate Jira or ADO requirements gathering and Definition of Ready validation?

Automating Jira or ADO requirements gathering and DoR validation involves fetching work items, checking their readiness, and distilling them into a structured plan. This pipeline replaces sequential steps with a unified workflow to reduce manual handoffs and rework.

What is the best way to research the codebase for context when starting a new Jira ticket?

Codebase research for a new Jira ticket is best handled by an automated requirements pipeline that orchestrates context discovery, identifies existing patterns, and surfaces relevant implementations to accelerate delivery.

How does a Definition of Ready report work when validating Jira or ADO work items?

A Definition of Ready report for Jira or ADO work items works by fetching the ticket, validating its readiness against established criteria, and generating a phase artifact that drives implementation and governance.

Can I generate a structured requirements plan directly from an ADO work item ID?

Yes, you can generate a structured requirements plan directly from an ADO work item ID by invoking the pipeline, which fetches the story, validates its DoR, researches the codebase, and outputs phase artifacts for raw-story, explain, research, and share-plan.

Does this requirements pipeline require any additional dependencies to function?

No, this requirements pipeline requires no additional dependencies to function. It operates independently to fetch ADO or Jira stories, validate DoR, and distill tickets into a structured plan without external component requirements.