ericrisco/rsc-harness / skills/sop-builder
sop-builder
VerifiedUse 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 stale, ignored or missing its branches. NOT capturing a meeting's decisions and action items (that is `meeting-notes`), NOT running a one-time project plan with milestones (that is `project-ops`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.2 KB |
| evals/README.md | markdown | 977 B |
| evals/cases.yaml | config | 3.3 KB |
| references/sop-skeleton.md | markdown | 6.7 KB |
evals/cases.yaml
View on GitHubskill: sop-builder
should_trigger:
- prompt: "Can you help me write an SOP for how we publish the weekly newsletter?"
why: Direct ask for the core artifact — a standard operating procedure for a recurring task.
- prompt: "Every time Maria goes on holiday the refund process breaks because nobody else knows how she does it."
why: Non-obvious. The bus-factor symptom of a process living in one head, with no SOP keyword present.
- prompt: "I recorded a Loom of me doing the month-end close — turn it into a written procedure."
why: The recording-as-source capture path; recording-to-SOP is a named fast path.
- prompt: "Documenta este proceso paso a paso para que cualquiera del equipo lo pueda hacer."
why: Spanish trigger — document this process step by step so anyone on the team can run it.
- prompt: "Our team does the client handoff differently every time and the results are inconsistent — standardize it."
why: Standardization-from-inconsistency symptom, no SOP keyword; the core when-to-use.
- prompt: "This SOP is two years old, nobody follows it, and it has no exception handling — fix it."
why: The audit/rewrite path — a stale SOP past the 18-month staleness line, missing its branches.
should_not_trigger:
- prompt: "Write up what we decided in today's standup and the action items."
route_to: meeting-notes
why: Recording a moment's decisions and actions, not documenting a repeatable procedure.
- prompt: "Build the project plan with milestones and owners for the Q3 launch."
route_to: project-ops
why: A one-time effort with an end date and milestones, not a recurring routine.
- prompt: "Write the help-center article explaining how customers reset their password."
route_to: technical-writing
why: External reader and product surface — a help doc, not an internal operating procedure.
- prompt: "Now automate this documented process with a webhook and a script."
route_to: automation-flows
why: Building the automation from steps, not capturing and writing the procedure.
- prompt: "Set up the new hire's first-week onboarding checklist and accounts."
route_to: people-ops
why: One specific employee's onboarding tracker, not the reusable procedure they follow.
capability:
- scenario: >
Given a messy transcript of someone describing how they triage and respond to
inbound sales leads — containing two hidden decision points (lead size routing,
and a "spam/not-a-real-lead" filter) and one exception (CRM is down) — produce
a usable SOP.
must_include:
- Picks the SOP altitude (who/what/when), not a keystroke-level work instruction.
- Names exactly one accountable owner and sets a next-review date.
- Chooses a format that matches the branching flow (decision table or flowchart with inline if/then), not a flat numbered list.
- Surfaces and writes BOTH decision branches explicitly (lead-size routing and the spam filter).
- Writes the exception with a named escalation target and a stop/proceed condition (CRM down).
- Writes steps in active voice with one action each and a named actor.
- Includes a change-log / version stub.
- Does NOT invent steps absent from the source transcript; flags gaps instead of backfilling.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |