Document-This
Decides which type of operational document you need and routes you to the right authoring
skill. This is a dispatcher, not an author. It resolves the ambiguity of "I want to
document X" into a concrete type + home, then hands off.
The single source of truth for the taxonomy is
references/documentation-taxonomy.md. Read it first.
document-this → decides the type → routes to the matching authoring skill
Language rule
Questions and working notes are in English. The generated document follows the
engagement's working language (English default, Spanish for Costa Rica engagements).
Flujo del skill
Paso 1 — Load the taxonomy
Read references/documentation-taxonomy.md (three-way taxonomy + placement rule + quick decision tree).
Paso 2 — Ask what the user wants to document
Prompt for the source material in plain language: "I want to document X". Do not assume a
type. Capture the intent, not the file name (a file named runbook may really be a
playbook).
Paso 3 — Run the decision tree
Walk the tree from references/documentation-taxonomy.md:
- Does it require engineering/technical context to execute? (needs repo, code, infra)
- No → it is a recurring business process with no code required → SOP.
- Route:
/sop-authoring
- Home: corporate handbook / business brain.
- Yes → go to 2.
- Is the reader choosing among paths under uncertainty? (when/why, decision tree)
- Yes → Playbook. Route:
/playbook-authoring. Home: the unit/repo.
- No → a sequence of concrete steps → Runbook. Route:
/runbook-authoring.
Home: the repo/system.
Check the related-types table too (post-mortem, PDR, ADR, product docs, pentest) so you do
not force a non-ops document into an ops type.
Paso 3b — If organizing a site/handbook, use Diátaxis
If the goal is not a single doc but a site/handbook structure, route through Diátaxis
instead of the ops tree:
| Quadrant |
Need |
Typical ChimeraNext / monorepo content |
| Tutorials |
learning |
onboarding paths, "get started" guides |
| How-to guides |
solving a task |
"how to open a PR", "how to deploy", runbooks, playbooks |
| Reference |
look-up |
SOPs, API refs, config schema, glossary |
| Explanation |
understanding |
why shared-services LLC, decision records, post-mortems |
Assign each page to exactly one quadrant; split pages that mix quadrants. Recommend
Docusaurus as the platform (recommended, not enforced).
Paso 4 — Name the type, home, and handoff
Present:
- The type (SOP / playbook / runbook).
- The canonical home (handbook/brain vs unit/repo) with a one-line reason.
- The authoring skill to use and its output location expectation.
- A clear routing statement: e.g. "This is a playbook — run
/playbook-authoring; it
lives in the repo's playbooks/."
Do not write the document yourself. If the user insists on authoring without switching skills,
tell them the correct authoring skill to invoke.
Notas para el modelo
document-this never authors. It only routes. If you find yourself writing the document,
you are doing the wrong thing — stop and delegate to the matching authoring skill.
- Do not invent a type. If the answer is genuinely ambiguous, ask one clarifying question
before routing.
- Use the Acme universe for examples (e.g. "AcmePay public-edge timeout playbook",
"RapidEats refund SOP").
- This skill is the entry point that makes the three-way taxonomy discoverable for
apprentices — it is intentionally thin.
1---2name: document-this3description: >4 Helps decide what KIND of operational document you should write — SOP, playbook, or5 runbook — and routes you to the right authoring skill. Use this skill when the user6 is unsure what to write: "what should this be", "SOP or playbook or runbook", "is7 this a runbook", "how do I document X", "qué tipo de documento", "¿SOP, playbook o8 runbook?", "what do I write", or any ambiguous "I want to document …" request.9 It is a thin dispatcher: it runs the three-way ops taxonomy routing, names the type10 and its canonical home, and hands off to /sop-authoring, /playbook-authoring, or11 /runbook-authoring. NOT an authoring skill itself — it never writes the document.12 NOT for security-test plans (that is /pentest-playbook-setup).13metadata:14 source: https://skillmd.com/skills/chimeranext/document-this15---1617# Document-This1819Decides which type of operational document you need and routes you to the right authoring20skill. This is a **dispatcher**, not an author. It resolves the ambiguity of "I want to21document X" into a concrete type + home, then hands off.2223The single source of truth for the taxonomy is24[`references/documentation-taxonomy.md`](../../references/documentation-taxonomy.md). Read it first.2526```27document-this → decides the type → routes to the matching authoring skill28```2930## Language rule3132Questions and working notes are in **English**. The generated document follows the33engagement's working language (English default, Spanish for Costa Rica engagements).3435## Flujo del skill3637### Paso 1 — Load the taxonomy3839Read `references/documentation-taxonomy.md` (three-way taxonomy + placement rule + quick decision tree).4041### Paso 2 — Ask what the user wants to document4243Prompt for the source material in plain language: "I want to document X". Do not assume a44type. Capture the *intent*, not the file name (a file named `runbook` may really be a45playbook).4647### Paso 3 — Run the decision tree4849Walk the tree from `references/documentation-taxonomy.md`:50511. **Does it require engineering/technical context to execute?** (needs repo, code, infra)52 - **No** → it is a recurring business process with no code required → **SOP**.53 - Route: `/sop-authoring`54 - Home: corporate handbook / business brain.55 - **Yes** → go to 2.562. **Is the reader choosing among paths under uncertainty?** (when/why, decision tree)57 - **Yes** → **Playbook**. Route: `/playbook-authoring`. Home: the unit/repo.58 - **No** → a sequence of concrete steps → **Runbook**. Route: `/runbook-authoring`.59 Home: the repo/system.6061Check the related-types table too (post-mortem, PDR, ADR, product docs, pentest) so you do62not force a non-ops document into an ops type.6364### Paso 3b — If organizing a site/handbook, use Diátaxis6566If the goal is not a single doc but a **site/handbook structure**, route through Diátaxis67instead of the ops tree:6869| Quadrant | Need | Typical ChimeraNext / monorepo content |70|---|---|---|71| **Tutorials** | learning | onboarding paths, "get started" guides |72| **How-to guides** | solving a task | "how to open a PR", "how to deploy", runbooks, playbooks |73| **Reference** | look-up | SOPs, API refs, config schema, glossary |74| **Explanation** | understanding | why shared-services LLC, decision records, post-mortems |7576Assign each page to exactly one quadrant; split pages that mix quadrants. Recommend77**Docusaurus** as the platform (recommended, not enforced).7879### Paso 4 — Name the type, home, and handoff8081Present:82- The **type** (SOP / playbook / runbook).83- The **canonical home** (handbook/brain vs unit/repo) with a one-line reason.84- The **authoring skill** to use and its output location expectation.85- A clear **routing statement**: e.g. "This is a playbook — run `/playbook-authoring`; it86 lives in the repo's `playbooks/`."8788Do not write the document yourself. If the user insists on authoring without switching skills,89tell them the correct authoring skill to invoke.9091## Notas para el modelo9293- `document-this` never authors. It only routes. If you find yourself writing the document,94 you are doing the wrong thing — stop and delegate to the matching authoring skill.95- Do not invent a type. If the answer is genuinely ambiguous, ask one clarifying question96 before routing.97- Use the Acme universe for examples (e.g. "AcmePay public-edge timeout playbook",98 "RapidEats refund SOP").99- This skill is the entry point that makes the three-way taxonomy discoverable for100 apprentices — it is intentionally thin.