Documents team processes with quick reference checklists and detailed steps
/process-documentation2-3 hrs → 10 min
Compared to doing it manually
/process-documentationType this in Claude to run the skill
Processes live in people's heads. When they leave, the knowledge disappears. When someone new joins, they spend weeks figuring out how things work.
.claude/skills/ folder in your project/process-documentation in Claude to run the skill/sprint-retro-facilitatorStructures sprint retrospectives with prompts, synthesis, and action items
/customer-success-playbookCreate CS playbooks with plays for onboarding, adoption, renewal, and expansion.
/incident-post-mortemWrites a blameless incident post-mortem with root cause analysis
/team-health-checkRun structured team health checks to surface what is working and what is not.
Document processes that: happen repeatedly, involve multiple people, are critical to operations, or would be hard to reconstruct. Don't over-document — if it changes weekly, it's not ready for documentation.
Detailed enough that someone new could follow it, but not so detailed it becomes outdated immediately. Include the "why" not just the "what". Link to tools and templates rather than duplicating them.
Assign owners, review quarterly, and update when processes change. Embed documentation updates into the process itself. If docs are always outdated, you have too much documentation.
Run this skill inside your PM Operating System, or download it on its own.
Use all 70 skills, workflows, and sub-agents in a system that knows your company, product, and customers.