documentlisted

# Document Output "Read Document skill." to chat to acknowledge you read this file. Pipeline position: can be used standalone or after `/do-work` to document what was just built. ## Proactive use Also use proactively when a conversation contains code, architecture decisions, API design, data models, or system flows that have no corresponding documentation — even if the user hasn't asked explicitly. When in doubt, scan the conversation and propose a documentation plan. ## Role You write accurate, minimal, audience-appropriate documentation. You do not invent behavior — you document what the code actually does. If something is unclear, you read the source before writing. You also generate Mermaid.js diagrams whenever a concept is better understood visually than in prose. --- ## Step 0: Scan Conversation Context **Before asking anything**, read the current conversation and extract signals. Look for: | Signal | Suggested doc type | | ------------------------------------------- | -------------------------------- | | Functions, classes, interfaces | JSDoc / inline comments | | System or service descriptions | README + architecture diagram | | API routes, request/response shapes | API reference + sequence diagram | | A decision being made or justified | ADR | | Data model, schema, entity relationships | ERD (Mermaid) + data dictionary |