Turn shipped work into clear release communication.
Collect shipped changes, translate implementation detail into customer outcomes, and route a complete release-note draft for approval.
A source-linked release-note draft grouped by customer outcome.
Human sign-off requiredA source-linked release-note draft grouped by customer outcome. Prepared for review, never posted.
How this composition works.
This workflow reads the final merged work rather than relying on memory at the end of a release. It groups related changes, checks the planning context, drafts outcome-led copy, and records sources. A human approves claims and publication so internal implementation language does not leak into public messaging.
Collect shipped changes
Read merged pull requests and release metadata from the completed window.
Recover product intent
Use linked planning issues to distinguish outcomes from implementation detail.
Draft the narrative
Write the release note in the approved product voice and document structure.
Request publication review
Send the draft and evidence to the accountable release owner.
A human signs off
A product or marketing owner approves every public claim and publication action.
A source-linked release-note draft grouped by customer outcome.
Human sign-off requiredA source-linked release-note draft grouped by customer outcome. Prepared for review, never posted.
Composed from the tools engineering already uses.
GitHub. Read and write GitHub repos, issues, and pull requests.
Linear. Browse and update Linear issues, projects, and cycles.
Craft. Manage markdown blocks in collections with create, edit, delete, move, and undo capabilities.
Slack. Read channels and messages, post messages, and upload files as your Slack bot.
Optional skills add method and verification.
Brand Guidelines. Apply a brand's colors, typography, and tone consistently across slides, docs, charts, and HTML. Use when output needs to match a company's visual identity. See the playbook →
Content Brief. Create an evidence-backed brief for an article, landing page, guide, case study, or campaign asset. Use before drafting when audience, angle, proof, structure, and approvals need alignment. See the playbook →
Put your engineering workflow under policy. Tell us what your team repeats today.
More for engineering.
Incident triage
Trace a production error, identify the likely change, and prepare a triage issue without giving the agent authority to modify production.
See the workflowDependency risk review
Read declared dependencies and recent runtime errors, identify the ones that are stale or already failing, and prepare a prioritized upgrade list.
See the workflow
Deploy health check
After a release, compare error and delivery signals against the pre-release baseline and report whether anything moved beyond normal variance.
See the workflow