New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Visualize Plan

by HazAT in HazAT/pi-config

Turns an existing implementation plan into a polished self-contained HTML page and opens it in the browser.

MITAuto-check passedAgent Workflows

Install Visualize Plan

skills CLI
$ npx skills add HazAT/pi-config --skill visualize-plan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install HazAT/pi-config visualize-plan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/HazAT/pi-config.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/visualize-plan .claude/skills/visualize-plan && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
visualize-plan
GitHub stars
451
Token cost
~1.1k tokens
SKILL.md length
574 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

Turns an existing implementation plan into a polished self-contained HTML page and opens it in the browser.

  • Works in 6 steps: Resolve the plan → Load the visual system → Inventory the source → …
  • Asked to visualize a plan
  • SKILL.md covers Step 1: Resolve the plan, Step 2: Load the visual system, Step 3: Inventory the source and Step 4: Compose the page, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Visualize Plan is an agent skill from HazAT/pi-config. Turns an existing implementation plan into a polished self-contained HTML page and opens it in the browser. Use when asked to "visualize a plan", "open this plan as HTML", "make this plan visual", or present a Markdown plan visually without changing its decisions.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Planning, HTML artifacts and Browser automation. The repository describes itself as: My personal pi coding agent configuration - skills and extensions. The licence is MIT.

When your agent uses it

  • Asked to visualize a plan
  • Open this plan as HTML
  • Make this plan visual
  • Present a Markdown plan visually without changing its decisions

Example prompts

  • “visualize a plan”
  • “open this plan as HTML”
  • “make this plan visual”
  • “/visualize-plan”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Resolve the plan
  2. Load the visual system
  3. Inventory the source
  4. Compose the page
  5. Render and open
  6. Verify and report

What it can do on your machine

Read from SKILL.md and the folder at commit 655acd4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Visualize Plan loads about 1.1k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 574 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~70
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from HazAT/pi-config at commit 655acd4, republished under its MIT licence (© HazAT). 574 words, ~1,128 tokens.

