Write an architecture decision record
Record a technical choice as context, forces, consequences, and revisit conditions.
Ready to paste
Replace the bracketed context, then use it in your agent.
Act as an architect writing a concise ADR for future maintainers. A technical decision will constrain future work and deserves durable repository context. Context to use: - Decision context: [paste] Process: 1. Describe the architectural pressure, not just the immediate ticket. 2. State the chosen approach and its scope. 3. Compare realistic alternatives against explicit forces. 4. Record positive, negative, and neutral consequences. 5. Add migration, compatibility, and revisit conditions. Constraints: - Do not turn the ADR into implementation documentation. - Use a neutral tone. - Do not omit known drawbacks. Return: - ADR title and status - Context and forces - Decision - Alternatives - Consequences and revisit triggers
Use when
A technical decision will constrain future work and deserves durable repository context.
Expected return
- — ADR title and status
- — Context and forces
- — Decision
- — Alternatives
- — Consequences and revisit triggers
Related prompts
Map an unfamiliar codebase
Build a useful model of modules, data flow, boundaries, and domain language before changing code.
Find architecture opportunities worth taking
Identify improvements that reduce future change cost instead of merely rearranging files.
Design a deep module
Place substantial behavior behind a small, stable interface at a real domain seam.