# Build a workflow around a result

A workflow is the way you combine teammates, context, tools, and review to get a repeatable outcome. Begin with one complete task before adding more roles or automation.

## Choose a starting pattern

| Your task                               | Start here                                               |
| --------------------------------------- | -------------------------------------------------------- |
| Turn scattered notes into a plan        | [Project kickoff](/docs/workflows/project-kickoff)       |
| Use information from an app             | [Connected work](/docs/workflows/connected-work)         |
| Have a second teammate critique a draft | [Team review](/docs/workflows/team-review)               |
| Produce a brief on a schedule           | [Recurring briefing](/docs/workflows/recurring-briefing) |
| Make a repository change                | [Cloud coding](/docs/capabilities/cloud-coding)          |

## Give each part an owner

Define which teammate gathers evidence, which teammate creates the result, and who reviews it. Share the necessary files or links and name a final deliverable.

Keep handoffs explicit: what is complete, where the output is, and what the next teammate should do with it.

## Make the successful pattern reusable

Save the general method as a skill. Save continuing project facts in memory. Add a routine only when the task should run on a schedule or another supported trigger.

> **Try this**
> Help me turn this one-off reporting task into a repeatable workflow. Identify the inputs, the teammate responsible, the review step, and the final output. Run one example before saving any recurring schedule.