k-dang/dotfiles/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` 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 forcing every paragraph into a card.

Build and verify

Deliver one responsive, accessible, self-contained HTML file. Use semantic headings, lists, tables, and landmarks. Keep essential CSS and JavaScript inline, avoid external services, and make any navigation or disclosure keyboard-operable.

Default to a source review: check that no commitment disappeared, that stages remain in the intended order, that ownership and dependencies are clear, and that the markup and responsive CSS handle long content. Deliver the plan and let the user's feedback guide visual refinements.

Use browser inspection when the user explicitly requests it or substantial interaction needs testing. Focus on the relevant behavior; inspect wide and narrow widths when responsive behavior matters. Capture screenshots only to assess a specific issue, and repeat inspection only to confirm a fix or resolve uncertainty.

Return the absolute path and note any structural interpretation you introduced.