Przejdź do treści
Biblioteka skilli
Zarządzanie i produkt · Pisanie

process-capture

/process-capture

Spisuje proces, który działa dobrze, ale zna go tylko kilka osób: rzeczywistą sekwencję, kryteria decyzji i listę kontrolną jakości dla zespołu.

Repozytorium
agency-skills ↗
Licencja
MIT
Ostatnia zmiana repozytorium
04.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 04.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Spisuje proces, który działa dobrze, ale zna go tylko kilka osób: rzeczywistą sekwencję, kryteria decyzji i listę kontrolną jakości dla zespołu.

Wyzwalacze z opisu

write down how we actually do thisdocument our processbuild an SOPwhy does everything go through me
Oryginalny opis (EN)

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".

Jak działa

  1. The play
  2. What good looks like
  3. Rules
Sekcje z nagłówków SKILL.md, w oryginale · 42 linii, 628 słów
Podgląd SKILL.md
---
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.

Wersje

W bazie nie ma innych skilli o nazwie process-capture.

Migawka bazy z 13.11.2026 · wersja paczki 5e07c392d835 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100process-documentation-sop
    Zamienia proces znany jednej osobie w instrukcję SOP: mapa stanu obecnego, role, numerowane kroki, reguły decyzyjne, wyjątki, eskalacje i kontrole jakości.
  • 100sop-builder
    Spisuje powtarzalny proces z głowy jednej osoby w SOP, który każdy człowiek lub agent wykona tak samo, a także audytuje i przepisuje nieaktualne SOP.
  • 100pm-process-docs
    Tworzy instrukcje SOP i runbooki dla procesów produktowych z krokami, punktami decyzyjnymi, listami kontrolnymi, właścicielami i punktami zgodności.
  • 100process-doc
    Dokumentuje powtarzalne procesy jako instrukcje SOP krok po kroku z punktami decyzyjnymi, przypadkami brzegowymi i nazwanym właścicielem, aby każdy mógł wykonać proces poprawnie bez pytania.
  • 100keel-process
    Dokumentuje lub przeprojektowuje proces biznesowy: procedura SOP, mapa procesu, RACI i przypisanie właścicieli.
  • 100process-doc
    Dokumentuje proces biznesowy w postaci schematów blokowych, macierzy RACI i procedur SOP, uwzględniając wyjątki i przypadki brzegowe.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.