[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-82277":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":15,"forks30d":15,"starsTrendScore":19,"compositeScore":20,"rankGlobal":10,"rankLanguage":10,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":24,"hasPages":22,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":26,"readmeContent":27,"aiSummary":28,"trendingCount":15,"starSnapshotCount":15,"syncStatus":29,"lastSyncTime":30,"discoverSource":31},82277,"procedure-ops","charlesdove977\u002Fprocedure-ops","charlesdove977","COO-in-a-box SOP builder for Claude Code. npm install (no clone) → sop-build skill ready in ~\u002F.claude\u002Fskills\u002F.","https:\u002F\u002Fgithub.com\u002Fcharlesdove977\u002Fprocedure-ops",null,"JavaScript",38,6,22,0,8,14,15,24,2.54,"MIT License",false,"main",true,[],"2026-06-12 02:04:24","\u003Cp align=\"center\">\n  \u003Cimg src=\"docs\u002Fhero.png\" alt=\"Procedure Ops — COO-in-a-box SOP builder for Claude Code\" width=\"900\">\n\u003C\u002Fp>\n\n# Procedure Ops\n\n> COO-in-a-box for [Claude Code](https:\u002F\u002Fclaude.ai\u002Fcode). Builds ironclad Standard Operating Procedures from interviews, screen-recording transcripts, or existing drafts — and pushes back on weak steps before they get written down.\n\n\u003Cp>\n  \u003Ca href=\"https:\u002F\u002Fwww.charlieautomates.com\u002Fcharlie-os-vs\u002F\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FWork_with_Charlie-Charlie_OS-7c3aed?style=for-the-badge&logo=anthropic&logoColor=white\" alt=\"Work with Charlie\">\u003C\u002Fa>\n  \u003Ca href=\"https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fprocedure-ops\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fnpm\u002Fv\u002Fprocedure-ops?color=blue&label=npm\" alt=\"npm version\">\u003C\u002Fa>\n  \u003Ca href=\"https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fprocedure-ops\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fnpm\u002Fdt\u002Fprocedure-ops?color=blue&label=downloads\" alt=\"npm downloads\">\u003C\u002Fa>\n  \u003Ca href=\"LICENSE\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fnpm\u002Fl\u002Fprocedure-ops?color=green\" alt=\"MIT license\">\u003C\u002Fa>\n  \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fcharlesdove977\u002Fprocedure-ops\u002Fstargazers\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Fstars\u002Fcharlesdove977\u002Fprocedure-ops?style=flat\" alt=\"stars\">\u003C\u002Fa>\n\u003C\u002Fp>\n\nProcedure Ops ships the **`sop-build`** skill: a structured, opinionated SOP author that captures *what* you do, *who* it is for, *how* to escalate when it breaks, and *which* steps belong on Zapier \u002F Make \u002F n8n \u002F a Claude managed agent instead of in a human's hands.\n\nDesigned for founders, agency operators, and team leads who need to delegate cleanly the first time — not the third time after the VA has already broken three clients.\n\n---\n\n## Why\n\nMost SOPs fail because they were written by the person who already knows the process. The result: fuzzy verbs (\"review the form\"), missing escalation paths, hidden judgment calls, and zero automation flagging. The delegate hits Step 3, gets stuck, messages you, and the SOP becomes a paperweight.\n\nProcedure Ops fixes that by acting like a COO during the build:\n\n- **Challenges weak inputs.** \"Review the form\" → \"Which fields? What does pass vs. fail look like?\"\n- **Names the escalation contact.** Single person, single channel. No \"ask the team.\"\n- **Flags automation candidates inline.** Every step gets the three-question filter (deterministic trigger \u002F known I\u002FO \u002F judgment required) and a tool recommendation when it passes.\n- **Routes the automation work cleanly.** When a step is automatable, the SOP points the user at the right next skill (`\u002Fseed:tasks:ideate` for scoping, `\u002Fpaul:plan` for build).\n- **Quality-gates before writing the file.** Built-in checklist catches \"obviously,\" missing Looms on UI-heavy steps, undefined jargon, and dangling `if X` conditions.\n\n---\n\n## Install\n\n### Option 1 — `npx` (recommended)\n\n```bash\nnpx procedure-ops install\n```\n\nInstalls the skill to `~\u002F.claude\u002Fskills\u002Fsop-build\u002F`. Run again with `update` to refresh after a package upgrade:\n\n```bash\nnpm view procedure-ops version          # check the latest published version\nnpx procedure-ops@latest update         # refresh in place\n```\n\n### Option 2 — Global install\n\n```bash\nnpm install -g procedure-ops\nprocedure-ops install\n```\n\nAfter global install, the `procedure-ops` command is on your `$PATH` and runs without `npx`.\n\n### Option 3 — Install directly from GitHub\n\n```bash\nnpx github:charlesdove977\u002Fprocedure-ops install\nnpx github:charlesdove977\u002Fprocedure-ops install --with-commands   # explicit slash commands too\n```\n\n`npx` clones the repo on the fly and runs the bundled CLI. Useful if you want to pin to a specific commit or test an unreleased branch.\n\n### Project-scoped install (per repo)\n\nInstall into a single project's `.claude\u002Fskills\u002F` instead of your user-wide directory:\n\n```bash\ncd ~\u002Fpath\u002Fto\u002Fproject\nnpx procedure-ops install --project\n```\n\nUseful when you want the skill scoped to one client repo, or pinned to a specific version per project.\n\n### Install command stubs\n\nBy default only the skill is installed; the slash command `\u002Fsop-build` is exposed by the skill itself. If you also want explicit slash commands per task (`\u002Fsop-build-interview`, `\u002Fsop-build-audit`, etc.), add `--with-commands`:\n\n```bash\nnpx procedure-ops install --with-commands\n```\n\nThis drops six stub `.md` files into `~\u002F.claude\u002Fcommands\u002F` (or `.\u002F.claude\u002Fcommands\u002F` with `--project`).\n\n### Uninstall\n\n```bash\nnpx procedure-ops uninstall\nnpx procedure-ops uninstall --with-commands   # also remove command stubs\n```\n\n### Where does it install?\n\n```bash\nnpx procedure-ops where           # ~\u002F.claude\u002Fskills\u002Fsop-build\nnpx procedure-ops where --project # .\u002F.claude\u002Fskills\u002Fsop-build\n```\n\n---\n\n## CLI reference\n\n```\nprocedure-ops \u003Ccommand> [flags]\n\nCommands:\n  install         Install the sop-build skill\n  update          Reinstall (overwrites existing)\n  uninstall       Remove the skill\n  where           Print the install path\n  --help, -h      Show help\n  --version, -v   Show version\n\nFlags:\n  --project           Use .\u002F.claude\u002F instead of ~\u002F.claude\u002F\n  --with-commands     Also install slash command stubs\n  --update, --force   Overwrite an existing install (implied by `update`)\n```\n\n---\n\n## Usage\n\nOnce installed, the skill is reachable from Claude Code as `\u002Fsop-build` plus a task name. All five tasks below run inside an active Claude Code session.\n\n### `\u002Fsop-build interview`\n\nGuided Q&A intake. Captures a process from scratch in 10 phases — routing, anatomy, step-by-step capture with COO push-back, reference docs, automation flagging, edge cases, checklist build, quality gate, file write, next-step suggestions.\n\nThe interview also auto-fires on natural language: \"write an SOP for X,\" \"document this process,\" \"delegate this to my VA,\" \"I keep redoing this.\"\n\n### `\u002Fsop-build scaffold-business`\n\nOne-time setup for a new business. Creates `SOPs\u002F\u003Cslug>\u002F{support,operations,onboarding,sales,finance,marketing,tech-it,compliance-legal}\u002F` and registers the business in `SOPs\u002FINDEX.md`. Defaults are configurable per-business.\n\n### `\u002Fsop-build from-recording`\n\nConverts a screen-recording transcript (Loom, Read.ai, otter, manual) into a structured SOP. Pulls steps, tools, exceptions, and gotchas from the transcript, then runs the same quality gate as `interview`.\n\n### `\u002Fsop-build audit`\n\nReviews an existing SOP file against the canonical anatomy, the delegation-ready checklist, and the automation-readiness checklist. Produces a severity-tagged report (🔴 Critical \u002F 🟡 Warning \u002F 🟢 Suggestion). Optional: write a revised version alongside the original.\n\n### `\u002Fsop-build delegate-pack`\n\nBundles a finished SOP into a handoff packet for a VA, contractor, or new hire. Includes access list, Loom\u002Ftraining inventory, first-week check-in cadence, escalation path, and success criteria.\n\n---\n\n## What gets installed\n\n```\n~\u002F.claude\u002Fskills\u002Fsop-build\u002F\n├── SKILL.md\n├── tasks\u002F\n│   ├── interview.md\n│   ├── scaffold-business.md\n│   ├── from-recording.md\n│   ├── audit.md\n│   └── delegate-pack.md\n├── frameworks\u002F\n│   ├── sop-anatomy.md           ← canonical SOP structure\n│   ├── automation-flagging.md   ← Zapier \u002F Make \u002F n8n \u002F managed-agent routing\n│   ├── raci-matrix.md           ← multi-actor accountability\n│   └── swim-lane-format.md      ← Mermaid swim-lane diagrams\n├── checklists\u002F\n│   ├── sop-ready-to-delegate.md\n│   ├── automation-readiness.md\n│   └── handoff-completeness.md\n└── templates\u002F\n    ├── sop-document.md\n    ├── delegate-packet.md\n    ├── sop-audit-report.md\n    └── interview-transcript.md\n```\n\nSOPs themselves are written to your *project*, not into the skill folder. Default location: `\u003Crepo-root>\u002FSOPs\u002F\u003Cbusiness-slug>\u002F\u003Cdepartment-slug>\u002F\u003Csop-slug>.md`.\n\n### Where the team actually reads the SOPs\n\nLocal markdown is fine for engineers but useless to a VA. When you scaffold a new business, Procedure Ops asks where the team will READ these SOPs day-to-day:\n\n- **Local markdown only** — Technical teams, git-based workflow. Zero setup.\n- **Google Drive (Google Docs)** — Easiest for VAs and non-technical hires. Markdown stays the source of truth; Drive gets a published copy. If you have the [`gws`](https:\u002F\u002Fgithub.com\u002F) CLI, Procedure Ops can call `gws docs create --from-markdown` to mirror per SOP.\n- **Notion** — Team wiki with database properties (Business \u002F Department \u002F Owner \u002F Status). Best when the team already lives in Notion. Procedure Ops uses the `notion-create-database` skill (if installed) to scaffold the schema.\n- **Both** — Drive for VAs, Notion for the internal team.\n\nThe choice is per-business and sticky — saved to `SOPs\u002F\u003Cbusiness>\u002FREADME.md` under a `## Hosting` section. Future SOP writes honor it without re-asking. See [`skill\u002Fframeworks\u002Fhosting-options.md`](skill\u002Fframeworks\u002Fhosting-options.md) for the full pattern.\n\n---\n\n## SOP anatomy\n\nEvery SOP that Procedure Ops writes follows the same nine-section structure:\n\n1. 🔗 **Reference Documents** — Linked Notion docs, source recordings, training videos, prerequisite SOPs\n2. 🎯 **Purpose** — One paragraph: what this teaches, who benefits, why it matters\n3. 👥 **Who This SOP Is For** — Role titles, never personal names\n4. 🧠 **Overview** — Plain-language context, systems involved, where it fits in the bigger process\n5. 🪜 **Step-by-Step Process** — Numbered steps with concrete actions, confirmation criteria, branches, automation callouts, Loom placeholders\n6. 🗂️ **Checklist Before Marking Complete** — Flat checklist mirroring step outcomes\n7. 🧠 **Notes & Reminders** — Gotchas, recurring failure modes, \"never do X until Y\"\n8. 📞 **Escalation** — Owner + escalation contact + when-to-escalate conditions\n9. 📅 **Metadata** — Business, department, created date, version, author\n\nSee [`skill\u002Fframeworks\u002Fsop-anatomy.md`](skill\u002Fframeworks\u002Fsop-anatomy.md) for the full spec, anti-patterns, and style rules.\n\n---\n\n## Automation flagging\n\nWhen a step looks automatable during the interview or audit, Procedure Ops runs it through a three-question filter and recommends the right tool:\n\n| Q1 — Deterministic trigger? | Q2 — Known I\u002FO? | Q3 — Judgment required? | Verdict |\n|---|---|---|---|\n| Yes | Yes | No | ✅ Workflow tool (Zapier \u002F Make \u002F n8n) |\n| Yes | Yes | Yes | ✅ Claude managed agent (judgment in the loop) |\n| Yes | No | — | 🟡 Map I\u002FO first |\n| No | — | — | ❌ Manual — needs human decision to start |\n\nEach flagged step gets an inline callout in the SOP:\n\n```markdown\n> 💡 **Recommended automation**\n> - **Tool:** Make\n> - **Trigger:** New row in Google Sheet `Onboarding Queue`\n> - **Inputs:** Client name, email, signed-contract URL\n> - **Outputs:** Asana subtask created, Slack message posted to #ops\n> - **Next step:** Run `\u002Fseed:tasks:ideate` to scope. Then `\u002Fpaul:plan` to build.\n```\n\nProcedure Ops never builds the automation itself — that is a deliberate handoff to two other Claude Code skills by [Christopher Kahler](https:\u002F\u002Fgithub.com\u002FChristopherKahler):\n\n- **[SEED](https:\u002F\u002Fgithub.com\u002FChristopherKahler\u002Fseed)** — AI project incubator. Turn a flagged step into a scoped workflow concept (trigger, data flow, tool selection, edge cases) before committing to build.\n- **[PAUL](https:\u002F\u002Fgithub.com\u002FChristopherKahler\u002Fpaul)** — Plan \u002F Apply \u002F Unify loop. Once SEED has a clear spec, PAUL phases the implementation, tracks milestones, and ships.\n\n**Procedure Ops only recommends installing SEED + PAUL if they are missing from your machine.** The skill checks `~\u002F.claude\u002Fskills\u002Fseed\u002F` and `~\u002F.claude\u002Fskills\u002Fpaul\u002F` before emitting any handoff language. If both are already installed, you just get a clean `\u002Fseed:tasks:ideate` → `\u002Fpaul:plan` → `\u002Fpaul:apply` chain in the SOP — no install noise. If one is missing, the SOP callout includes the exact `git clone` line for the missing skill.\n\nInstall if needed:\n\n```bash\n# SEED\ngit clone https:\u002F\u002Fgithub.com\u002FChristopherKahler\u002Fseed.git ~\u002F.claude\u002Fskills\u002Fseed\n# PAUL\ngit clone https:\u002F\u002Fgithub.com\u002FChristopherKahler\u002Fpaul.git ~\u002F.claude\u002Fskills\u002Fpaul\n```\n\nProcedure Ops captures the SOP first; SEED + PAUL handle the build.\n\n---\n\n## Why a skill, not a library\n\nProcedure Ops is distributed as a Claude Code skill rather than a TypeScript\u002FPython library because the actual work — challenging vague answers, pushing back on missing escalation contacts, generating Mermaid swim-lanes — is conversational. A library would just be a markdown template. Claude is the COO; this package gives Claude the playbook.\n\nThe `procedure-ops` CLI exists only to put the playbook files in the right directory.\n\n---\n\n## FAQ\n\n**Does it run without an internet connection?**\nThe CLI install does not need the network after `npm install`. The skill itself runs inside Claude Code, which does require connectivity.\n\n**Does it work outside Claude Code?**\nThe skill files are plain markdown. You can read them and apply the playbook manually — but the COO behavior is in Claude's hands. There is no standalone runtime.\n\n**Does it touch my repo when I install?**\nNo. The default install writes to `~\u002F.claude\u002Fskills\u002Fsop-build\u002F`, which is your user-wide Claude Code config directory. Only `--project` writes into the current directory.\n\n**How do I update the skill after publishing changes to my SOPs?**\nSOPs live in your project, not in the skill folder. Updating the skill (`npx procedure-ops update`) never touches your `SOPs\u002F` directory.\n\n**Can I customize the skill after installing?**\nYes — the installed files are yours. Edit anything in `~\u002F.claude\u002Fskills\u002Fsop-build\u002F`. The next `update` will overwrite your edits, so consider forking the repo instead if you are making meaningful changes.\n\n---\n\n## Related projects\n\n- **[Charlie OS](https:\u002F\u002Fwww.charlieautomates.com\u002Fcharlie-os\u002F)** — one-click Claude Code setup that bundles BASE, CARL, PAUL, SEED, Skillsmith, and 32 curated skills. If you want Procedure Ops *plus* the rest of Charles's stack on day one, install Charlie OS instead.\n- **[Work with Charlie](https:\u002F\u002Fwww.charlieautomates.com\u002Fcharlie-os-vs\u002F)** — done-for-you install, custom skill builds, and 1:1 Claude Code engineering for founders and agency operators.\n- **[SEED](https:\u002F\u002Fgithub.com\u002FChristopherKahler\u002Fseed)** — AI project incubator skill.\n- **[PAUL](https:\u002F\u002Fgithub.com\u002FChristopherKahler\u002Fpaul)** — Plan \u002F Apply \u002F Unify implementation loop skill.\n\n---\n\n## Contributing\n\nIssues + PRs welcome at [github.com\u002Fcharlesdove977\u002Fprocedure-ops](https:\u002F\u002Fgithub.com\u002Fcharlesdove977\u002Fprocedure-ops).\n\nWorkflow:\n\n1. Fork + clone\n2. Edit files under `skill\u002F`\n3. Smoke test with `npx . install --project` inside a scratch directory\n4. PR against `main`\n\nWhen the package version bumps, the skill version inside `skill\u002FSKILL.md` should match.\n\n---\n\n## License\n\nMIT — see [LICENSE](LICENSE).\n","Procedure Ops 是一个用于构建标准操作流程（SOP）的工具，专为 Claude Code 设计。其核心功能包括从访谈、屏幕录制转录或现有草稿中创建高质量的操作流程，并在步骤不明确时提供反馈。技术特点上，该项目使用 JavaScript 编写，支持通过 npm 安装，无需克隆仓库即可快速部署。它适合需要高效地将业务流程标准化并委托给团队成员的企业创始人、代理运营商及团队领导使用，特别是在首次委托任务时希望避免因流程不清晰导致的反复沟通和错误。",2,"2026-06-11 04:08:14","CREATED_QUERY"]