visualise-planlisted

# Implementation plan The user has just finished walking you through what they want to build. You probably know more about this feature right now than at any later point in the conversation. Your job is to **freeze that understanding into a single HTML document** they can scroll through on a phone or laptop, push back on, and only then green-light. You are not implementing yet. You are not allowed to implement yet. ## When this skill runs By the time this skill triggers, the user has already answered the questions you needed answered — about the feature's behavior, constraints, edge cases, scope. **Do not re-interrogate them.** If something genuinely critical is missing, write the plan with your best assumption, flag the assumption in the Future scope section, and let the user correct you in their review pass. Asking another round of questions before producing the plan defeats the point of the skill. ## What you produce A single self-contained HTML file at: ``` docs/plan/<feature-slug>.html ``` `<feature-slug>` is a short kebab-case name for the feature (e.g. `comment-threads`, `bulk-export`, `oauth-pkce`). If the user gave you a name, use theirs. The file is self-contained: no external CSS, no external JS, no image hosts. Everything inline. The reviewer should be able to open it offline. A starter template lives at `references/template.html` in this skill. **Read it before writing.** It defines the visual style — the Botanical Almanac aesthetic (deep forest-green i