AI Product Documentation Workflow

I'm auditing documentation for [product]. Here are our top 20 support tickets from last month: [list]. Current docs cover: [list topics]. Identify: gaps where docs don't address common questions, sections likely outdated based on support patterns, and priority order for new content based on ticket volume.

Design the information architecture for [product] documentation. User types: [list personas]. Organize into: Getting Started guide, Feature documentation, API reference, Troubleshooting, and FAQ. For each section, list the pages needed and their hierarchy. Follow the Divio documentation system.

Write documentation for [feature]. Include: what it does (one paragraph), prerequisites, step-by-step instructions with code examples, expected results at each step, common errors and solutions, and a "next steps" section. Use second person ("you"). Mark where screenshots should be added with [SCREENSHOT: description].

Generate API documentation from this code/spec: [paste]. For each endpoint: HTTP method and path, description, request parameters with types and requirements, example request (cURL and JavaScript), success response with example, error responses, and rate limits if applicable.

Review this documentation page for: technical accuracy (would these steps actually work?), clarity (could a beginner follow this?), completeness (are any steps missing?), code sample correctness, and consistent formatting. Suggest improvements and flag any assumptions that should be explicit.