html-plan

1# HTML Plan
2 
3Turn 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.
4 
5## Shape the document around the work
6 
7Read 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.
8 
9When [`design-artifact`](../design-artifact/SKILL.md) is available, read its
10fundamentals to make that direction intentional. Keep this skill's traceability
11and source-preservation rules authoritative; creative direction must not
12inflate the plan into a dashboard or campaign page.
13 
14Decide what the plan actually needs:
15 
16- phases or sequence;
17- status and decision points;
18- owners and collaborators;
19- dependencies and risks;
20- acceptance checks;
21- unresolved questions.
22 
23Do 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.
24 
25## Preserve traceability
26 
27- Keep source commitments recognizable.
28- Separate accepted decisions from assumptions and open questions.
29- Show sequence and dependency only where they are real.
30- Use tables for exact mappings, comparisons, or repeated fields.
31- Use a flow or timeline only when it makes order materially easier to understand.
32…