Changelog from raw commit history
writingGroups commits into user-facing changes, without inventing anything that is not in the log.
Landing copy from a feature list
Turns what the product does into what it removes from the reader's day.
When to use it
You have the feature list and no headline.
The prompt
Copy into your assistant
Write landing page copy from the feature list below.
Constraints:
- Headline states the outcome, not the category. No "AI-powered platform".
- Subhead names who it is for and what it replaces.
- Three benefit blocks, each: a claim, one sentence of proof, and what the reader stops doing.
- One line that says who this is not for.
Rules:
- No superlatives, no exclamation marks, no words like seamless, revolutionise, or unlock.
- If a feature has no clear benefit, leave it out rather than inflating it.
- British or American spelling, pick one and stay consistent.
Features:
<features>
Audience:
<audience>What to change
The 'who this is not for' line converts best and is the one everyone skips — it signals confidence.
Why it works
Banning the specific words is more effective than 'be concise'. Models default to a vocabulary of empty intensifiers, and naming them removes the escape hatch.
More writing prompts
- Incident postmortem from a raw timelineTurns logs and a chat transcript into a blameless postmortem with contributing factors, not a culprit.
- Meeting transcript to decisions and ownersExtracts what was decided, what was merely discussed, and who owes what by when.
- Audit interface copy for clarityRewrites button labels, errors, and empty states so they say what happened and what to do.
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