Files
plannotator__effective-html/site/content/docs/plans.mdx
2026-08-02 13:19:07 -07:00

50 lines
1.8 KiB
Plaintext

---
title: Plans
description: Preserve commitments and implementation sequence without adding visual ceremony.
---
Plans are often better as Markdown. The information is usually linear, the
source commitments matter, and the reader needs a durable sequence more than a
visual interface.
<GuideChapterEvidence chapter="plans" />
## Use HTML selectively
HTML can help when the plan needs:
- side-by-side comparison of alternatives;
- a timeline with meaningful overlap;
- an interactive dependency view;
- expandable evidence attached to milestones;
- a review surface that combines a plan with diagrams or working examples.
If none of those improve the decision, keep the plan simple.
## Preserve the source
A plan should distinguish supplied requirements from interpretation. Keep
scope, dependencies, validation, and unresolved questions visible. Do not
invent product claims or infrastructure to make the plan appear complete.
## Make verification part of the sequence
Name the checks that establish completion. Connect them to the work they
validate instead of collecting every test in a vague final phase.
<GuideHandoff
artifactHref="https://thariqs.github.io/html-effectiveness/16-implementation-plan.html"
artifactLabel="Inspect the HTML plan reference"
artifactDescription="See the case where visual grouping earns the extra medium."
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="Preserve supplied commitments and choose Markdown first."
/>
<GuideNext
href="/catalog?view=compact#catalog-collection"
title="Browse the complete artifact field"
description="Compare the guide's decisions against real HTML, SVG, and interactive work."
/>