Menu
Use when writing or updating an ADR for a specific technical decision.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | adr-writer |
| description | Use when writing or updating an ADR for a specific technical decision. |
Use this skill to create concise architecture decision records.
references/adr-templates.md; fall back to docs/foundation/adr-templates.md or templates/adr-template.md when installed.docs/adr/, use the next available ADR number.# ADR NNNN: Title
Date:
Status: Proposed | Accepted | Superseded
## Context
## Decision
## Consequences
- Positive:
- Negative:
- Follow-up:
## Revisit When
-
Do not invent certainty. Label assumptions and missing expert review.
Use when creating, reviewing, or restructuring AGENTS.md, CLAUDE.md, or scoped instruction files for a project, including root, feature, service, backend, or domain-level guidance.
Use when a new app plan already exists and needs an interactive kickoff into setup decisions and first tasks.
Use at task handoff, milestone review, or after implementation when project lessons may be reusable for future apps, toolkit docs, AGENTS/CLAUDE instructions, skills, or templates.
Use when a greenfield app needs a mature foundation plan before implementation.
Use when explicitly defining MVP scope, exclusions, beta screens, states, or success metrics.
Use when drafting pull request descriptions, end-of-session handoffs, reviewer notes, verification summaries, or stop-start task updates.