User Documentation

---
name: user-documentation
description: Create task-oriented user documentation that explains current product behavior with prerequisites, steps, examples, troubleshooting, and expected results.
---
# User Documentation

Use for setup guides, how-to articles, help-center pages, tutorials, and operator instructions.

## Procedure
1. Identify the user's goal and minimum prerequisite knowledge.
2. Verify the current product behavior before documenting it.
3. Put prerequisites and required permissions before the procedure.
4. Write steps in execution order with exact labels, commands, paths, or examples where they matter.
5. State the expected result at important checkpoints.
6. Add troubleshooting for common, evidenced failure modes rather than speculative edge cases.
7. Test the instructions from a clean starting point when practical.

## Quality gate
A new user should be able to complete the task without access to internal conversations, implementation notes, or tribal knowledge.