Product templates

Use case

Turn a technical changelog or ticket list into customer-facing release notes that highlight value and what to do next.

Inputs required

• Changelog or list of changes
• Target audience (e.g. end users, admins)
• Product/version name
• Tone (e.g. concise, friendly)

Copy/paste prompt

You are a product writer who turns technical updates into clear, customer-focused release notes.
Changelog: [PASTE CHANGELOG OR TICKETS]
Product/version: [NAME]. Audience: [WHO].
Output format:
- Short intro (1–2 sentences) on what’s in this release
- Sections by theme (e.g. New features, Improvements, Fixes) with 1–2 sentence descriptions each
- Optional "What to try" or "Next steps" if relevant
Tone: [TONE]. Avoid internal jargon; focus on what users get.

Example output

Intro: This release brings faster dashboards and easier sharing. New: Export to PDF… Improvements: Simplified login… Fixes: Resolved loading issue on Safari…

Common mistakes

• Copy-pasting internal ticket text
• No grouping by value/theme
• Missing "what to do next"

Use case

Generate clear acceptance criteria for a user story or feature so dev and QA know what "done" looks like.

Inputs required

• User story or feature description
• Persona (who)
• Context (when/where)
• Definition of done (optional)

Copy/paste prompt

You are a product manager who writes precise, testable acceptance criteria.
User story: [STORY OR FEATURE DESCRIPTION]
As a [PERSONA], when [CONTEXT], I need [OUTCOME] so that [VALUE].
Generate 5–8 acceptance criteria in Given/When/Then or bullet form. Each must be:
- Testable (yes/no or clear pass/fail)
- Unambiguous (no "should work well" or "user-friendly")
- Scoped to this story (no out-of-scope edge cases)
[If you have a DoD standard, add it here.]

Example output

Given the user is logged in, when they click Export, then a PDF downloads within 5 seconds. Given the user has no data, when they click Export, then they see an empty-state message with a CTA to add data. …

Common mistakes

• Vague criteria ("works correctly")
• Mixing multiple stories
• No edge cases (empty, error states)