write-decision-rationale

Writes lightweight decision records with options, risk-reward labels, and reopening triggers.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/dineshrevunuru/SuperSkills --skill write-decision-rationale-dineshrevunuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-decision-rationale
Source: https://github.com/dineshrevunuru/SuperSkills/tree/main/write-decision-rationale
Command: npx skills add https://github.com/dineshrevunuru/SuperSkills --skill write-decision-rationale-dineshrevunuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Decisions made in one session are forgotten by the next, leaving future collaborators (or your future self) unable to reconstruct what was chosen, what was rejected, and under what conditions the choice should be reopened. This Skill captures a decision in about two minutes as a structured record with options, reasoning, and explicit reopening triggers. ## Core Features & Use Cases - Structured decision records: Produces a Markdown record with 2-3 options, each labeled with pros/cons, realistic time estimates, and a risk-reward quadrant, plus a chosen path with milestone-anchored reasoning. - Mandatory What-Would-Change-This section: Every record lists 2-4 observable trigger-to-action conditions that define when the decision should be revisited. - Status lifecycle management: Tracks records through Awaiting decision, Decided, Revisiting, and Superseded states so old decisions are updated rather than silently rewritten or deleted. - Use Case: After choosing between two voice engine architectures for a demo, generate a dated decision record that documents the rejected option's real strengths, the reasoning behind the choice, and the exact conditions (e.g., a new eval result) that would reopen it. ## Quick Start Write a decision record for the choice we just made between option A and option B, including the rejected option's tradeoffs and what would change this decision.

Frequently Asked Questions about write-decision-rationale

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a decision record or ADR quickly?

Use a lightweight template with a short title, 1-2 sentences of context, 2-3 options each with pros, cons, time estimates, and a risk-reward label, then a chosen path with specific reasoning. The whole record should take about two minutes, not twenty.

When should I document a decision versus skip it?

Document a decision only when a real alternative was seriously considered and rejected, and the choice affects timeline, quality, scope, or money. Skip records for choices with no real alternative or trivially reversible decisions, since the record costs more than the decision.

What is a What-Would-Change-This section in a decision record?

It is a mandatory list of 2-4 reopening conditions, each written as an observable trigger paired with an action, such as a new evaluation result that would reopen the choice. Vague lines like 'if circumstances change' are invalid because they are not observable or actionable.

How do I update an old decision record when assumptions expire?

Never edit a Decided record's choice in place. Flip its status to Revisiting, re-run the options and reasoning analysis, then either re-confirm the original with a date note or write a successor record and mark the old one Superseded with a link.

What is the difference between a decision record and a problem statement?

A problem statement frames the problem before any solution options exist, while a decision record starts only once a choice between solution paths exists. Deciding whether a problem is worth solving at all belongs to opportunity sizing, not decision documentation.