Playbooks
A repeatable job.
A reviewable result.
Use a playbook to give an agent the same inputs, steps, and quality checks each time. Here is a complete release-note example you can adapt to your own team.
Use this example with your own agent or working notes. Saving and running playbooks inside Autoglide is not available yet.
Worked example / Release note
Start with three facts and one limit.
For this fictional notes app, the approved release brief is the source of truth. The content role prepares the announcement; the release owner checks it and decides when to publish.
Source brief
- New: filter notes by tag.
- Fixed: duplicate notes appearing after a retry.
- Limit: tag filters are available on desktop only.
- Audience: existing users. Length: under 70 words.
Required output
One draft, its supporting source facts, and any unresolved questions. Do not invent a release date, pricing, customer quote, or mobile availability.
Publication is a separate decision. A finished draft is ready for review, not automatically ready to send.
Reusable instructions
A brief you can use.
PLAYBOOK: Release note / v1
Owner: Content role
Reviewer: Release owner
INPUTS
Approved changes, known limits, audience, word limit.
STEPS
1. Read the source brief. Stop if facts conflict.
2. Draft only supported changes in plain language.
3. Mention any limit that affects the audience.
4. Return the draft and a fact-to-source checklist.
DONE WHEN
The reviewer can verify every product claim.
ASK FIRST
Missing facts, changed scope, or external publication.Replace the inputs for each release. Keep the procedure stable until review shows a specific reason to change it.
Example result
The output stays close to the evidence.
Find the right notes faster with tag filters on desktop. We also fixed an issue that could create duplicate notes after a retry. Mobile tag filtering is not included in this release.
Supporting facts: sentence one uses the new feature and desktop limit; sentence two uses the retry fix; sentence three makes the mobile boundary explicit.
- Every feature and limitation matches the approved brief.
- The draft is under 70 words and names no unsupported benefit.
- The release owner has confirmed the final text and destination.