A shared AI workflow is useful when teammates can repeat the result without guessing which context, destination, or approval rule another person intended. Sharing everything is not the goal. Preserving the accepted parts of one working process is.

Strawberry can keep team guidance, shared artifacts, ownership, and recurring work together while personal or client-confidential context stays within its approved boundary. Start with one proven workflow and verify one real handoff.

Start with one proven workflow

Choose a process that already creates a useful result for one person. Clarify its inputs, owners, destination, field meanings, review points, exceptions, and what a successful handoff means before trying to standardize it.

Use an existing example or template when one is available. The aim is to preserve the team's judgment, not replace it with a generic process document.

Set up a shared team workflow

Use this to map an accepted workflow into a clear shared process.

I want to turn a workflow that works into a clear shared process for my team.

Share the right context, not every context

Put reusable guidance and approved shared artifacts in the team workspace. Keep personal, client-confidential, and unapproved material out, and keep different clients' data separated.

A shared skill can preserve the team's sources, structure, writing conventions, and review rules. Shared memory should hold durable context that is genuinely useful across the team rather than becoming a dump of every conversation.

Make ownership and handoffs visible

Map approved inputs to a reviewable output, keep source links where they matter, and make responsibility and approval boundaries explicit. Pilot the process with the people who own the work and verify permissions, field meanings, handoffs, and review behavior.

Ask before sending sensitive communication, changing access, or making irreversible updates. A shared process should make control clearer, not bury it.

Add recurrence only when the team trusts the process

Preserve the accepted process as a team-visible custom skill after the first handoff works. Add a Routine only when the team explicitly wants recurring execution and has agreed on ownership, review, exceptions, and notification behavior.

When the workflow is part of joining or leaving the team, connect it to a reviewed onboarding or offboarding checklist so access and responsibilities do not drift.

Onboard and offboard teammates reliably

Use this when the shared workflow belongs in teammate onboarding or offboarding.

I want to make teammate onboarding and offboarding reliable and much less manual.
Official Strawberry skill
name
set-up-shared-team-workflow
description
Turn an accepted individual workflow into a clear shared team process. Use when several teammates need consistent inputs, destinations, ownership, review points, or reusable guidance for work they perform together.

Set Up a Shared Team Workflow

This is a starter skill for turning a useful individual workflow into a shared team process. Adapt it to the team's existing tools, responsibilities, privacy boundaries, and way of working rather than treating the outline as a fixed method.

Context, setup, and planning

Try to understand the result, team, source systems, shared destination, ownership, review points, privacy boundaries, and what a successful handoff means. Existing team documentation, workspace files, process notes, templates, and approved systems can help when they are relevant and available; they are not prerequisites. Offer to learn through a few questions, inspect that existing context, or combine both.

Before changing anything, show the team a concise plan covering inputs, owners, destination, review points, and the intended approach. Where useful, agree on one representative example, template, or reporting cadence to calibrate the workflow before expanding it.

Execution

  1. Start with one accepted workflow rather than redesigning all of the team's operations.
  2. Map the workflow from approved inputs to a reviewable output. Keep responsibilities and approval boundaries explicit.
  3. Preserve source links or other provenance needed to review shared findings and updates.
  4. Put reusable team guidance and shared artifacts in the team workspace. Keep different clients' data separate, and do not move personal, client-confidential, or unapproved context into shared files.
  5. Run a small pilot with the people responsible for the work. Verify permissions, handoffs, field meanings, and review behavior before scaling.
  6. Preserve the accepted process as a team-visible skill or shared guide. Add a Routine only when the team explicitly wants recurring execution.

Ask for approval before sending sensitive communications, changing access, or making irreversible updates.

Suggested outcome

Create a concise, reusable team workflow with clear inputs, owners, shared destinations, field meanings, review points, privacy boundaries, and a verified first handoff. Teammates should be able to repeat the process without guessing what another person meant.

Suggested next steps

  • Use strawberry/recruiting/onboard-offboard-teammates when the workflow must be added to a teammate's onboarding or removed during offboarding.
  • Add a Routine only after the team accepts the manual or assisted first run.
  • Invite additional teammates only when the user wants them involved in the shared workflow.