visual-planlisted

# Visual plan Produce a disciplined, local, reviewable plan before implementation begins. Markdown is the canonical plan because it supports comments, editing, history, backlinks, and durable storage. A self-contained HTML companion is optional and answers a specific review question, including a diagram drawn as inline SVG. The plan is the approval gate: research and write it, then stop before source edits until the user approves. This skill is provider-neutral. It works the same on Claude and OpenCode. It does not depend on any hosted plan application, MDX, or a second review service. ## When to use this skill Use it when the user asks for a plan, design direction, architecture review, UI flow, implementation proposal, migration plan, or approval artifact **and** the work has at least one of these properties: - more than one file or subsystem; - meaningful product or UX ambiguity; - a UI state or workflow that benefits from seeing it; - a data, API, security, or ownership decision that is expensive to undo; - a plan that another person or model must review before implementation. Skip it for a typo, a one-line fix, a single obvious function, or a task whose complete change can be explained in one sentence. Also skip it for a routine working doc: notes, an analysis, a draft with no approval gate and no cross-session handoff. That is the stock `workspace-authoring` skill's territory. The dividing line is whether the document exists to get a decision approved and survive