What problem does it solve? Coordinating a product planning workflow that spans spec Markdown authoring, HTML rendering, and Figma frame creation requires switching between three separate skills and deciding when to proceed. This Skill acts as a single entry point that routes requests to the right sub-skill and enforces confirmation gates between stages so nothing advances automatically. ## Core Features & Use Cases - Entry-point routing: Directs requests to planning-md (spec creation/editing), planning-html (template rendering), or planning-figma (new 3-tier frames) based on intent. - Confirmation gates: Pauses after each stage to ask whether to continue, with an extra mandatory check before any Figma write operation. - Cross-artifact consistency: Verifies 4-way alignment between md section numbers, HTML area numbers, Figma section names, and mockup markers. - Use Case: A product manager says "draft a new spec, then take it through HTML and Figma" — the orchestrator runs planning-md, pauses for confirmation, runs planning-html, pauses again, then confirms once more before creating Figma frames. ## Quick Start Ask the assistant to start a new product plan and carry it from Markdown spec through HTML rendering to a new Figma frame, confirming at each step.
