documentation

Write structured process documentation with steps, decision trees, and examples.

Updated May 23, 2026
One-click install
npx skills add https://github.com/TheGraphicKing/skott-canvas --skill documentation-thegraphicking
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: documentation
Source: https://github.com/TheGraphicKing/skott-canvas/tree/main/skills/documentation
Command: npx skills add https://github.com/TheGraphicKing/skott-canvas --skill documentation-thegraphicking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams lose critical knowledge when processes live only in one person's head, causing onboarding delays, recurring errors, and key-person dependency. This Skill produces structured process documentation that any team member can follow without help from the original author. ## Core Features & Use Cases - Standard Document Structure: Generates documents with purpose, owner, frequency, prerequisites, numbered steps, decision points, common mistakes, examples, and version history. - Decision-Tree Logic: Converts branching conditional steps into explicit if/then formats so judgment calls are never buried in prose. - Review Cadence Management: Adds last-reviewed dates, next-review schedules, and triggers for unscheduled reviews to keep documents current. - Use Case: When onboarding a new marketing coordinator, use this Skill to document the lead-routing process end-to-end, including score-based decision branches and common mistakes, so the new hire can execute it independently on day one. ## Quick Start Document our monthly newsletter send process, including prerequisites, step-by-step instructions, decision points for list segmentation, and common mistakes to avoid.

Frequently Asked Questions about documentation

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

FAQPage Schema
How do I write process documentation that anyone can follow?▼

Structure the document with purpose, owner, frequency, prerequisites, numbered steps, decision points, common mistakes, and examples. Write one action per step starting with a verb, and include expected outcomes for steps that could fail silently.

How to document a process that has conditional branching steps?▼

Use explicit if/then decision-tree formatting for every conditional step, such as routing actions based on a score threshold. Never bury conditional logic in paragraph prose, since readers consistently miss it.

What should a standard process document template include?▼

Include purpose, owner, frequency, prerequisites, numbered process steps, decision points, common mistakes, a worked example, related upstream and downstream processes, and a version history table with dates and authors.

How do I capture an undocumented process from a current owner?▼

Walk through the process step by step with the owner, asking what they check before starting, which tools they open, what can go wrong, where exceptions occur, and at which points they make judgment calls.

How often should process documentation be reviewed and updated?▼

Review active processes quarterly and stable ones semi-annually, recording last-reviewed and next-review dates in the document header. Trigger an unscheduled review when tools change, team structure changes, or an error is traced to the process.