html-plan
Skill48 starsChanged 4 months agoMITView on GitHub
Use this skill when the user asks to create, edit, review, or standardize a planning document that should be delivered as a standalone HTML file. This includes project plans, implementation plans, migration plans, release plans, research plans, and technical execution plans where readable structure, scannable sections, and portable HTML output matter.
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
- anirudhaxe/friday-skillstheir own version, first seen Jun 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
- mckayqsnell/snell-skills★ 2same name
- arkan/skills★ 1same name
- linkc-skills/HTML-Plan★ 1same name
- anirudhaxe/friday-skills★ 0same 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 repository5 other files it gives its agents.
- novel-writerSkill
- obsidian-git-repo-syncSkill
- qimao-novel-scraperSkill
- weibo-hot-scraperSkill
- zhihu-hot-scraperSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 10 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Create clear, standalone HTML planning documents for technical or project work.
- Distinctive: line 12
Use this skill when the user wants a plan document in HTML format, especially for:
- Distinctive: line 21
Do not use this skill for interactive web apps, marketing pages, dashboards, or rich UI prototypes unless the user specifically asks for a …
- Very specific: line 29
Use semantic HTML5: header, main, section, article, nav, footer where appropriate.
- Very specific: line 31
Use a readable structure with stable heading levels: one h1, then h2 for major sections, h3 for subsections.
- Distinctive: line 33
Prefer tables for timelines, milestones, owners, risks, dependencies, and status matrices.
- Very specific: line 34
Keep styling embedded in a single <style> block.
- Distinctive: line 35
Avoid external scripts, remote fonts, tracking pixels, or network-dependent assets.
- Distinctive: line 40
Use this structure as a default and adapt it to the user's context:
- Distinctive: line 79
Use this CSS as the starting point unless the user explicitly provides another document style:
- Distinctive: line 225
Use concrete action items with owners or owner placeholders.
- Distinctive: line 229
Prefer concise bullets over long prose unless the plan requires rationale.
- Distinctive: line 233
Before finalizing, verify that:
“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 Skill
Create clear, standalone HTML planning documents for technical or project work.
When to Use
Use this skill when the user wants a plan document in HTML format, especially for:
- Implementation plans
- Project or roadmap plans
- Migration or rollout plans
- Release plans
- Research or investigation plans
- Technical decision or execution plans
Do not use this skill for interactive web apps, marketing pages, dashboards, or rich UI prototypes unless the user specifically asks for a plan document.
Output Requirements
Produce a single self-contained .html file unless the user requests otherwise.
The document should:
- Use semantic HTML5:
header,main,section,article,nav,footerwhere appropriate. - Include a concise document title in both
<title>and the visible<h1>. - Use a readable structure with stable heading levels: one
h1, thenh2for major sections,h3for subsections. - Include a small table of contents when the document has more than four major sections.
- Prefer tables for timelines, milestones, owners, risks, dependencies, and status matrices.
- Keep styling embedded in a single
<style>block. - Avoid external scripts, remote fonts, tracking pixels, or network-dependent assets.
- Work when opened directly from the filesystem.
Recommended Document Structure
Use this structure as a default and adapt it to the user's context:
- Overview
- Goals and Non-Goals
- Scope
- Assumptions
- Workstreams or Phases
- Timeline or Milestones
- Dependencies
- Risks and Mitigations
- Open Questions
- Next Actions
For technical plans, also consider:
- Architecture Summary
- Implementation Steps
- Testing and Validation
- Rollout and Rollback
- Observability
- Security and Privacy Considerations
HTML Style Guidelines
Use the fixed Standard Plan Theme below for every generated plan document. Do not adapt the plan document's visual style to the surrounding project, product, brand, app UI, selected design option, or existing site palette. The plan document should look like a neutral execution document, not an extension of the product being planned.
Fixed style rules:
- Palette: page
#f6f8fb, paper#ffffff, text#111827, muted text#4b5563, border#d1d5db, accent#2563eb, accent-soft#eff6ff, code background#111827. - Layout: centered content, max width
1040px, page padding32px 16px 48px. - Shape: sections, cards, tables, callouts, and code blocks use
8pxradius. - Typography: system sans-serif only; body
16px; line height around1.65; oneh1;h2for major sections;h3for subsections. - Header: plain document header only. No hero layout, no preview-as-hero, no gradients, no decorative imagery, no product-style composition.
- Navigation: if used, render as a simple table-of-contents card with text links.
- Sections: white cards with subtle border; use light blue callouts for recommendations or notes.
- Tables: full-width, clear headers, light blue header background, visible row borders.
- Code: dark code blocks with light text; inline code uses light blue background.
- Print: include print-friendly CSS that removes background effects and avoids breaking sections.
Use this CSS as the starting point unless the user explicitly provides another document style:
:root {
color-scheme: light;
--page: #f6f8fb;
--paper: #ffffff;
--ink: #111827;
--muted: #4b5563;
--line: #d1d5db;
--accent: #2563eb;
--accent-soft: #eff6ff;
--code-bg: #111827;
--code-ink: #f9fafb;
}
* {
box-sizing: border-box;
}
body {
margin: 0;
background: var(--page);
color: var(--ink);
font-family: system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif;
font-size: 16px;
line-height: 1.65;
}
.page {
width: min(1040px, calc(100vw - 32px));
margin: 0 auto;
padding: 32px 0 48px;
}
header,
nav,
section,
footer {
border: 1px solid var(--line);
border-radius: 8px;
background: var(--paper);
padding: 24px;
}
main {
display: grid;
gap: 16px;
}
h1,
h2,
h3,
p {
margin: 0;
}
h1 {
font-size: 36px;
line-height: 1.15;
}
h2 {
margin-bottom: 12px;
font-size: 24px;
}
h3 {
margin: 18px 0 8px;
font-size: 18px;
}
p,
li,
td {
color: var(--muted);
}
a {
color: var(--accent);
}
table {
width: 100%;
border-collapse: collapse;
border: 1px solid var(--line);
border-radius: 8px;
overflow: hidden;
}
th,
td {
border-bottom: 1px solid var(--line);
padding: 10px 12px;
text-align: left;
vertical-align: top;
}
th {
background: var(--accent-soft);
color: var(--ink);
}
code {
border-radius: 4px;
background: var(--accent-soft);
color: var(--ink);
padding: 2px 5px;
}
pre {
overflow: auto;
border-radius: 8px;
background: var(--code-bg);
color: var(--code-ink);
padding: 16px;
}
pre code {
background: transparent;
color: inherit;
padding: 0;
}
.callout {
border-left: 4px solid var(--accent);
border-radius: 8px;
background: var(--accent-soft);
padding: 14px 16px;
}
@media print {
body {
background: #fff;
}
section {
break-inside: avoid;
}
}Content Guidance
Plans should be specific enough to execute:
- Use concrete action items with owners or owner placeholders.
- Make dependencies and sequencing explicit.
- Mark unknowns as open questions instead of hiding them.
- Separate facts, assumptions, and recommendations.
- Prefer concise bullets over long prose unless the plan requires rationale.
Quality Checklist
Before finalizing, verify that:
- The HTML file opens without build tooling.
- Heading levels are logical and not skipped.
- Tables have clear headers.
- Dates, owners, and statuses are consistently formatted.
- The plan includes risks, dependencies, and next actions.
- The document title and filename match the plan topic.
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.

