Stop Guessing, Start Documenting

Most AI agents write documentation by simply paraphrasing what you tell them. This leads to "hallucinated" docs that drift from reality the moment your code changes. This skill implements a rigorous, 5-phase engineering workflow specifically designed for developer-centric documentation.

What it does

This skill guides your AI agent through a structured process to create high-leverage technical assets. It forces the agent to verify every technical claim against your actual source code using grep and file reads before writing a single line of prose. It supports a variety of formats including:

• CLAUDE.md: Context-steering files that improve every future AI session.
• Architecture Decision Records (ADR): Capturing the "why" behind complex changes.
• Runbooks: Actionable, verified steps for incident response.
• READMEs & API Docs: Technical guides that match actual function signatures.

Why this is better than manual prompting

Standard prompts often result in "docstring sprawl"—verbose text that just repeats the code's method names. This skill enforces a "Structure First" mandate via Plan Mode, ensuring you approve an outline before the agent spends tokens on prose. It prioritizes documenting intent over implementation, creating docs that actually age well.