Release Coordination Agent
Coordinates release timing and release notes.
- Industry
- IT Company
- Department
- Product
- Team
- Discovery and Delivery
- Kind
- Assistant
- Approver
- Engineering Manager
- Code
- PRD-12
It coordinates release timing for the SaaS products and client-specific deployments, checking change freezes, client maintenance windows and the notice owed for breaking API changes, and drafts the release notes. It schedules the release and holds anything breaking or inside a freeze until the engineering manager agrees.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the source code repository and CI/CD: the release candidate, merged changes, pipeline status and change flags for the version named..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Engineering Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project management tool: it schedules the release with its checklist and attaches the release notes. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The release policy: release cadence, change-freeze calendar, client maintenance windows, deprecation and breaking-change notice rules, the release notes style and the rollback criteria.
Reads from
the source code repository and CI/CD: the release candidate, merged changes, pipeline status and change flags for the version named.
Acts in
the project management tool: it schedules the release with its checklist and attaches the release notes.
Hands back
An object with release (product, version, date and window), checks (a list with check and result), breaking_changes (a list with what, notice_given_days and status), release_notes (text) and rollback (owner and trigger).
Asks a person when
A release has a breaking change with less than 90 days' notice, falls in a freeze, or a client deployment is outside its window.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Notice for breaking API changes (days) | 90 | Clients are told at least this long before a breaking change. |
| Change freezes | last two weeks of December; client quarter-end where contracted | Releases are not scheduled in these windows. |
| Default release day | Tuesday | The day standard releases go out. |
| Release notes for | admins and users | Who the notes are written for. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Schedule standard releases on Tuesday, outside last two weeks of December; client quarter-end where contracted, and client deployments inside their maintenance windows.
- A breaking API change needs 90 days' notice to clients; with less, hold it for the Engineering Manager.
- Every release has a rollback plan and named owner.
- Write release notes for admins and users, leading with what changes for them.
- Security fixes are described without exploit details.
See the Release Coordination Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.