doc-holiday

Use when a documentation site needs real screenshots — "take the screenshots in SCREENSHOT_PLAN.md", "add screenshots to these docs", "screenshot the web app for the docs", "this page needs a picture of the dashboard", "get me terminal screenshots for this guide". Reads (or writes) a page-by-page screenshot plan, drives a browser to capture real product-UI screenshots, crops out chrome/PII, saves them under a per-page directory, and wires `` references into the docs at the exact spot. For shots it cannot generate itself (terminal output, IDE/editor state, native dialogs), it pre-wires the image path into the docs and hands the human an exact per-file capture list so dropping the file in requires no follow-up edit.

Use when you have a documentation site map / content plan and need the actual Doc Holiday instructions that generate and maintain the docs — "turn the site map into Doc Holiday prompts", "write the @doc.holiday prompts for our docs", "how do we make Doc Holiday build this docs site", "generate the create/update prompts for each page". Reads the planned IA (the output of `defining-the-documentation-site-map`) and the project's source, then emits, for every page, a ready-to-run `@doc.holiday` prompt with the right action, scope, Diátaxis mode, and target section — plus reusable Instruction Library entries for shared voice/style, ordered to match the IA, with maintenance/update prompts.

Use when you need to plan a project's documentation — "what should our docs contain and how should they be organized", "design the docs site map / IA", "lay out the docs site", "what pages do we need". Scans the source and emits a Diátaxis-organized site map (every page classified tutorial / how-to / reference / explanation) plus a per-page content plan and a Mermaid hierarchy, derived from the code and reconciled against the intended IA.