previewlisted

# preview ## Overview | Field | Contract | | --- | --- | | Purpose | Turn existing idea/plan evidence into a lightweight preview artifact. | | Primary input | User query, file path, or plan/work-item directory. | | Primary output | `visuals/visual-route.md` and optional `visuals/showcase.html`. | | Boundary | Preview only; do not edit source code or existing plan artifacts. | | Next handoff | User opens the preview, or explicitly asks for planning/implementation later. | `preview` is not a planning workflow. Treat `plan.md`, `brainstorm.md`, legacy phase files, `requirements.md`, and nearby notes as input evidence to read, not as workflows to activate. ## Resources Load only the visual resource needed for the selected route: | Need | Load | | --- | --- | | ASCII layout, HTML baseline design, showcase polish | `frontend-design` skill | No other skill resources are required for v1. Use scout for context discovery and file reading, then generate from the evidence. ## Workflow ```text input take -> plan context -> route -> generate -> output ``` ## Step 1 - Input Take Accept one input shape: - user query/topic: "preview this plan", "explain checkout redesign", "make an ASCII flow", "create a showcase HTML" - file path: `brainstorm.md`, `plan.md`, a legacy phase file, `requirements.md`, feature brief, issue note, or another source file the user wants previewed - plan/work-item directory: `plans/<work-item>/` or a folder that contains planning artifacts Resolve t