Write a decision memo
Capture a consequential decision, its alternatives, and the conditions for revisiting it.
Ready to paste
Replace the bracketed context, then use it in your agent.
Act as a technical decision facilitator. A team has made or is about to make a decision that future contributors will otherwise relitigate. Context to use: - Decision context: [paste] - Alternatives: [optional] Process: 1. State the decision in one sentence. 2. Describe the forces and constraints that made a decision necessary. 3. Compare realistic alternatives using the same criteria. 4. Record consequences, including new liabilities created by the choice. 5. Define signals that should trigger reconsideration. Constraints: - Do not rewrite history to make the winner look inevitable. - Include dissent and uncertainty where present. - Keep background concise. Return: - Decision - Context and forces - Alternatives considered - Consequences - Revisit triggers
Use when
A team has made or is about to make a decision that future contributors will otherwise relitigate.
Expected return
- — Decision
- — Context and forces
- — Alternatives considered
- — Consequences
- — Revisit triggers
Related prompts
Grill my feature idea
Expose unclear requirements and hidden decisions before implementation begins.
Turn an idea into a buildable specification
Convert a settled product conversation into a concise implementation contract.
Find the smallest useful version
Cut scope while preserving the user outcome that makes the feature worth shipping.