mcpField
H
html-plan

html-plan

github.com/plannotatorDocuments3.8k3.8k installsUpdated 2w ago
Repository

About html-plan

html-plan is a skill for turning source material into a traceable, actionable plan in a single responsive HTML file. It is intended for plan authors who need to preserve commitments, ordering, terminology, and distinguish decisions from assumptions and open questions.

Key features

  1. 01Preserves source scope and commitments
  2. 02Structures phases, owners, dependencies, and risks
  3. 03Separates decisions, assumptions, and questions
  4. 04Creates responsive, accessible HTML
  5. 05Checks layout at wide and narrow widths

Use cases

  1. 01Converting project notes into an actionable plan
  2. 02Presenting dependencies and ownership clearly
  3. 03Publishing a plan as a self-contained HTML file

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/plannotator/effective-html --skill html-plan

After installing, type/html-planin Claude Code to confirm it loaded.

Bundled filesagents/openai.yaml

Details

From the project README

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 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.

Comments

Markdown supported