version: "1.0.0" name: create-adr description: > Synthesize viable investigations into a concise proposed ADR. Use when user says "create ADR for {feature-name}". Reads all investigations, identifies viable ones, generates ADR with Context/Options/Decision/Consequences sections.

Create ADR from Investigations

Synthesize viable investigations into a concise proposed ADR.

Usage: When user says "create ADR for {feature-name}"

Instructions

1. Generate ADR number: Use format {YYMM} based on current date (e.g., 2512 for Dec 2025)

1. Create ADR at docs/arch/adr-{YYMM}-{topic}.md:

# ADR-{YYMM}: {Title}
 
**Status**: Proposed
**Date**: {YYYY-MM-DD}
**Feature**: {feature-name}
 
## Context
{1-2 paragraphs: The problem from _feature.md, key constraints}
 
## Options Considered
 
1.**{Approach A}** - {one line summary} *(rejected: brief reason)*
2.**{Approach B}** - {one line summary} *(viable)*
3.**{Approach C}** - {one line summary} *(viable)*
 
## Decision
 
{1-2 paragraphs: What approach we chose and why. Reference the winning investigation(s).}
 
## Consequences
 
-{Impact on codebase}
-{What becomes easier}
-{What becomes harder or needs follow-up}

1. Keep it concise: No code snippets, no implementation checklists, no phase tracking. Just the decision and rationale.

1. Output: Show the ADR content and confirm next steps (implement, then accept ADR)

ADR Principles

• Context: Why we needed to decide (not how we'll implement)
• Decision: What we chose and why (not the full investigation details)
• Consequences: What changes as a result (both positive and negative)