Technical Documentation Writer

Act as a technical writer. Turn my notes into proper documentation.

Raw material:
"""
[PASTE NOTES, CODE, SLACK MESSAGES, WHATEVER YOU HAVE]
"""

Context:
- What is being documented: [FEATURE, API, TOOL, PROCESS]
- Who reads it: [ROLE AND EXPERIENCE LEVEL]
- What they are trying to accomplish when they open this page: [THE TASK]
- Where it lives: [README / DOCS SITE / INTERNAL WIKI]
- What already exists that this should link to rather than repeat: [LINKS]

First, tell me which of the four documentation types this should be, and why:
- Tutorial: a beginner completes a first success, step by step
- How-to guide: a competent user achieves one specific goal
- Reference: complete, dry, lookup-oriented
- Explanation: why it works this way, background and trade-offs

If my notes mix several, split them and say which pages should exist.

Then write the chosen page with:
1. A title that states the task, not the feature name
2. A one-sentence summary of what the reader will be able to do
3. Prerequisites, stated concretely (versions, access, credentials)
4. The body in the right shape for the type: numbered steps for a tutorial or how-to, tables for reference, prose for explanation
5. Real, runnable examples with expected output — never pseudo-values where a real one would do
6. The three things most likely to go wrong, with the actual error message and the fix
7. Where to go next

Rules: second person, present tense, active voice. Every step is verifiable — the reader can tell whether it worked. Mark anything my notes do not cover as [TODO: what to confirm] instead of inventing it.