A 90-Minute Recording Becomes an SOP
Record your best person doing the job once. Get the procedure forever.
Nobody writes SOPs because writing them is boring and the expert is busy. Recording them talking through it takes ninety minutes of the time they already spend.
That is the gap this drop closes. It is a operations skill built for Kimi, and it takes about ten minutes to set up the first time. After that it runs in under a minute.
Who should use it
Businesses where the process lives in one person's head.
How it works
The skill file does five things, in this order.
1. Record a real run-through. Screen and voice, doing the actual task, not describing it.
2. Extract the ordered steps. Including the ones they did without mentioning.
3. Capture the judgement calls. Every 'it depends' becomes an explicit if-then rule.
4. Note the tools and access. The SOP is useless if step 4 needs a login nobody has.
5. Write the failure branch. What to do when the normal path does not work.
What comes back
A numbered SOP with decision rules, required access, and failure handling.
The mistake to avoid
Have a second person follow the SOP without asking questions, then feed their confusion back in. The gaps only show up when someone who does not know the job tries it.
Running it
Paste the prompt block into a new Kimi chat and attach your files in the same message. Kimi's long context means you should upload everything at once rather than in batches, splitting the input is what causes it to lose cross-references between documents.
Where this fits
On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.
In the file
Convert this recording transcript into a standard operating procedure.
1. PURPOSE AND TRIGGER, what this procedure achieves and what starts it.
2. PREREQUISITES, tools, logins, permissions, information needed before step 1.
3. STEPS, numbered, one action each, written as commands. Include steps the
expert performed without narrating, and mark those [OBSERVED, UNSTATED].
4. DECISION RULES, every "it depends" or "usually" in the transcript becomes
an explicit IF / THEN / ELSE rule. List the ones you could not resolve under
NEEDS CLARIFICATION.
5. FAILURE HANDLING, what to do when a step fails, per step where it matters.
6. QUALITY CHECK, how to know the output is correct.
Write for someone who has never done this task.
<transcript>{paste}</transcript>