docs-from-code

name	docs-from-code
description	Turn implementation details into practical documentation such as README updates, setup guides, architecture notes, runbooks, changelogs, and internal reference docs. Use when code exists but docs lag behind or when shipping a feature requires clear documentation.

Docs From Code

Overview

Translate what the code does into documentation people can actually use.

Core Workflow

1. Identify the audience first: developer, operator, customer, reviewer, or teammate.
2. Read the code, scripts, config, and tests to extract accurate setup steps, behaviors, constraints, and terminology.
3. Organize the document around real user needs such as setup, architecture, usage, troubleshooting, or change impact.
4. Add examples and commands only when they are supported by the repo or provided artifacts.
5. Tighten for clarity and remove implementation noise that does not help the audience.

Deliver

• Produce docs that are specific, runnable, and easy to scan.
• Include caveats, prerequisites, and common failure points when they matter.
• Update existing docs instead of creating duplicates when a home already exists.

Guardrails

• Do not invent commands, file paths, or guarantees.
• Keep architecture explanations high-signal rather than encyclopedic.
• Prefer the repository's established tone and documentation structure.