HTML Spec, Planning & Exploration

Use HTML as the working surface for thinking through problems — brainstorms, alternative explorations, mockups, and implementation plans. Markdown specs over ~100 lines stop getting read; HTML specs get read because they're navigable, visual, and shareable as a link.

When to use this skill

• "Write a spec / RFC / design doc / proposal for X"
• "I'm not sure how to approach X — explore the options"
• "Make me an implementation plan for X"
• "Brainstorm approaches to X"
• "Lay out the tradeoffs for X"
• Whenever the planning artifact will be reviewed by humans, or later read by another Claude session for implementation

Output requirements

Save with a descriptive filename like <topic>-spec.html or <topic>-plan.html so multiple planning artifacts on one project compose into a readable folder rather than colliding on output.html.

HTML output foundation