Release Notes Draft AI Agent Workflow

Workflow overview

Produce a human-reviewed release-note draft from merged changes and issue context.

• Trigger: Manual run after a release candidate is selected.
• Intended role: Developer
• Version: 1.0

Compatible agents

Compatibility with OpenAI Dots and Meta Muse has not been tested by AI Dots. Check app access, native permissions, and scheduling in your own account before adapting this Blueprint.

Required integrations

GitHub read access or a user-provided export is needed to inspect repository evidence. The exact connection path depends on the chosen agent.

How it works

These steps produce a reviewable artifact; the agent does not receive permission to publish or write by default.

• Collect changes in the specified range.
• Group user-facing changes and identify source links.
• Exclude internal-only or unverified claims.
• Draft concise notes with an unresolved-items list.

Agent Blueprint

One source of truth for the on-page copy and Markdown download.

# Release Notes Draft

Version: 1.0
Status: Untested by AI Dots

## Goal
Produce a human-reviewed release-note draft from merged changes and issue context.

## Trigger
Manual run after a release candidate is selected.

## Inputs
- Release range or tag pair
- Merged pull requests or changelog
- Audience and tone requirements

## Steps
1. Collect changes in the specified range.
2. Group user-facing changes and identify source links.
3. Exclude internal-only or unverified claims.
4. Draft concise notes with an unresolved-items list.

## Outputs
- Release-note draft
- Source links for each substantive change
- Open questions

## Permissions
- Read repository history and linked issues.
- Do not publish a release or edit a repository.

## Approval boundaries
- Maintainer reviews claims and approves publication separately.

## Failure behavior
- If the release range is unclear, ask for it.
- If a change lacks enough context, place it in open questions.

This Blueprint is an instruction template. It does not run an agent, connect apps, schedule work, or enforce permissions. Check support in the chosen agent platform.

Permissions

Configure actual app permissions in the agent and external service. Blueprint text alone does not enforce access.

• Read repository history and linked issues.
• Do not publish a release or edit a repository.
• Maintainer reviews claims and approves publication separately.

Expected output

Illustrative structure, not a result from an AI Dots test.

• Release-note draft
• Source links for each substantive change
• Open questions

Failure modes

Missing evidence is reported explicitly.

• If the release range is unclear, ask for it.
• If a change lacks enough context, place it in open questions.

Test results

Not tested by AI Dots yet. A complete Blueprint does not establish vendor compatibility or successful execution.

Version history

Version 1.0 — initial public Blueprint.