Download SKILL.mdSave it as .claude/skills/visualize-plan/SKILL.md (or your agent's skills folder).
name
visualize-plan
description
Turns an existing implementation plan into a polished self-contained HTML page and opens it in the browser. Use when asked to "visualize a plan", "open this plan as HTML", "make this plan visual", or present a Markdown plan visually without changing its decisions.
<!--
Uses Visual Explainer by Nico Bailon:
https://github.com/nicobailon/visual-explainer
-->

Visualize Plan

Transform an existing plan into a faithful, polished HTML explanation. Do not review, rewrite, execute, or expand the plan into new requirements.

Step 1: Resolve the plan

Resolve the plan source in this order:

  1. If the input names a readable file, use that file. Treat the full input as one path after removing optional surrounding quotes or a leading @.
  2. If the input is empty, derive the session file (PI_SESSION_FILE, or in Claude Code $HOME/.claude/projects/<project slug>/$CLAUDE_CODE_SESSION_ID.jsonl with / and . in the project path mapped to -) and use ${SESSION_FILE%.jsonl}.plan.md when it exists.
  3. If the input contains substantial inline plan content, use it directly.
  4. Otherwise, stop and ask for a plan file path or pasted plan.

For path-like input that does not exist, report the missing path; do not reinterpret it as plan text. Read the complete plan before generating anything.

Step 2: Load the visual system

Load the visual-explainer skill and follow its full-HTML workflow, design rules, reference routing, and delivery checklist. Do not use quick mode: implementation plans need custom hierarchy and composition.

Use only the source plan unless the user explicitly asks to verify it against the repository. Do not research the codebase merely because the plan mentions files or symbols.

Step 3: Inventory the source

Create a private coverage inventory of every substantive source section, including:

  • goal, intent, and selected approach;
  • in-scope and out-of-scope boundaries;
  • architecture, data flow, or behavior changes actually stated in the plan;
  • implementation phases and dependencies;
  • affected files, interfaces, contracts, and migrations;
  • acceptance criteria and verification commands;
  • assumptions, risks, rejected alternatives, and repository evidence.

Preserve exact commands, paths, identifiers, and acceptance-criterion IDs. Never invent missing architecture, dependencies, evidence, or requirements. Use cards or prose when the source does not justify a diagram.

Show full SKILL.md (282 more words)Show less

Step 4: Compose the page

Choose a distinctive editorial, blueprint, paper/ink, or IDE-inspired direction suited to the plan. Make the first viewport communicate the goal, selected approach, scope, and implementation shape.

Prefer this hierarchy when the source supports it:

  1. executive overview and scope;
  2. architecture or behavior map;
  3. ordered implementation sequence with dependencies;
  4. contracts and affected-file map;
  5. acceptance criteria and test/verification plan;
  6. risks, assumptions, evidence, and rejected alternatives.

Use Mermaid only for relationships or flow present in the source. Use semantic tables for matrices and compact cards or timelines for implementation work. Keep dense evidence and reference material collapsible. Preserve all substantive source content even when this requires additional sections.

Step 5: Render and open

Generate one complete self-contained HTML document. Derive a descriptive kebab-case filename from the plan title, ending in -visual-plan.html. Avoid overwriting an existing output by adding a short numeric suffix when needed.

Call visual_explainer with:

  • action: "render";
  • the basename in filename;
  • the complete document in html;
  • open: true;
  • viewer: "browser".

The renderer writes under ~/.agent/diagrams/. Do not create a Markdown companion unless requested.

Step 6: Verify and report

Confirm the render result reports the output path and a dispatched browser open. Confirm the HTML file exists. If browser opening fails, report the failure and provide the file path without claiming it opened.

Reply with only a concise result: the plan title, output path, and whether the browser open was dispatched.

Completion criteria

  • The page is faithful to the supplied plan and introduces no new decisions.
  • Every substantive plan section appears in the page.
  • The HTML is self-contained, readable, responsive, and visually intentional.
  • The file exists under ~/.agent/diagrams/ and browser-open status is reported accurately.

© HazAT, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/visualize-plan of HazAT/pi-config.

Open the folder on GitHubat commit 655acd4

Compare with similar skills

Visualize Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Visualize Plan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Visualize Plan this skillHazAT/pi-config451—~1.1kAutomated safety check: PassMIT
Plannotator Visual Explainerbacknotprop/plannotator9.2k—~1.7kAutomated safety check: PassApache-2.0
Plannotator Planning Analysisbacknotprop/plannotator9.2k—~6.7kAutomated safety check: PassApache-2.0
Plan Previewu-ichi/reviewable-html-workbench2981 repos~1.8kAutomated safety check: PassMIT
Visual HTML Rendereru-ichi/reviewable-html-workbench2981 repos~8.7kAutomated safety check: PassMIT
PRP Visual Companion PageWirasm/prp2.3k—~1kAutomated safety check: PassMIT

Similar skills

  • Plannotator Visual Explainer

    backnotprop/plannotator

    Builds self-contained HTML explainers for plans, pull requests and technical concepts in Plannotator's theme, then opens them in its annotation view.

    9.2k GitHub stars~1.7k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Plannotator Planning Analysis

    backnotprop/plannotator

    Mines a Plannotator archive of denied plans for feedback patterns and prompt improvements, then writes an HTML dashboard report, with a Claude Code fallback.

    9.2k GitHub stars~6.7k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Plan Preview

    u-ichi/reviewable-html-workbench

    Plan Mode の <proposedplan を出す直前に、計画の段階・依存関係・検証観点を一時HTMLで視覚確認したい時に使う agent-internal skill。Use this agent-internal skill to create a temporary HTML preview for a plan just before presenting…

    298 GitHub starsUsed in 1 repo~1.8k tokens
    Agent WorkflowsAuto-check passed

  • Visual HTML Renderer

    u-ichi/reviewable-html-workbench

    HTMLを最終成果物として生成・検証・プレビューしたい時に使う共通レンダラー。Use this shared renderer when the user wants content turned into a final, validated, previewable HTML artifact.

    298 GitHub starsUsed in 1 repo~8.7k tokens
    Agent WorkflowsAuto-check passed

  • PRP Visual Companion Page

    Wirasm/prp

    Writes a self-contained HTML companion beside a PRP plan or review that shows the diagram, steps, risks, verdict and findings, each item with a stable id.

    2.3k GitHub stars~1k tokensUpdated 5 days ago
    Agent WorkflowsAuto-check passed

  • Visualize Plan

    yonatangross/orchestkit

    Renders planned changes — architecture and before/after comparisons, risk heat maps, execution order, dependency graphs, impact metrics — in your chosen output format (ASCII + emojis, an interactive…

    288 GitHub stars~6.2k tokensUpdated yesterday
    Agent WorkflowsAuto-check: notes

More from HazAT/pi-config

All 10 skills in this repo

  • Session Reader

    HazAT/pi-config

    Efficiently read and analyze pi agent session JSONL files. An agent skill from HazAT/pi-config.

    451 GitHub stars~808 tokensUpdated 1 mo ago
    Auto-check passed

  • Pi Extension Development

    HazAT/pi-config

    Defines the local standard for standalone Pi extension repositories.

    451 GitHub stars~1.5k tokensUpdated 1 mo ago
    Auto-check passed

  • Superconductor

    HazAT/pi-config

    Operates the super.engineering/Superconductor sc CLI for app-managed agents, teams, sessions, layouts, worktrees, and review threads.

    451 GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed

  • Plan

    HazAT/pi-config

    Interactively investigate a request, compare approaches, and write the selected implementation plan to a supplied Markdown path.

    451 GitHub stars~528 tokensUpdated 1 mo ago
    Auto-check passed

  • Review

    HazAT/pi-config

    Coordinate a model-diverse local code review, automatically repair actionable findings with sequential workers, and re-review to a final verdict.

    451 GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check passed

  • Setup Superconductor Project

    HazAT/pi-config

    Configures a repository for super.engineering with repo-owned worktree setup and development-server scripts.

    451 GitHub stars~999 tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Visualize Plan

What does Visualize Plan do?

Turns an existing implementation plan into a polished self-contained HTML page and opens it in the browser. Visualize Plan is an agent skill from HazAT/pi-config. Turns an existing implementation plan into a polished self-contained HTML page and opens it in the browser.

When should I use Visualize Plan?

Visualize Plan fits situations like: asked to visualize a plan; open this plan as HTML; make this plan visual; present a Markdown plan visually without changing its decisions.

How do I install Visualize Plan in Claude Code?

Run `npx skills add HazAT/pi-config --skill visualize-plan -a claude-code`. Or copy the skill folder (skills/visualize-plan in HazAT/pi-config) into .claude/skills/visualize-plan in your project. Claude Code loads it when a task matches its description.

How do I install Visualize Plan in Codex?

Run `npx skills add HazAT/pi-config --skill visualize-plan -a codex`. Or copy the skill folder (skills/visualize-plan in HazAT/pi-config) into .agents/skills/visualize-plan in your project. Codex loads it when a task matches its description.

Can I use Visualize Plan in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add HazAT/pi-config --skill visualize-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/visualize-plan, .gemini/skills/visualize-plan, .github/skills/visualize-plan and .opencode/skills/visualize-plan in your project.

What does Visualize Plan need to run?

SKILL.md names no scripts, command-line tools or credentials: Visualize Plan is instructions for the agent only.

Does Visualize Plan access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Visualize Plan safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Visualize Plan use?

Visualize Plan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Visualize Plan use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Visualize Plan?

Skills that share tags, products or a category with Visualize Plan: Plannotator Visual Explainer (backnotprop/plannotator, 9.2k stars), Plannotator Planning Analysis (backnotprop/plannotator, 9.2k stars), Plan Preview (u-ichi/reviewable-html-workbench, 298 stars) and Visual HTML Renderer (u-ichi/reviewable-html-workbench, 298 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Visualize Plan?

HazAT (a GitHub user) maintains it in HazAT/pi-config, which has 451 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on August 25, 2026.

Source: HazAT/pi-config on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.