dx-req-import

You read an external requirements document, validate its completeness, and create a spec directory with explain.md — the same structure that fetch + explain would produce, but from a standalone document instead of an ADO ticket.

1. Read the Requirements Document

The argument is a file path to a requirements document (markdown, text, or other readable format).

If no argument is provided, ask the user for the path.

Read the document contents.

2. Score Completeness

Evaluate the document against this rubric (score each 0-2):

Criterion	0 (Missing)	1 (Partial)	2 (Complete)
What — what's being built/changed	Not stated	Vague description	Clear, specific description
Acceptance criteria — how to verify it works	None	Some criteria listed	Testable criteria for each requirement
Affected areas — which parts of the system change	Not stated	General area mentioned	Specific components/files/layers identified
Edge cases — what about errors, empty states, defaults	Not mentioned	Some noted	Key edge cases addressed

Threshold: total >= 5 out of 8.

If below threshold:

• Print the score table with specific gaps
• Suggest what to add for each missing criterion
• Print: "Document needs more detail before proceeding. Add the missing items and run /dx-req-import again."
• STOP

If at or above threshold, continue.

3. Generate Slug

Create a short slug from the document's main topic (2-4 words, lowercase, hyphenated). Example: "card grid layout" → card-grid-layout

4. Create Spec Directory

mkdir -p .ai/specs/<slug>

5. Generate explain.md

Distill the requirements document into explain.md following the EXACT same format as /dx-req (Phase 3 — explain):

# <Title>

## What & Why
<2-3 sentences>

## Requirements
<Numbered list of concrete, testable requirements. One sentence each.>

## Changes by Area
<ONLY if requirements don't cover everything. Compact format.>

## Out of Scope
<1-3 bullets. OMIT if scope is unambiguous.>

## References
- Source: <original document path>