Docs ADR Writer

Use this skill when

• documenting an architectural decision
• recording migration rationale
• updating harness principles
• producing technical handoff notes

Goals

• preserve decision rationale
• support future continuation
• reflect actual implementation reality
• keep technical language precise

ADR structure

1. Title
2. Status
3. Context
4. Decision
5. Consequences
6. Alternatives considered
7. Open issues if any

Documentation rules

• explain why, not just what
• distinguish proposed from verified
• avoid vague claims
• record trade-offs honestly

Output contract

Return a complete document or section with clear headings and precise wording.