Record technical decisions with AI
Capture what a team decided, the alternatives it weighed and the consequences it accepted. A small choice can stay in a dated log rather than growing into a full record.
Record technical decisions with AI when a short discussion has settled something that future maintainers will need to understand. A team might choose to generate a report overnight because the buyer sees it only each morning. Give recording-decisions the actual discussion so that this constraint survives beyond the chat history.
A decision record can also preserve an objection that nobody resolved. Readers can then see which assumption to revisit if the report becomes customer-facing or its timing changes. Smaller choices can live in a dated decision log.
What it does
- Write one architecture decision record for one consequential choice.
- Note which alternatives the team considered and why it declined them.
- Keep unresolved objections beside the choice that was actually made.
- Keep a short dated entry for a smaller trade-off.
- Link a replacement decision back to its predecessor.
Install and use
- Install the maker’s technical-writer bundle in your agent with its shared writing rules.
- Provide the choice, the date and an authorised record of the discussion.
- Ask, “Write up our decision to use overnight exports. Preserve the objection about late orders and flag anything the meeting did not settle.”
- Have the decision-makers check the record before treating it as accepted.
FAQ
Source
Made by riekelt. Original skill: recording-decisions, published on GitHub under the MIT licence.
View on GitHub