Company Documentation System

Company Documentation System

Use this skill when the user wants to create, improve, audit, or maintain internal company documentation: a company handbook, team knowledge base, operating manual, onboarding guide, process library, policy hub, decision log, or cross-team source of truth.

This skill is for company and team knowledge. For codebase architecture, setup, deployment, testing, or API documentation, prefer a software documentation skill.

Core Judgment

Make documentation useful before making it complete.

Do not try to document everything. Build the smallest system that lets people answer real work questions faster, update the right page when something changes, and trust what they find.

Ask questions only when the missing answer changes the structure, audience, privacy boundary, or publishing target. Otherwise, make a reasonable first pass and call out assumptions.

What Good Looks Like

A good company documentation system is:

• easy to search and browse
• owned by clear teams or people
• current enough to be trusted
• explicit about what is public, internal, confidential, or restricted
• written in plain language
• organized around how people actually work
• easy for teammates to update
• honest about gaps, drafts, and uncertain information

First Pass

Before writing or changing docs, quickly identify:

• audience: employees, leadership, candidates, contractors, customers, partners, or a specific team
• scope: company-wide handbook, one team, one workflow, onboarding, policy, or cleanup
• destination: Markdown repo, wiki, Notion, Confluence, Google Docs, GitHub, or another tool
• visibility: public, internal, confidential, restricted, or mixed
• source material: existing docs, tickets, meeting notes, repo files, policies, chat summaries, or user-provided notes
• owner model: named owner, team owner, approver, or "needs owner"
• freshness model: review date, source-of-truth link, change log, or no maintenance expectation

If any of those are unknown but not blocking, proceed with placeholders such as Owner: TBD or Review cadence: TBD.