This skill creates one or more ADR documents that — together with the PRD — give an AI development agent everything it needs to implement the feature or application without ambiguity. All technical decisions, reasoning, diagrams, data structures, and test plans are defined here so the implementing agent does not have to make architectural guesses.

Technical implementation details and testing strategy intentionally excluded from PRD belong here.

Process

Step 1 — Read the PRD (if it exists)

Check for docs/PRD.md. If found, read it fully before proceeding. If not found, ask the user to provide a description of the feature or application: what it does, who uses it, what the main flows are.

Step 2 — Ask clarifying questions (REQUIRED — minimum 5)

Ask the user at least five focused clarifying questions before writing any ADR. Do not start writing until you have answers. If the PRD, user, or codebase already answers a topic, ask a deeper question about another decision instead of repeating it. Relevant topics include:

write-adr

Process

Step 1 — Read the PRD (if it exists)

Step 2 — Ask clarifying questions (REQUIRED — minimum 5)