htmldecklisted

# htmldeck One pipeline. **Two questions up front, both specification files written every time, two gates the user can decline.** ## Ask exactly two questions Ask both together, before anything else, and ask nothing else: 1. **How long should it be?** A maximum and/or a minimum. 2. **Anything to align to?** An existing brand, a deck, or source documents. Optional. **Unanswered is a valid answer to both.** Defaults: **8–12 slides**, no alignment material, both gates on. These produce a good deck — that is what the defaults are for. **Never ask a third question.** Every other decision is already made in the design system, and asking is the failure this plugin exists to prevent. If something seems to need asking, it is either already decided in `${CLAUDE_PLUGIN_ROOT}/docs/DESIGN-SYSTEM.md` or it is yours to decide. **Never ask whether to skip the gates.** Unprompted, both gates are on. If the user volunteers "no gates", "just build it", or names one of the two, honour exactly that. Asking would be a third question. ## Then run the pipeline Load `${CLAUDE_PLUGIN_ROOT}/skills/htmldeck/references/pipeline.md` and follow it. Seven stages, two gates: ``` governing idea → requirements → foundation spec (with the outline) → OUTLINE SIGN-OFF → slide-by-slide spec → spec review → DETAILED-SPEC SIGN-OFF → build, in batches → build review → owner review → fix ``` **Both `.md` specification files are written on every run**, gates or no gates, beside the deck and named