Plans

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.

Selective visual evidence

Use HTML only when the plan gains a useful second dimension.

Open complete artifact

Keep Markdown

The sequence is linear and the source commitments are already clear.

Earn HTML

Overlap, dependencies, alternatives, or attached evidence change the judgment.

Stop

The plan is actionable and traceable without decorative interface work.

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.

Browse the complete artifact fieldCompare the guide's decisions against real HTML, SVG, and interactive work.