Others

Release Shepherd

A closed loop bound to one upcoming release that runs a daily readiness checklist, reports drift, and files a final go/no-go on release day before finishing.

Moderate setupShort cycleClosed loopVisible first run

Create directly in Loopany

How this loop works

Suggested schedule: Daily until release day
Loop type: Closed loop — goal-bound; it finishes itself when the goal is met.
Exit condition: Finishes when the release ships or is formally called off.
Notifications: On by default — you're alerted on each run's outcome (completion or failure). Silence with notify: never.
Ease of starting: Some setup and context are needed before the first useful run.
When you see value: The first readiness pass flags drift immediately; it finishes on release day.

The prompt this runs

Set up a closed loop that shepherds one specific upcoming release to its date. Confirm the release with me first - which version or milestone, and the target date - and before creating anything, verify this machine can read the signals a readiness check needs - CI status via gh, the dependency and advisory state, the docs and changelog, the rollback or deploy plan - and smoke-test them once; never create a blind loop. Create the loop closed, with the release shipping (or being formally called off) as its goal, and a cadence of one readiness pass per day until the date. Each run, walk the checklist - is CI green on the release branch, are dependencies and advisories clear, are the docs and changelog updated, is the rollback plan in place - and report any drift plainly with what still needs doing, staying strictly report-only: never mutate the release yourself. On release day, file a final go/no-go readiness report with front matter `type: report`, a `title`, and `date`, and once the release has shipped or been called off, finish the loop. Report the count of open readiness items as a metric. Set up the loop's dashboard at creation: an embed of the latest readiness report plus a chart of the open-item count over time.

This is the exact intent appended to the bootstrap when you create the loop — your coding agent reads it, then proposes cadence and config and confirms with you before creating anything.