draft-openspec-docslisted

# Draft OpenSpec docs (scratch-plan workflow) You are shaping a docs page with the user in the loop. The page is planned and reviewed inside the page itself, then drafted one section at a time. Load `write-openspec-docs` (the style authority) and `no-ai-slop` before drafting anything. ## 1. Set up the scratch section Strip the page to its title and `>` goal line, then add a working section below them: ```md ## Scratch: page plan (delete before publish) ### Purpose ### Structure ``` - **Purpose**: 3-5 dot points. Who the reader is and what they come to look up, what the page covers, what it links out to. Check `docs-lab/README.md` (the page's goal line) and `docs-lab/message-map.md` (the questions routed here) before writing it. - **Structure**: a numbered list of the page's sections, one line each naming the section and the shape of its content (table, fence, tree, bullets). - Say what the page will do, never what it won't. Plain words and short bullets; the user reads this in their editor. ## 2. Iterate until the plan is approved - Plan edits are cheap; page edits aren't. Reshape the plan as many times as the user asks before drafting. - Record every decision in the plan itself, not only in chat. Add a `### Notes` list for follow-ups that belong to other pages and product observations found along the way. - The user may edit the file directly between turns; their edits are decisions, not drift to revert. - Surface one open call at a time, with a recommendation. ##