html-plan — Claude Code skill: what it does, how to install
Turns project notes and requirements into a self-contained HTML plan. Useful for organizing phases, dependencies, and owners without turning the doc into a dashboard.
npx skills add plannotator/effective-html --skill html-plan -a claude-codeWhat html-plan does
This skill converts unstructured discussion notes, tasks, and project constraints into an inspectable HTML document. It keeps original commitments and terms while clarifying work sequence and boundaries. Decisions, assumptions, and open questions are separated explicitly. Tables handle direct mappings, while long prose stays readable instead of being split into decorative cards.
The output is a single responsive HTML file with semantic markup. Essential CSS and JavaScript are strictly inline, avoiding third-party services. The skill requires checking the document across narrow and wide viewport widths, confirming that dependencies remain clear and content does not overflow. It then reports the absolute path to the generated file.
This specialist tool runs only on direct user invocation or routing from a general html skill. It refuses to invent progress bars, status badges, or timelines unless the source material actually defines them.
What it helps with
- convert unstructured project notes into a clean HTML plan
- map owners, dependencies, and verification checks into one document
- isolate accepted decisions from working assumptions and open questions
- generate a self-contained responsive plan without external assets
Example prompts for the agent
- Use html-plan to turn our sprint discussion into an HTML plan
- html-plan: organize the database migration steps and their dependencies
- Convert this task outline into a single-file HTML document using html-plan
How to install html-plan
1Skills CLI (Vercel)
npx skills add plannotator/effective-html --skill html-plan -a claude-code2Manually: put the files in place
~/.claude/skills/html-plan/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/html-plan/
1Skills CLI (Vercel)
npx skills add plannotator/effective-html --skill html-plan -a codex2Manually: put the files in place
.agents/skills/html-plan/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add plannotator/effective-html --skill html-plan -a cursor2Manually: put the files in place
.cursor/skills/html-plan/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install plannotator/effective-html html-plan2Manually: put the files in place
.github/skills/html-plan/SKILL.md1Skills CLI (Vercel)
npx skills add plannotator/effective-html --skill html-plan -a gemini-cli2Platform CLI
gemini skills install https://github.com/plannotator/effective-html --path skills/html-planManually: put the files in place
.devin/skills/html-plan/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add plannotator/effective-html --skill html-plan -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set3
The whole set →Similar
Questions about html-plan
How do I install html-plan in Claude Code?
Run npx skills add plannotator/effective-html --skill html-plan -a claude-code in your terminal.
What does the html-plan skill do?
It turns raw discussion notes and task requirements into a structured, self-contained HTML document with clear phases, owners, and risks.
Does the generated HTML require external libraries?
No. The skill packages all necessary styles and scripts inline inside a single file, avoiding calls to external services.
Source text
SKILL.md · MIT
--- name: html-plan description: Direct-invocation specialist for clear, self-contained HTML plans that preserve source material while improving hierarchy, sequence, ownership, dependencies, and reviewability. Use when the user explicitly invokes html-plan or the broad html skill routes a plan request here. Do not activate independently from a general request. --- # HTML Plan Turn source material into a plan people can inspect and act on. Preserve the user's scope, ordering, commitments, and terminology unless they ask for broader synthesis. ## Shape the document around the work Read the conversation, project instructions, and supplied plan before designing. Match an existing design language when one is present. Otherwise derive a quiet, workmanlike direction from the audience and subject. When [`design-artifact`](../design-artifact/SKILL.md) is available, read its fundamentals to make that direction intentional. Keep this skill's traceability and source-preservation rules authoritative; creative direction must not inflate the plan into a dashboard or campaign page. Decide what the plan actually needs: - phases or sequence; - status and decision points; - owners and collaborators; - dependencies and risks; - acceptance checks; - unresolved questions. Do not add a timeline, progress percentage, status badge, or dashboard summary unless the source supports it. Improve grammar and structure without inflating an implementation plan into a strategy document. ## Preserve traceability - Keep source commitments recognizable. - Separate accepted decisions from assumptions and open questions. - Show sequence and dependency only where they are real. - Use tables for exact mappings, comparisons, or repeated fields. - Use a flow or timeline only when it makes order materially easier to understand. - Keep long prose readable instead of forcing every paragraph into a card. ## Build and verify Deliver one responsive, accessible, self-contained HTML file. Use semantic headings, lists, tables, and landmarks. Keep essential CSS and JavaScript inline, avoid external services, and make any navigation or disclosure keyboard-operable. Inspect the result at wide and narrow widths. Check that no commitment disappeared, that stages remain in the intended order, that ownership and dependencies are legible, and that long content does not overflow. Return the absolute path and note any structural interpretation you introduced.
© plannotator · MIT · plannotator/effective-html