Skip to content
Skills Library
Management & product · Writing

process-capture

/process-capture

Use this skill when something the firm does well lives only in one or two people's heads, and those people have become the bottleneck. Produces a written process anyone on the team can run: the real sequence including the steps people skip, each decision with the criteria behind it, the quality bar as checkable items, and which steps still need the senior person. Also use for "write down how we actually do this", "document our process", "build an SOP", "why does everything go through me".

Licence
MIT
Last repository change
04.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 04.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use this skill when something the firm does well lives only in one or two people's heads, and those people have become the bottleneck. Produces a written process anyone on the team can run: the real sequence including the steps people skip, each decision with the criteria behind it, the quality bar as checkable items, and which steps still need the senior person. Also use for "write down how we actually do this", "document our process", "build an SOP", "why does everything go through me".

Triggers from the description

write down how we actually do thisdocument our processbuild an SOPwhy does everything go through me
Original author description

Use this skill when something the firm does well lives only in one or two people's heads, and those people have become the bottleneck. Produces a written process anyone on the team can run: the real sequence including the steps people skip, each decision with the criteria behind it, the quality bar as checkable items, and which steps still need the senior person. Also use for "write down how we actually do this", "document our process", "build an SOP", "why does everything go through me".

How it works

  1. The play
  2. What good looks like
  3. Rules
Original SKILL.md headings · 42 lines, 628 words
SKILL.md preview
---
name: process-capture
title: Process capture
description: |
  Use this skill when something the firm does well lives only in one or two
  people's heads, and those people have become the bottleneck. Produces a
  written process anyone on the team can run: the real sequence including
  the steps people skip, each decision with the criteria behind it, the
  quality bar as checkable items, and which steps still need the senior
  person. Also use for "write down how we actually do this", "document our
  process", "build an SOP", "why does everything go through me".
category: Operations
tags: [sop, process-documentation, delegation, knowledge-capture, agency-operations]
---

Applies to work the firm repeats and has never written down. Produces the process document, plus a list of the judgment calls that could not be articulated yet.

## The play

1. Collect several finished examples of what this process produces before interviewing anyone. The standard is visible in the outputs and describable only vaguely in conversation. Three real examples teach more than an hour of the senior person explaining their method.

2. Get the sequence by walking through the last real instance, start to finish, rather than asking how the process works in general. Asked in general, people describe the version in the handbook. Asked about last Tuesday, they describe the version that happens.

3. Note the steps people skip when busy, and sort them: the skips that are fine, and the skips that cause the problems. This distinction is most of the value, and it never appears in a process written top-down.

4. Split the mechanical steps from the decisions. Mechanical steps get instructions and can be handed over tomorrow. Decisions get criteria, and they are the reason the work cannot be delegated yet.

5. For each decision, get the criteria out. If the senior person cannot state the rule, have them talk through two past instances where they chose differently, and derive it from the contrast. "It depends" is the start of the answer, not the end of it.

6. Write the quality bar as things a reviewer actually checks, pulled from the examples. Not that it should be good, but the five specific things looked at before it goes to a client.

7. Mark which steps genuinely need the senior person and which do not. This is the line the owner is really buying: it tells them what they could hand off this week.

8. Note what the process needs from upstream and hands off downstream, so it connects to the rest of how the firm runs instead of sitting in isolation.

9. Surface any contradiction between what the person described and what the examples show. That gap is where the written process and the real one have drifted, and it is usually the most useful finding in the document.

## What good looks like

- First thing I check that most people skip: the finished outputs, before I talk to anybody. People describe the process they believe they follow. The artifacts show the one they actually followed, and the gap between those two is the whole job.
- The mediocre version: a numbered list of the happy path, with every real decision collapsed into "review and approve". It documents the parts nobody needed written down.
- I know it is right when somebody who has never done the work produces something the reviewer does not have to rebuild.
- Second test: every decision has criteria underneath it. "It depends" is where the knowledge is, not where the document stops.
- Red flag: the written process and the examples disagree and nobody had noticed. The real process has drifted, and writing up the old one just makes the wrong version official.

## Rules

- MUST work from several real examples of the output, not only a description.
- MUST derive the sequence from the last real instance, not from how it is supposed to go.
- MUST separate mechanical steps from decisions, and give every decision its criteria.
- MUST write the quality bar as items a reviewer can check.
- MUST mark which steps require the senior person.
- MUST surface contradictions between the description and the examples.
- NEVER leave a decision as "use your judgment". That is the thing being captured.
- NEVER write a generic version of the process. With nothing firm-specific to work from, produce the interview questions instead.

Versions

The database has no other skills named process-capture.

Database snapshot: 13.11.2026 · package version 5e07c392d835 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100process-documentation-sop
    Turns a process that lives in one person's head into a standard operating procedure someone new can follow without asking: the current-state map built by observation, then the document with purpose, trigger, owner, roles, numbered steps naming the exact system and the expected…
  • 100sop-builder
    Use when a repeated process lives in one person's head, breaks when they are away, gets re-explained to every new hire, or produces inconsistent results — and needs writing down once so anyone or any agent can run it the same way. Also for auditing and rewriting an SOP that is…
  • 100pm-process-docs
    SOP and runbook generator for PM processes. Documents steps, decision points, checklists, ownership, and compliance checkpoints. Produces actionable runbooks. Use when someone says "SOP", "standard operating procedure", "runbook", "process doc", "how do we do X", "document the…
  • 100process-doc
    Documents recurring processes as step-by-step SOPs with decision points, edge cases, and a named owner, so anyone can run the process correctly without asking. Use when someone asks "write an SOP for this", "document our onboarding process", "this only lives in one person's…
  • 100keel-process
    Document or redesign a business process — standard operating procedure (SOP), process map, RACI, and owner assignment. Use when asked to "document this process", "write a runbook", "design how we handle X", or "map the process for Y".
  • 100process-doc
    Document a business process — flowcharts, RACI, and SOPs. Use when formalizing a process that lives in someone's head, building a RACI to clarify who owns what, writing an SOP for a handoff or audit, or capturing the exceptions and edge cases of how work actually gets done.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.