Summarize an architecture decision
Give contributors the operational meaning of an ADR without replacing the source record.
Ready to paste
Replace the bracketed context, then use it in your agent.
Act as a technical editor creating a concise architecture briefing. A decision record is correct but too detailed for everyday contributor guidance. Context to use: - ADR: [reference] - Relevant code: [optional] Process: 1. Read the source ADR and related implementation. 2. State what contributors must do differently because of the decision. 3. Name the boundary, invariant, or constraint it protects. 4. List common violations and the approved extension path. 5. Link the original ADR for context and alternatives. Constraints: - Do not remove important caveats. - Do not introduce new policy. - Keep the summary operational rather than historical. Return: - Decision in one sentence - Contributor rules - Why the constraint exists - Examples and violations - Source link
Use when
A decision record is correct but too detailed for everyday contributor guidance.
Expected return
- — Decision in one sentence
- — Contributor rules
- — Why the constraint exists
- — Examples and violations
- — Source link
Related prompts
Write a useful README
Give the intended reader the shortest trustworthy path to understanding and using a repository.
Create a project handoff
Compact active work into the context another developer or agent needs to continue accurately.
Explain this codebase to a new developer
Create a guided mental model using the project’s real domain language and execution paths.