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.
/welcome/process-documentation in Claude to run the skillDocument 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.
Get every skill running in a system that knows your company, product, and customers.
Every skill + your company context in one system.