dx-req-import

Validate requirements documents and generate formal spec structures.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reads a standalone requirements document to validate its completeness and generate a formal spec structure.

Core Features & Use Cases

  • Reads external requirements documents (BA, Confluence, email) and validates them against a completeness rubric.
  • Generates explain.md (and optional research.md) and creates a ready-to-use spec directory at .ai/specs/<slug>.
  • Applies a gating threshold to decide whether to proceed or report gaps, then guides next steps.

Quick Start

Provide the path to your requirements document to start the validation and spec generation.

Frequently Asked Questions about dx-req-import

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

FAQPage Schema
How do I validate an external requirements document and generate a spec?

To validate an external requirements document, provide its file path. The tool reads it, applies a completeness rubric, and generates a formal spec directory containing explain.md and optional research.md.

Do I need an ADO ticket to generate a spec from a requirements document?

No, you do not need an ADO ticket to generate a spec. The process reads standalone external documents like emails or Confluence pages and creates the spec structure directly without requiring a ticket.

What happens if my requirements document fails the validation gating?

If your requirements document fails validation gating, the process reports the identified gaps instead of proceeding. It applies a rubric-based threshold to block incomplete documents and guide your next steps.

How does the spec generation process enrich the final output?

Spec generation enriches the output by performing lightweight research when references are present in the source document. This adds context to the generated explain.md and optional research.md files.

Can I use requirements from Confluence or email to generate a spec directory?

Yes, you can use requirements from Confluence, emails, or BA documents. The validator reads these external sources and creates a ready-to-use spec directory at .ai/specs/<slug>.

What files are created when generating a spec from external requirements?

Generating a spec from external requirements creates a directory at .ai/specs/<slug>. This directory contains a formal explain.md file and an optional research.md file for enriched context.