SkillVaultskills Browse all 500 skills

Writing · Version 1.0.0 · Reviewed 2026-08-02

Release Notes Writer

Make the reader act on audience framing and change grouping with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Writes release notes organized around what changed for the reader rather than what shipped internally.

₹149 one-time

Get this skill archive

What this skill helps you do

  • Audience framing
  • Change grouping
  • Breaking change clarity

How Release Notes Writer works

You provide

Source material, audience, and the decision it supports

It inspects

Facts, gaps, and unstated assumptions for audience framing

It decides

A change grouping draft organized around the next action

You verify

Every claim traced back to the supplied source

What it checks first

Release Notes Writer writes release notes organized around what changed for the reader rather than what shipped internally. Use it when the work involves Audience framing, Change grouping, Breaking change clarity.

  1. The decision the reader must make and whether the document leads with it.
  2. Which claims are measured, which are derived, and which are assumed.
  3. Whether the structure follows the reader path or the author research order.
  4. Whether every assertion traces back to something in the source material.

Failure modes it recognizes

  • A recommendation buried after the analysis, so the reader never reaches the decision.
  • Invented specifics introduced while smoothing prose, which destroy credibility on discovery.
  • Precision implied by confident tone where the underlying evidence is thin.
  • Documentation mirroring product structure while readers arrive with tasks.

Answers it will reject

  • Producing a balanced list of considerations instead of a recommendation.
  • Restating the question with more words as though it were analysis.
  • Writing for the approver rather than for the person who must act.

Decision rules it applies

  • Lead with the decision and the confidence, then supply the evidence beneath it.
  • Label evidence quality so a reader can calibrate rather than assume everything is measured.
  • Cut anything that does not change the reader decision or action.

Evidence it asks for

  • Check every claim against the supplied source and mark unverifiable ones explicitly.
  • Have someone outside the work state the decision after reading only the opening.
  • Verify the document answers the question that was actually asked.

The method inside

  1. Identify the reader decision before drafting
  2. Lead with the conclusion and strongest evidence
  3. Remove unsupported claims and background that does not change action
  4. Check traceability, ambiguity, and the explicit ask

Deliverables

  • Audience framing revised draft
  • Change grouping source and logic check
  • Breaking change clarity approval-ready version

Evidence requirements

  • Source analysis, facts, decisions, and approved claims
  • Named audience, decision, and desired action
  • Format, length, tone, and review constraints

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Turn these 60 merged pull requests into release notes for our API customers.

Expected output

Sixty PR titles are an internal artifact and most affect nobody externally. Group by what a consumer must do: breaking changes needing action, new capabilities they can adopt, and fixes; drop everything with no observable external effect...

Boundaries and compatibility

Ideal for

  • Audience framing: produce a decision or artifact grounded in supplied evidence.
  • Change grouping: produce a decision or artifact grounded in supplied evidence.
  • Breaking change clarity: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Inventing facts, quotations, or approvals
  • Hiding uncertainty or material bad news

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.