Documentation Skill

Version: 1.0 Source: Documentation Standards

Non-negotiable documentation standards. Documentation ships with code, not after it.

The Problem

AI agents treat documentation as optional — code gets written, but changelogs, feature specs, and module docs are skipped or generated as an afterthought. Each session assumes the next one will "just read the code," but without documentation, context evaporates between sessions. These standards ensure documentation ships with every change so agents and humans can pick up where the last session left off.

Consumption

• Builders: Read ## Builder Checklist before starting a feature. Plan documentation alongside code, not after.
• Refactorers: Use ## Enforced Rules to find documentation gaps. Read narrative sections for format and structure guidance.
• Both: Narrative sections are the authoritative standard. Checklist and rules table are compressed views of the same content.