expertise-to-procedure — turn "what I know" into "what the system knows"

Purpose: Capture how an expert actually performs a task and freeze it into a durable, reusable asset (playbook, checklist, or skill) so the procedure is repeatable, auditable, and not lost when the person leaves.

⚠️ Critical Constraints

• Capture the REAL procedure, not the sanitized one. Experts narrate the tidy version and skip the judgment calls. Why: the skipped steps (the "obviously you'd check X first") are exactly the tacit knowledge you are here to extract; the clean version is already in the docs and helps no one.

  • WRONG: "Step 3: review the config." (what does review mean here?)
  • CORRECT: "Step 3: grep the config for replicas:; if < 3 in prod, STOP and escalate — that's the failure that caused last quarter's outage."

• Encode decisions, not just steps. A linear recipe rots; the value is the branch points. Why: a checklist that can't say "if X then Y, else Z" loses the expert's judgment, which is the whole asset.