Changelog from raw commit history
writingGroups commits into user-facing changes, without inventing anything that is not in the log.
Meeting transcript to decisions and owners
Extracts what was decided, what was merely discussed, and who owes what by when.
When to use it
Right after a call where things were agreed verbally and nobody wrote it down.
The prompt
Copy into your assistant
Turn this transcript into a decision record.
Produce exactly three sections:
1. Decided — one line per decision, with the person who owns it.
2. Open — questions raised that nobody answered.
3. Discussed but not decided — topics that sounded decided but were not.
Rules:
- Quote the sentence for every item you place in section 1. If you cannot quote it, it is not a decision.
- Do not summarise the whole meeting.
- If nothing was decided, write "no decisions" and list the open questions.
- No names in section 3.
Transcript:
<transcript>What to change
The quoting rule is the whole prompt. Without it, politeness in meetings gets promoted to agreement.
Why it works
Section 3 is what people actually need: the topics everyone left thinking were settled. Requiring a quote for section 1 is the cheapest way to tell a decision from a discussion.
More writing prompts
- Audit interface copy for clarityRewrites button labels, errors, and empty states so they say what happened and what to do.
- An email that says no, without burning the bridgeDeclines a request clearly, names the constraint, and offers a smaller yes.
- Changelog from raw commit historyGroups commits into user-facing changes, without inventing anything that is not in the log.
Going deeper
- Prompts that survive contact with realityUsing agents · Level 2
- Writing a skill that changes behaviorSkills and prompts · Level 2
- The last hour before launchRunning agents in production · Level 3