html-plan

# 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`](../design-artifact/SKILL.md) 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 forc...