Generate Adrs From Tech Spec.prompt

---
description: "Generate ADR draft files from a completed technical specification using the project's ADR capture and traceability rules."
name: "Generate ADR Drafts from Tech Spec"
argument-hint: "Path to completed tech spec"
agent: "agent"
---

Generate ADR drafts directly from the provided completed technical specification.

References:
- [ADR Capture from Tech Specs](../instructions/adr-capture-from-tech-spec.instructions.md)
- [Create Tech Spec Skill](../skills/create-tech-spec/SKILL.md)
- [Tech Spec Template](../skills/create-tech-spec/assets/tech-spec-template.md)

## Goal
Create ADR draft markdown files for major technical decisions in the tech spec.

## Scope
- Work from the completed tech spec as the source of truth.
- Capture major architecture decisions that materially affect design, operations, cost, compliance, or compatibility.
- Preserve traceability to source PRD requirements and tech spec sections.

## Generation Steps
1. Parse the tech spec and extract decision candidates from sections such as:
   - Proposed Architecture
   - Data Design
   - API and Integration Design
   - Non-Functional Design
   - Rollout and Migration Strategy
   - Alternatives Considered
2. Decide whether each candidate requires an ADR using the ADR rules.
3. Resolve ADR output directory using this priority:
   - Existing `docs/adr/`
   - Existing `docs/architecture/adr/`
   - Existing `tasks/adr/`
   - If none exist, create `docs/adr/`
4. For each qualifying decision, create file name:
   - `ADR-YYYY-MM-DD-<decision-slug>.md`
5. Draft each ADR with status `Proposed` unless the tech spec states another status.
6. Add traceability links:
   - Source tech spec path
   - Related PRD requirement IDs (`FR-*`, `NFR-*`) when available
   - Source section references from the tech spec
7. If a major decision does not warrant an ADR, record one explicit justification in a "Non-ADR Decisions" section of the response.

## ADR Draft Template
Use this structure for each generated file: