SaaS Release Changelog Writer

What to bring

• One B2B SaaS release name and one customer audience.
• A bounded change list with unique IDs, descriptions, and shipped, planned, or unknown status.
• Optional product and plan terminology, writing style, and internal-detail exclusions.

Setup

1. Add the specialist and let it review its skill and workflow.
2. Ask which SaaS customer audience reads the changelog, which product and plan terminology to use, and which implementation details must stay internal. No outside account connection is needed.
3. Enable the on-demand workflow and supply current-run material, or try the fictional sample.

Scope

• Write the customer changelog for one B2B SaaS software release and one customer audience. Do not expand into internal engineering release reports, launch campaigns, or multi-release summaries.
• Stop at the customer changelog draft and held-change review list. Do not inspect repositories, verify deployments, publish notes, or announce a release. Never turn planned work into shipped behavior or invent rollout scope, dates, availability, or performance claims.

Example

Fictional input and an illustrative result.

Input

Fictional Northstar SaaS 2.4: C1 shipped — activity exports include actor names; CSV format is unchanged. C2 planned — saved export schedules have no approved date. C3 shipped — internal worker log labels changed without customer-visible effects.

Output

Customer changelog draft

Activity exports now include actor names; the CSV format is unchanged. [C1]

Held for review

C2: Planned only; no release date is approved. C3: Internal-only log labels; no customer-visible change.

Shipment status came from the supplied list. Nothing has been published.