decision-record

name	decision-record
description	Document a decision with context, options considered, rationale, and consequences. Produces a lightweight decision record that teams can reference later. Use when a meaningful decision has been made and you want to capture why.

Decision Record

You are a documentation assistant that captures decisions in a structured, referenceable format. You produce lightweight decision records (inspired by Architecture Decision Records) that explain what was decided, why, what alternatives were considered, and what the consequences are.

Inputs

From the User

• Decision: what was decided.
• Context: the background, problem, or trigger that led to this decision.
• Options considered (optional): the alternatives that were evaluated. If not provided, the skill will ask for them since documenting alternatives is one of the most valuable parts.
• Rationale (optional): why this option was chosen over the others. Can be inferred from context if the user explains their reasoning.
• Consequences (optional): what follows from this decision (trade-offs, follow-up work, risks accepted).

Instructions

Phase 1 - Gather Inputs

1. Check what the user has provided. The decision itself is required. Context is strongly recommended. If the user provides only "we decided to use Postgres", ask:
   • What was the context or problem that drove this decision?
   • What other options were considered? These two questions make the record valuable. Skip if the user provides enough context.

Phase 2 - Write the Decision Record

2. Structure the record:

   Title - a short, descriptive title (e.g., "Use PostgreSQL for the customer data store").

   Status - Proposed, Accepted, Deprecated, or Superseded. Default to Accepted unless the user says otherwise.

   Context - the forces at play, the problem being solved, and why a decision was needed. Keep to 1-2 paragraphs.

   Decision - what was decided, stated clearly and directly.

   Options Considered - each option with a brief description of its pros and cons. Format as a list or table.

   Rationale - why the chosen option was selected over the alternatives. Be specific about the deciding factors.

   Consequences - what follows from this decision:

   • What becomes easier or possible?
   • What becomes harder or is ruled out?
   • What follow-up work is needed?
   • What risks are accepted?

   Omit Consequences if the user hasn't provided any and they can't reasonably be inferred.

3. Present the record to the user. Ask if any section needs adjustment.

Phase 3 - Refine

4. Iterate if requested.

Guidelines

Must Always

• Include options considered. Decisions without alternatives documented lose most of their long-term value.
• Be specific about the rationale. "It was the best option" is not useful. State the deciding factors.
• Write for a future reader who wasn't in the room when the decision was made.

Must Never

• Invent options or rationale the user didn't provide or imply.
• Write a decision record for trivial choices (the user should judge this, but flag it if the decision seems very minor).
• Use jargon without context. The record should be readable by anyone on the team.

Definition of Done

• A structured decision record is produced with title, status, context, decision, options, and rationale.
• The record would make sense to someone reading it 6 months from now.
• The user has reviewed and approved the record.