The setup
This illustrative Spinrun workflow shows how an operations team can approach the work. The intended result is a reviewed weekly brief. The team starts from information it has permission to use and names a person to review the result.
The relevant tools are Slack · Google Drive · Linear. Available connections depend on the workspace and provider authorization. The first attempt uses a small representative input so the reviewer can compare the result with its source.
The job to delegate
The useful brief sets the output, audience, sources, and approval boundary together. It should describe work a teammate can recognize as finished rather than ask for a broad improvement to the business.
Read this week's project notes and open issues. Draft an operating brief with wins, blockers, owners, and next steps. Link every factual claim to its source. Do not post it until I approve.The first run
The reviewer supplies the approved material and asks for a draft. Spinrun gathers the permitted context, reports missing sources, and produces a reviewed weekly brief. A task that cannot read its source should identify that gap rather than quietly guess.
The result stays attached to the conversation, along with corrections and approval context. The team checks a normal case and an exception before relying on the instruction again.
Real work needs a review point
The reviewer verifies source links, identifiers, date ranges, and the proposed next actions. A successful tool response is one part of the evidence. Publishing, sending, or changing an external record deserves a separate decision based on the actual destination and content.
If an external write has an uncertain outcome, the team inspects the destination before repeating it. A retry should not become a duplicate message or record.
Make the process shared
Once a manual run is useful, the team saves the instruction as a skill. It includes the inputs, source locations, decision rules, exceptions, and output standard. One person owns maintenance. This makes the workflow easier to review and keeps it from depending on an unstated habit.
Measure what changed
Measure preparation, review, corrections, and maintenance together. Check whether the output arrived on time and whether each next action had an owner. This walkthrough makes no claim about customer savings, revenue, or headcount. Useful evidence comes from the team's own before-and-after work.
Put the working version on a schedule
The team schedules only the reviewed process. It specifies a timezone, reporting period, destination, and response to missing sources. Unchanged state can stay quiet when the job is an exception check. The first scheduled result receives the same review as the first manual one.
Honest notes
A workflow is only as useful as its sources and maintenance. For this example, the team should check that a reviewed weekly brief still supports the decision it was designed for. Revise the skill when the business process changes. Start with the product guides or Academy to build a version for your own workspace.