html-plan
Skill0 starsChanged 5 months agoMITView on GitHub
Create a thorough implementation plan in a single self-contained HTML file. Use when the user asks for implementation planning, architecture design, technical design documents, or wants to think through a feature before coding. Generates mockups, data flow diagrams, code snippets, and decision logs in a single easy-to-read HTML artifact.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- mckayqsnell/snell-skillstheir own version, first seen Nov 1, 2026
- linkc-skills/HTML-Plantheir own version, first seen Oct 19, 2026
- MondayNotAGoodDay/skillstheir own version, first seen Oct 15, 2026
- anthropics/claude-plugins-communitytheir own version, first seen Oct 13, 2026
- Yunshiro/yunn-skillstheir own version, first seen Jul 30, 2026
- plannotator/effective-htmltheir own version, first seen Jun 13, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- anthropics/claude-plugins-community★ 4.8ksame name
- plannotator/effective-html★ 3.8ksame name
- Yunshiro/yunn-skills★ 48same name
- mckayqsnell/snell-skills★ 2same name
- arkan/skills★ 1same name
- linkc-skills/HTML-Plan★ 1same name
- MondayNotAGoodDay/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 8 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Create a thorough implementation plan as a single self-contained HTML file.
- Distinctive: line 16
Every plan HTML must include these sections in order:
- Distinctive: line 28
Use HTML/CSS to create realistic-looking mockups of key screens or components
- Distinctive: line 35
Use CSS box diagrams with arrows (pure HTML/CSS, no SVG library needed)
- Distinctive: line 44
Keep snippets focused — no more than ~40 lines each
- Distinctive: line 54
Place this section at the very bottom of the HTML
- Distinctive: line 58
Use a clean, readable font stack (system-ui or similar)
- Very specific: line 61
Use max-width: 960px centered container for readability
- Distinctive: line 63
Keep the file size reasonable — no large embedded images or heavy JS libraries
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
HTML Plan
Create a thorough implementation plan as a single self-contained HTML file. The plan must be comprehensive, scannable, and useful for both the developer implementing it and anyone reviewing it later.
Output format
Write the output to a single .html file in the current working directory. Use a descriptive filename like plan-{feature-name}.html. The HTML must be fully self-contained (no external dependencies, CSS and JS inline). Create the output in dark mode (adjust colors of the elements like text etc if needed for good dark mode visibility).
Structure
Every plan HTML must include these sections in order:
1. Header
- Title:
Implementation Plan: {Feature Name} - Status badge (draft / in-review / approved)
- Date and author context
2. Summary
- 2-3 sentence overview of what this plan covers
- Bullet list of key goals
3. Mockups / Visual Design
- Use HTML/CSS to create realistic-looking mockups of key screens or components
- Annotate mockups with callouts showing what changes where
- Show before/after states where useful
- For APIs or backend work, show request/response wireframes instead
4. Data Flow
Show how data moves through the system:
- Use CSS box diagrams with arrows (pure HTML/CSS, no SVG library needed)
- Label each step clearly
- Show: user action → event → handler → data layer → response → UI update
- Include error paths as dashed-line branches
5. Key Code Snippets
- Show 3-6 critical code snippets the implementer will need to reference
- Include: types/interfaces, core logic, edge-case handling
- Annotate important lines or patterns with inline notes
- Keep snippets focused — no more than ~40 lines each
6. Implementation Steps
Numbered, ordered steps in implementation order:
- Each step: what file to touch, what to change, any dependencies on prior steps
- Mark risky/complex steps with a warning icon
7. Open Questions / Decisions
- Bullet list of unresolved questions
- For each: the question, options considered, recommended choice, and what blocks on it
- Place this section at the very bottom of the HTML
Style guidelines
- Use a clean, readable font stack (system-ui or similar)
- Color scheme: light background, dark text, one accent color for highlights
- Code blocks should use a monospace font with subtle background
- Use
max-width: 960pxcentered container for readability - Interactive: add collapsible sections for details that would otherwise cause scrolling fatigue
- Keep the file size reasonable — no large embedded images or heavy JS libraries
- Print-friendly: the plan should read well when printed to PDF
After writing
End your response with: Plan created: {filename} — providing a relative path to the HTML file.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

