html-spec-planning

Generate navigable HTML documents for specs, RFCs, and implementation plans.

Updated May 5, 2026
One-click install
npx skills add https://github.com/ethan-rio/skills --skill html-spec-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: html-spec-planning
Source: https://github.com/ethan-rio/skills/tree/main/skills/html/html-spec-planning
Command: npx skills add https://github.com/ethan-rio/skills --skill html-spec-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Long-form markdown planning artifacts (specs, RFCs, implementation plans) longer than a screen fail to engage reviewers, are hard to navigate, and are poorly suited for feeding back to AI agents for subsequent implementation work.

Core Features & Use Cases

  • Navigable HTML Artifacts: Generates self-contained, mobile-responsive HTML files for specs, RFCs, design docs, brainstorms, and implementation plans that are shareable via link and easy for stakeholders to review.
  • Multiple Workflow Patterns: Supports three core use cases: single-direction decided specs, N-way option explorations with clear tradeoff comparisons, and multi-file linked doc sets for large, complex projects.
  • Real-World Use Case: When you need to document a new feature's implementation plan for cross-team review, or explore 3 architectural approaches for a service migration with pros and cons, this skill outputs a polished, accessible document instead of a long markdown file that stakeholders skip.

Quick Start

Request an HTML spec for the new payment processing feature, covering context, 3 implementation approaches with tradeoffs, and a final recommended plan.

Frequently Asked Questions about html-spec-planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert long markdown RFCs into navigable HTML documents?

You can create navigable HTML specs from markdown by generating self-contained, mobile-responsive files with semantic markup and inline assets. This skill converts lengthy planning artifacts into accessible HTML documents that stakeholders can easily review instead of skipping.

What is the best way to present architectural tradeoffs for a service migration?

Presenting architectural tradeoffs is best handled through N-way option explorations in an HTML spec. This skill outputs polished documents that clearly compare multiple implementation approaches with their pros and cons, enabling reviewers to evaluate tradeoffs efficiently.

Can I generate multi-file linked documentation sets for complex projects?

Yes, you can generate multi-file linked documentation sets for complex projects. This skill supports creating linked multi-file doc sets alongside single-direction specs and multi-option explorations to cover large technical planning workflows.

How do I create implementation plans that are suited for AI agent follow-up?

To create implementation plans suited for AI agent follow-up, generate navigable HTML artifacts instead of long markdown files. This skill produces self-contained, semantically marked HTML documents that agents can parse effectively and stakeholders can engage with.

Does the generated HTML require external dependencies to render correctly?

No, the generated HTML does not require external dependencies to render correctly. This skill produces self-contained files with inline assets, ensuring implementation plans and RFCs are shareable via link and display properly on mobile-responsive layouts.