SOP Authoring
Turns a captured process into a rigorous Operational SOP using a structured template, calibrated to
the process's maturity. When /automation-triage marked steps as RPA- or AI-automatable, it also
emits a runnable executable SOP with human-approval gates. Final stage of the pipeline:
process-standardization → automation-triage → sop-authoring
(discover + capture) (decide the how) (write the SOP + executable form)
Language rule
The skill's questions and working notes are in English. Generated SOPs follow the engagement's
working language — English by default, Spanish for Costa Rica engagements (matching the contract
skills). Confirm if unclear.
Output directory
Resolve the pipeline directory {sops-dir} first, in this order:
- If a business brain exists in the working directory (a
business-brain/ folder, or a vault
root with _procedimientos/ — see /business-brain-setup), then
{sops-dir} = <brain-root>/_procedimientos/. SOPs that belong to a business LIVE in its
business brain; that folder is their canonical home.
- Otherwise (no brain yet, e.g. a client engagement without one),
{sops-dir} = ./fractional-cto/sops/.
Flujo del skill
Paso 1 — Routing test
Before writing, confirm the thing is actually an Operational SOP. An SOP documents how the
company operates a recurring process, no code required to understand it. Use the shared
three-way ops taxonomy in references/documentation-taxonomy.md
(playbook / runbook / SOP) plus the usual product-docs cases.
Rule of thumb (from the taxonomy): if a software engineer must understand it to execute it,
it is not an SOP — it is a runbook (or an ADR). If they must choose among branches first,
it is a playbook — never a runbook, post-mortem, or SOP. Promote a playbook to an SOP only once
the work is a recurring company process with no engineering context required. If it fails the
routing test, tell the user which type it actually is and stop — do not force a non-process into
the SOP template.
If the type is ambiguous, run /document-this to resolve it before continuing.
Paso 2 — Depth by maturity
Ask (or infer) the process's stage; it decides which sections are required:
| Stage |
Required sections |
TBD allowed? |
| Draft / proposed |
Header, 1 Purpose, 2 Scope, 3 Audience, 6 Process (outline), 11 Revision History |
Yes, freely |
| In rollout |
+ 5 Roles; Process fully documented |
Edge cases only |
| Active production |
All sections; no TBD in the procedure |
No |
This calibration mirrors how /project-takeover scales document detail to risk level — here it
scales to process maturity.
Paso 3 — Author the SOP
- Read the template:
${CLAUDE_PLUGIN_ROOT}/references/05-operational-sop-template.md
- Load inputs if present:
{slug}-capture.md (the steps) and {slug}-triage.md (the verdicts).
- Fill each required section. Apply the template's writing discipline:
- Name owners by role, not person ("Head of Support", not "Fer") so the SOP survives turnover.
- Real tool names, real numbers, real thresholds — days of lead time, dollar amounts, volumes.
- Sequential, testable steps — Step 4 executable only after Step 3.
- Tables for anything with more than three parallel items (roles, phases, tools).
- Callouts for what the reader must not miss:
> DECISION POINT, > SCALE NOTE,
> LESSON LEARNED.
- In Section 6, structure phases with Owner / Duration / Gate to next phase.
- Write to
{sops-dir}/{slug}/{slug}-sop.md.
Paso 4 — Executable mode (when automatable)
If {slug}-triage.md contains any RPA or AI agent / Human + AI verdict, ALSO emit a runnable
executable SOP:
- Read the template:
${CLAUDE_PLUGIN_ROOT}/references/06-executable-sop-skill-template.md
- Build the frontmatter:
name, a description with the run trigger, and required_tools —
the MCP tools the RPA/AI steps call.
- Turn the procedure into numbered executable steps, attaching gate markers by verdict:
Human / Human + AI step → [APPROVAL REQUIRED]; outward-facing or irreversible actions
(sends email, moves money, deletes data) → [PRE-APPROVAL REQUIRED].
RPA — attended → runs with a human trigger; RPA — unattended / AI agent → no gate.
- Conditional steps →
[OPTIONAL].
- State in the doc that the markdown is authoritative (edit steps = change behavior) and that human
gates are structural. Reference the JSONL run log.
- Write to
{sops-dir}/{slug}/{slug}-sop.skill.md.
If every verdict is Human, skip this step — a purely human process needs no executable form. Say so.
Paso 5 — Quality checklist + bus test
Before finishing, run the checklist from the template (routing / structure / content / cross-reference)
and the bus test: "if I got hit by a bus tomorrow, could a teammate read this SOP and run the
process?" If no, add detail — vague steps, unnamed owners, and missing thresholds are the usual gaps.
Paso 6 — Confirmación
Present the deliverables and how to use them:
{slug}-sop.md → "The operational SOP — the human-readable source of truth."
{slug}-sop.skill.md (if emitted) → "The runnable version — an LLM runtime executes it, pausing at
the approval gates. The markdown is authoritative; edit the steps to change behavior."
Suggested next step:
"Keep the SOP a living document: bump the version when the process changes, and re-run
/automation-triage when a step's volume or tooling shifts enough to change its verdict."
Notas para el modelo
- This skill is the general-purpose SOP engine.
/project-takeover is a specialized SOP producer
(project handovers) — this one handles any operational process.
- The executable form is only emitted when triage says a step is automatable. Do not fabricate
automation for a process that is genuinely all-human.
- The SOP is the source of truth for what exists today; keep improvement ideas in the open-questions
list, not silently baked into the steps.
- Personalization is about ELIMINATING sections that do not apply at the current maturity, not adding
unnecessary complexity — same discipline
/project-takeover uses when pruning its templates.
- Use the Acme universe for examples (e.g. "AcmeLegal client-intake SOP", "RapidEats refund SOP").
1---2name: sop-authoring3description: >4 Writes a structured Operational SOP from a captured process, and emits an executable version when5 any step is automatable. Use this skill when the user mentions "write an SOP", "standard operating6 procedure", "operational procedure", "document this process properly", "turn this into an SOP",7 "make this SOP executable", "runnable SOP", "SOP as an agent", or any situation where a fractional8 CTO needs to produce a rigorous, testable operating procedure. This is the OUTPUT stage of the9 process-engineering pipeline — it consumes /process-standardization captures and /automation-triage10 verdicts. NOT for takeover-specific SOPs (that is /project-takeover), NOT for11 decision-tree ops playbooks (that is /playbook-authoring), NOT for execute-under-pressure12 runbooks (that is /runbook-authoring), and NOT for contracts.13metadata:14 source: https://skillmd.com/skills/chimeranext/sop-authoring15---1617# SOP Authoring1819Turns a captured process into a rigorous Operational SOP using a structured template, calibrated to20the process's maturity. When `/automation-triage` marked steps as RPA- or AI-automatable, it also21emits a runnable executable SOP with human-approval gates. Final stage of the pipeline:2223```24process-standardization → automation-triage → sop-authoring25 (discover + capture) (decide the how) (write the SOP + executable form)26```2728## Language rule2930The skill's questions and working notes are in **English**. Generated SOPs follow the **engagement's31working language** — English by default, Spanish for Costa Rica engagements (matching the contract32skills). Confirm if unclear.3334## Output directory3536Resolve the pipeline directory `{sops-dir}` first, in this order:37381. If a business brain exists in the working directory (a `business-brain/` folder, or a vault39 root with `_procedimientos/` — see `/business-brain-setup`), then40 `{sops-dir}` = `<brain-root>/_procedimientos/`. SOPs that belong to a business LIVE in its41 business brain; that folder is their canonical home.422. Otherwise (no brain yet, e.g. a client engagement without one),43 `{sops-dir}` = `./fractional-cto/sops/`.4445## Flujo del skill4647### Paso 1 — Routing test4849Before writing, confirm the thing is actually an Operational SOP. An SOP documents *how the50**company** operates a recurring process*, no code required to understand it. Use the shared51three-way ops taxonomy in [`references/documentation-taxonomy.md`](../../references/documentation-taxonomy.md)52(playbook / runbook / SOP) plus the usual product-docs cases.5354Rule of thumb (from the taxonomy): if a **software engineer must understand it to execute it**,55it is not an SOP — it is a runbook (or an ADR). If they must **choose among branches** first,56it is a playbook — never a runbook, post-mortem, or SOP. Promote a playbook to an SOP only once57the work is a recurring company process with no engineering context required. If it fails the58routing test, tell the user which type it actually is and stop — do not force a non-process into59the SOP template.6061If the type is ambiguous, run `/document-this` to resolve it before continuing.6263### Paso 2 — Depth by maturity6465Ask (or infer) the process's stage; it decides which sections are required:6667| Stage | Required sections | `TBD` allowed? |68|---|---|---|69| **Draft / proposed** | Header, 1 Purpose, 2 Scope, 3 Audience, 6 Process (outline), 11 Revision History | Yes, freely |70| **In rollout** | + 5 Roles; Process fully documented | Edge cases only |71| **Active production** | All sections; no `TBD` in the procedure | No |7273This calibration mirrors how `/project-takeover` scales document detail to risk level — here it74scales to process maturity.7576### Paso 3 — Author the SOP77781. Read the template: `${CLAUDE_PLUGIN_ROOT}/references/05-operational-sop-template.md`792. Load inputs if present: `{slug}-capture.md` (the steps) and `{slug}-triage.md` (the verdicts).803. Fill each required section. Apply the template's writing discipline:81 - **Name owners by role, not person** ("Head of Support", not "Fer") so the SOP survives turnover.82 - **Real tool names, real numbers, real thresholds** — days of lead time, dollar amounts, volumes.83 - **Sequential, testable steps** — Step 4 executable only after Step 3.84 - **Tables** for anything with more than three parallel items (roles, phases, tools).85 - **Callouts** for what the reader must not miss: `> DECISION POINT`, `> SCALE NOTE`,86 `> LESSON LEARNED`.87 - In **Section 6**, structure phases with **Owner / Duration / Gate to next phase**.884. Write to `{sops-dir}/{slug}/{slug}-sop.md`.8990### Paso 4 — Executable mode (when automatable)9192If `{slug}-triage.md` contains any `RPA` or `AI agent` / `Human + AI` verdict, ALSO emit a runnable93executable SOP:94951. Read the template: `${CLAUDE_PLUGIN_ROOT}/references/06-executable-sop-skill-template.md`962. Build the frontmatter: `name`, a `description` with the run trigger, and `required_tools` —97 the MCP tools the RPA/AI steps call.983. Turn the procedure into numbered executable steps, attaching gate markers by verdict:99 - `Human` / `Human + AI` step → `[APPROVAL REQUIRED]`; outward-facing or irreversible actions100 (sends email, moves money, deletes data) → `[PRE-APPROVAL REQUIRED]`.101 - `RPA — attended` → runs with a human trigger; `RPA — unattended` / `AI agent` → no gate.102 - Conditional steps → `[OPTIONAL]`.1034. State in the doc that the markdown is authoritative (edit steps = change behavior) and that human104 gates are structural. Reference the JSONL run log.1055. Write to `{sops-dir}/{slug}/{slug}-sop.skill.md`.106107If every verdict is `Human`, skip this step — a purely human process needs no executable form. Say so.108109### Paso 5 — Quality checklist + bus test110111Before finishing, run the checklist from the template (routing / structure / content / cross-reference)112and the **bus test**: "if I got hit by a bus tomorrow, could a teammate read this SOP and run the113process?" If no, add detail — vague steps, unnamed owners, and missing thresholds are the usual gaps.114115### Paso 6 — Confirmación116117Present the deliverables and how to use them:1181191. `{slug}-sop.md` → "The operational SOP — the human-readable source of truth."1202. `{slug}-sop.skill.md` (if emitted) → "The runnable version — an LLM runtime executes it, pausing at121 the approval gates. The markdown is authoritative; edit the steps to change behavior."122123**Suggested next step:**124> "Keep the SOP a living document: bump the version when the process changes, and re-run125> `/automation-triage` when a step's volume or tooling shifts enough to change its verdict."126127## Notas para el modelo128129- This skill is the general-purpose SOP engine. `/project-takeover` is a *specialized* SOP producer130 (project handovers) — this one handles any operational process.131- The executable form is only emitted when triage says a step is automatable. Do not fabricate132 automation for a process that is genuinely all-human.133- The SOP is the source of truth for *what exists today*; keep improvement ideas in the open-questions134 list, not silently baked into the steps.135- Personalization is about ELIMINATING sections that do not apply at the current maturity, not adding136 unnecessary complexity — same discipline `/project-takeover` uses when pruning its templates.137- Use the Acme universe for examples (e.g. "AcmeLegal client-intake SOP", "RapidEats refund SOP").