d5sd5s
Engineering workflow example

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.

When a release is marked complete Reviewable deliverable Approval boundary

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.

01

Collect shipped changes

Read merged pull requests and release metadata from the completed window.

02

Recover product intent

Use linked planning issues to distinguish outcomes from implementation detail.

03

Draft the narrative

Write the release note in the approved product voice and document structure.

04

Request publication review

Send the draft and evidence to the accountable release owner.

Connected systems

These are the real product connectors composed for this example, each scoped to the credential permissions your workspace approves.

GitHub

Read and write GitHub repos, issues, and pull requests.

Explore connector

Linear

Browse and update Linear issues, projects, and cycles.

Explore connector

Craft

Manage markdown blocks in collections with create, edit, delete, move, and undo capabilities.

Explore connector

Slack

Read channels and messages, post messages, and upload files as your Slack bot.

Explore connector

Optional skills

Where relevant, skills add reusable method and verification. The connectors and agent instructions remain the primary building blocks.

Brand

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
Marketing

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

Try asking

“Draft this week's release notes”
“Group these PRs by customer outcome”
“Prepare the publication review”

More examples for Engineering

Engineering When a qualifying alert fires

Incident triage

Trace a production error, identify the likely change, and prepare a triage issue without giving the agent authority to modify production.

Human approval built in

Build a governed workflow like release notes.

Tell us what your team repeats today. We will map the systems, approval boundaries, and first governed run with you.

Design a workflow