process-docs

Document recurring internal processes into SOPs, runbooks, and onboarding playbooks.

285|39|Updated Mar 16, 2026

Search Tags:#workflow #documentation #onboarding #process #runbook #sop

Ready to run

npx skills add https://github.com/shawnpang/startup-founder-skills --skill process-docs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: process-docs
Source: https://github.com/shawnpang/startup-founder-skills/tree/main/skills/process-docs
Command: npx skills add https://github.com/shawnpang/startup-founder-skills --skill process-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardize undocumented, recurring internal processes into repeatable SOPs, runbooks, and onboarding playbooks.

Core Features & Use Cases

Create SOP templates and runbooks for routine operations.
Generate onboarding playbooks to accelerate new-hire ramp-up.
Map ownership, steps, decision points, escalation, and review cadence into runnable workflows.

Quick Start

Describe the process you want documented in a brief, high-level form to generate a complete SOP or runbook.

Frequently Asked Questions about process-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I document recurring internal processes into repeatable SOPs?▼

To document recurring internal processes into repeatable SOPs, provide a high-level description of the workflow. This generates a complete SOP mapping ownership, steps, decision points, escalation paths, and review cycles.

What is the best way to create onboarding playbooks for new hires?▼

Creating onboarding playbooks involves mapping routine operations and internal processes into structured templates. This defines clear inputs, outputs, and actionable guidance to accelerate new-hire ramp-up.

How do I build a runbook that includes escalation paths and decision points?▼

Building a runbook with escalation paths requires defining process ownership, operational steps, and failure handling. Describing the workflow generates a template with structured metadata and actionable guidance.

Can I turn tribal knowledge into structured process templates automatically?▼

Yes, you can turn tribal knowledge into structured process templates by briefly describing the undocumented workflow. This transforms high-level process descriptions into standardized, runnable documentation.

What should an SOP include for failure handling and review cycles?▼

An SOP for failure handling should include clear inputs, outputs, escalation paths, and defined review cadence. Structuring these elements ensures the runbook provides actionable guidance during operational failures.

Does creating process documentation require predefined templates or components?▼

No, creating process documentation does not require predefined templates or components. Supplying a brief high-level process description is sufficient to generate a complete SOP with structured metadata and ownership.