Release notes and the email to users
A list of commits becomes a readable changelog and an email people finish reading.
Treść promptu
Turn a list of changes into release notes and an email to users. Changes: {paste a list of commits, tickets or your own notes} Product: {what it does} Who reads it: {technical users / general users} Any breaking changes: {yes, which / no} What the user must do: {nothing / update settings / migrate} Do this: 1. Release notes grouped into "new", "improved", "fixed". Every item in the language of benefit, not of code. 2. Breaking changes as a separate block at the top, with the exact date and instructions. 3. The email: subject, first line, three paragraphs, one button. About the single biggest change; the rest as a link. 4. A short social post about the most noticeable item. 5. What on the list users don't need to hear about at all — and why. 6. A tone check: cut "we've been working hard" and "we're excited to announce", keep what people can now do. Rule: never write "fixed bugs" without saying which — be specific or don't mention it.
To, co w nawiasach klamrowych, zamieniasz na swoje.
Przykładowy wynik
Improved: the annual report builds in 4 seconds instead of 40 — on large projects it used to time out entirely. Don't mention: dependency upgrades and the logging migration. They give the user nothing and dilute the email.
Podobne prompty
Your idea broken down into risks plus a one-week test plan — before you spend months.
You are a product strategist who has seen plenty of projects die. Assess my SaaS idea honestly, without cheering me on. Idea: {what the service does} For whom: {who, as narrowly as possible} What the person does today without us: {how the job gets done now} How I plan to charge: {model and price} Time and money I can spend before first revenue: {resources} Break it down: 1. The problem: does it hurt regularly, or is it a one-off inconvenience? Answer plainly. 2. Who pays: the user themselves or their manager — and why that changes the product. 3. The three main risks: why this could fail. For each — the cheapest way to test it. 4. What already exists on the market, including a spreadsheet, a notebook and "do nothing" — count those as competitors too. 5. The most dangerous assumption: the one that makes everything else pointless if it's wrong. 6. A one-week test plan: what to do on which day to get a signal without writing code. 7. The kill criterion: what result means the idea should be dropped. If the idea is weak, say so in the first paragraph.
Pokaż przykładowy wynikUkryj przykład
Most dangerous assumption: that the bookkeeper is allowed to change tools. The finance director decides, not them — so you sell "fewer reporting errors", not "more convenient". Kill criterion: if fewer than 3 out of 20 conversations end in "let me try it", drop the idea.
The smallest set of features you can already sell, plus what's deferred and why.
Help me draw the boundary of an MVP that can actually be shipped and sold. Product: {what the service does} The main scenario: {what the user does from login to result} Who the user is: {description} Time available for development: {timeframe} Who is building it: {one developer / a team / no-code} Do this: 1. One user path from sign-up to first value — step by step, no branches. 2. The features without which that path doesn't work. Each with a reason why it can't be dropped. 3. Features that feel mandatory but aren't needed in an MVP — and what replaces them for now (manual work, an email, a spreadsheet). 4. What to cut entirely, and why it won't stop you selling. 5. The boundaries: what the product does NOT do. Wordings for the site so nobody expects otherwise. 6. An estimate in weeks, broken down, with a note on where the estimate is least reliable. 7. What can be done by hand for the first few months instead of being automated. Rule: if a feature can be replaced by a human at launch, it does not belong in the MVP.
Pokaż przykładowy wynikUkryj przykład
Do it by hand: PDF export is done by support on request for the first months. Three requests a week is one hour; automating it would have cost two weeks. Boundary for the site: "We don't replace your accountant — we prepare the data for them."
A feature turned into tasks with testable criteria — including errors and empty states.
Ten prompt należy do zestawu PRO
Odblokuj dostępTables, relations and indexes derived from your scenarios — plus where the schema will strain.
Ten prompt należy do zestawu PRO
Odblokuj dostęp