md-document

Topics in the source

• md-document — Long-form Markdown to HTML
• When to invoke
• Pipeline
• What gets rendered
• Hard rules
• Forcing-question library (Matt Pocock grill discipline)
• Distinct from
• Output artifact

The general-purpose converter — handles the 90% case Shihipar describes (specs, plans, RFCs, reports, explainers). Three stdlib tools pipeline together: Output is one .html file with sticky TOC, search filter, scrollspy, code-copy buttons, and the user's 12 derived brand tokens. Externals limited to Google Fonts CSS + Prism.js CDN. | Symptom | Action | |---|---| | markdown-html-orchestrator routes input as DOCUMENT | Invoke this skill | | User runs /cs-md-document .md directly | Invoke this skill | | User says "convert this spec/report/RFC/plan to HTML" | Invoke this skill | | Input is a code review (has diff blocks) | Route to md-review instead | | Input is a slide deck (clear --- boundaries) | Route to md-slides instead | | Input is [!NOTE], > [!TIP], > [!IMPORTANT], > [!WARNING], > [!CAUTION]) Blockquotes, ordered + unordered lists (single-level), horizontal rules Out of scope: nested lists, HTML inlines, footnotes, definition lists, task list checkboxes (rendered as plain text), reference-style links. 1. Refuses input 800 words / 4+ H2s; collapsible-top for shorter mobile-first docs. Canon: NN/g TOC Best Practices (2023). 3. All four interactive features, or a subset? Recommend

This is an excerpt. Refer to the complete source and its current requirements.