---
name: html-summary
description: >
Convert a stakeholder summary markdown file into a single self-contained HTML executive report — bottom line and
decision asks up front, supporting detail later — styled with a Test Double-derived palette and self-contained mermaid
diagrams. Use when the user wants to turn a stakeholder summary, executive summary, or business summary into an HTML
report, generate an HTML version of a summary doc, or produce a shareable HTML file from a summary markdown. Produces
an HTML sibling file only; does not publish anything.
argument-hint: "[path to stakeholder-summary.md]"
allowed-tools: Read, Write, Bash(bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh")
---
## Project Context
- personal config directory: !`bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh" 2>/dev/null || echo "$HOME/.claude"`
- project .han/config.md: !`cat .han/config.md 2>/dev/null || echo ""`
As your first action, use the Read tool on `.han/config.md` inside the `personal config directory` path above. A read
that returns no file is no personal configuration: continue silently. When that file or the `project .han/config.md`
probe supplies content, apply it per [config-rule.md](../../references/config-rule.md), which governs precedence
between the two files, relative-path resolution, and what to do with a file that reads but cannot be used.
# HTML Summary
Convert a stakeholder summary markdown file into a single self-contained HTML report tailored for executive readers —
bottom line and decision asks up front, supporting detail later — styled with a Test Double-derived palette. The skill
produces one HTML file next to the source markdown and stops there.
## Inputs
- **Source markdown file** — usually a `stakeholder-summary.md` inside a planning folder. If the user does not name one,
ask. Do not guess.
## Output
- **HTML sibling file** — written next to the source markdown, same basename, `.html` extension. Example:
`filters-and-saved-views/stakeholder-summary.md` → `filters-and-saved-views/stakeholder-summary.html`. This is the
only artifact the skill produces.
## Hard rules
- **Single file, no external network resources.** No ``, no `
```
Leave the placeholder string `` exactly as written. The inliner script in Step 6
replaces it with the vendored mermaid.min.js bundle. The mermaid initialization block (with the report palette theme
variables) is also part of the template — paste it verbatim.
Section omission rules:
- Omit any section the source markdown does not address. Do not invent content to fill a section.
- The bottom line card is the only required section other than the header — if the source has no explicit TL;DR, derive
one from the opening paragraph and clearly mark it as such in your work notes.
Markup rules:
- Use the entity `—` not `—` for em-dashes in HTML body content (the template does this consistently).
- Use the entity `→` for arrows in flow diagrams.
- Apply class names verbatim from the template — `tldr`, `ask-block`, `ask`, `walk`, `flow`, `node`, `node.good`,
`node.bad`, `node.start`, `out-of-scope`, `chip`, `chip.good`, `chip.bad`.
- Wrap the feature-name portion of the `
` in `` for the green background.
### 5. Verify the HTML
Open the file you just wrote and confirm:
- The `