Lesson 2.4 of the Free Claude Cowork Course · 25 minutes
Overview
A skill only you can run is a personal productivity gain. A documented workflow anyone on the team can run is an organizational one — it survives vacations, handoffs, and departures. This lesson takes the skill you built in 2.2 and makes it shareable: documented, owned, and runnable by a colleague who wasn’t in the room when you made it.
What You’ll Do
- Document a workflow using the four-field standard: trigger, inputs, output, owner
- Start a team workflow library with naming conventions that scale
- Run the colleague test: could someone else execute this from the documentation alone?
The Lesson
Say “start lesson 2.4”. You’ll take your 2.2 skill and write its library entry: what phrase triggers it, what inputs it expects and where they live, what the output should look like, and who owns it when it breaks. Then the lesson runs the colleague test — Cowork role-plays a teammate seeing the workflow for the first time, following only your documentation, and you find out fast which steps lived only in your head. You’ll fix the gaps and re-test.
Naming conventions get a short but important section: reporting-weekly-pipeline beats my workflow v2 final once the library passes five entries.
Try It Now
Document one more workflow — someone else’s task this time, based on how you understand it — and note the questions you couldn’t answer. Those questions are exactly what makes shared documentation valuable.
What’s Next
← Previous: 2.3 Team Context Folder
Next: 2.5 Capstone: Your First Team Workflow →
New here? Download the full course free on GitHub.
Rolling this out for a whole team? See our live team training.