Agent skill · writing content · yonatangross
visualize-plan
Renders planned changes as before/after architecture, risk heat maps, execution order and dependency graphs in ASCII, HTML or NotebookLM. Use when reviewing a plan. Not for an inline chart (use glyph).
Why this skill is useful
Adds specific visualization commands and structured outputs for architectural planning that the AI wouldn't reliably generate on its own.
What it needs
About 11k tokens when loaded. Last updated 2026-08-06. 215 stars on the source repository.
What this skill does
Plan Visualization Render planned changes as structured ASCII visualizations with risk analysis, execution order, and impact metrics. Every section answers a specific reviewer question. Core principle: Encode judgment into visualization, not decoration. Argument Resolution Question budget: ZERO before the first render This skill used to ask three blocking questions (source, then format, then sections) before a single character rendered, plus a fourth after. That is why fast paths leaked to glyph and to hand-written HTML. The format answer is not needed to render ASCII — the ASCII floor rule renders it first regardless of what the user picks. So asking up front buys nothing and costs a round-trip. The rule now: Decision When How --- --- --- Source before Auto-detect. Ask only if detection is genuinely ambiguous (STEP 0). Sections never Default to all. The tier-1 header is the progressive-disclosure layer. Format after ASCII One post-render question (STEP 5), merged with drill-deeper. --quick skips even that one. Budget: at most 1 Explore agent and one post-render question (STEP 5); stop and report at the finish line or the first cap, whichever comes first. --- CRITICAL: Task Tracking --quick skips this whole block. A 15-second render does not need a dependency graph; the task overhead would cost more than the work. STEP -1: Check Memory for Prior Plans STEP 0: Detect or Clarify Plan Context First, attempt auto-detection by running scripts/detect-plan-context.sh: This outputs branch name, issue number (if any), commit count, and file change summary. If auto-detection finds a clear plan (branch with commits diverging from main, or issue number in args), proceed to Step 1. If ambiguous, clarify with AskUserQuestion: --- STEP 0.5: Probe Formats (silent — no question here) Probe capabilities now so STEP 5 can offer only what will actually work. Do not ask anything at this step. Full procedure: Read("references/format-dispatch.md"). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills yonatangross/visualize-plan