Write Documentation

Write accurate, user-focused documentation with real examples by executing operations through the user.

Principles

1. Execute-then-document: Never write examples without real output
2. Chunk-by-chunk: Write one section at a time, get confirmation before proceeding
3. User-focused: Write for users, not developers
4. Validate prerequisites: Run setup steps from existing docs to verify they work
5. Claude runs infrastructure, user runs MCP: Claude executes all bash/infrastructure commands. Only ask user for MCP client interactions (the actual user-facing examples).
6. Fix docs when broken: If existing docs don't work during setup, STOP and discuss updating those docs before proceeding.

Workflow

Step 1: Identify the Documentation Target