[01] LOOP
ContentmanualHardened

Changelog Until Shipped

Parse recent PRs and commits, write a user-facing changelog entry, publish it, and verify it appears on the public changelog page.

by Trooper

Kickoff prompt
Start the "Changelog Until Shipped" loop.

Goal: changelog entry published and visible on public changelog page
Max iterations: 6
Between iterations run: Verify changelog page includes the new entry with correct date
Exit when: entry is live on public changelog with accurate release date

Step 1: Parse PRs/commits, write user-facing changelog, publish, and verify live.

## Before you start

Connect plugins:
- GitHub (required) — Read branches, PRs, reviews, checks, workflow runs, and source diffs.
- Browser / Web access (required) — Open pages, inspect live state, collect evidence, and verify changes.
- Google Analytics (required) — Read traffic, conversion, product, or campaign performance signals.
- Notion (required) — Read and update approved briefs, docs, calendars, and reports.

Attach skills:
- Loop runner (required) — Self-pace iterations, run the check between passes, and stop only on the exit condition.
- Code change + local verification (optional) — Edit code safely, run commands, and keep changes scoped.
- Browser QA (optional) — Exercise product flows, capture visual evidence, and verify fixes in-browser.
- Content operations (optional) — Turn signals into reviewable briefs while preserving source attribution.
- Documentation QA (optional) — Check docs against current product behavior and keep claims accurate.

Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.

Paste the kickoff prompt into Cursor, Claude Code, or Codex. Deeplinks do not install hook files.

Steps

1. Parse changes

Read merged PRs and commits since last release; group by user impact.

2. Write changelog

Draft user-facing entries with features, fixes, and breaking changes.

3. Publish and verify

Deploy changelog update and confirm it appears on the public page.

Flow diagram

Guardrails

Rules the agent must follow so it cannot cheat the exit condition.

  • Write user-facing language — no internal ticket IDs or commit hashes in copy
  • Do not publish breaking changes without migration notes
  • Get approval before publishing customer-visible entries

More Content loops