AI Blocks › Write down how work gets done
Set up a documentation system and write procedures that pass
Give it how your team works. Get a documentation system, procedures, runbooks and a check of each.
Set up a documentation system and write procedures that pass is a free AI workflow for the job "Write down how work gets done". It guides your AI through several skills in order, passing each step's output to the next.
Free · No account · Made by AI Blocks · Thinking: high
What it does
Teams write documentation twice: once in a burst, then never again. The pages live in three places, nobody owns them, and the procedure that matters is out of date by the second week. When something breaks at night, the runbook says "ask Sam". This workflow sets up a system before it writes a word. It plans where documentation lives, how it is named, who owns each page and when it is reviewed. It writes the standard procedures for your repeat tasks, step by step, with what good looks like. It writes the runbooks for when things break: what to check, in what order, who to call. Then it checks each procedure and runbook as a newcomer would, step by step, and lists every place a stranger would get stuck or need to ask.
You give it
- How your team works: the repeat tasks, who does them, where notes live today
- What goes wrong and how it gets fixed now
- Your tools and systems
- Existing docs, however rough (optional)
You get
- A documentation system: where pages live, how they are named, who owns each, when they are reviewed
- A standard procedure for each repeat task
- A runbook for each thing that breaks
- A check of every procedure and runbook with what a stranger could not follow
Use it when
- The same task is done differently by everyone who does it.
- Something broke at night and the only person who could fix it was asleep.
- You have docs, but nobody can find them or trusts them.
Steps
- Documentation system planner: Describe your team and product. Get what to write down, where it lives and how to keep it fresh.
- Process and SOP writer: Describe how work gets done. Get a flowchart, who does what, and a written procedure with the edge cases.
- On-call runbook writer: Describe a service or process. Get a step-by-step runbook that anyone on call can follow under pressure.
- SOP and runbook checker: Give it your SOPs or wiki export. Get missing owners, stale pages and gaps, plus new SOPs to fix them.
How to use it
- Download the handoff pack. It's a zip with HANDOFF.md and every skill file this workflow uses.
- Give the folder to Claude (in Claude Code, or as files in a Claude Project) and say "Follow HANDOFF.md".
- Paste how your team works and what goes wrong. It plans the system and writes the procedures.
- Read the runbooks with the person who fixes things today. Correct what they know differently.
- Read the check and fix every step a stranger could not follow. Put the pages in the system.