Skip to content

Agent skills for useful HTML artifacts, wireframes, interactive prototypes, plans, and diagrams.

1.5 KB
Raw Blame
---
title: Plans
description: Use HTML plans when timelines, comparisons, dependencies, or embedded examples help explain the work.
---

Plans are usually easiest to read and edit as Markdown. HTML can help when the
plan includes visual information that does not fit naturally in a linear
document.

<GuideChapterEvidence chapter="plans" />

## When HTML helps

An HTML plan can include:

- side-by-side alternatives;
- timelines with overlapping work;
- dependencies;
- diagrams or working examples;
- expandable detail attached to a step.

If the plan is just a sequence of tasks, keep it simple and use Markdown.

## Keep it tied to the source

A plan should preserve the supplied requirements, scope, dependencies, checks,
and unresolved questions. It should not invent missing product or technical
details to make the plan look complete.

<GuideHandoff
  artifactHref="https://thariqs.github.io/html-effectiveness/16-implementation-plan.html"
  artifactLabel="Inspect the HTML plan reference"
  artifactDescription="See how an implementation plan can use visual grouping."
  sourceHref="https://github.com/plannotator/effective-svg"
  skillHref="https://github.com/plannotator/effective-html/blob/main/skills/html-plan/SKILL.md"
  skillLabel="Use the plan skill"
  skillDescription="Create a plan without inventing missing requirements."
/>

<GuideNext
  href="/catalog?view=compact#catalog-collection"
  title="Browse the catalog"
  description="Open the HTML, SVG, and interactive examples."
/>