parthjshah95/visual-planning-skills

Tool-agnostic Claude skills — visual-explainer, visual-plan, and challenge-plan: single-file interactive HTML explainers and browser-reviewed plans.

11

stars

24

commits

HTML

primary language

Sep 3, 2026

updated

README

Visual Planning Skills

Struggling to understand the giant walls of text your AI throws at you? Frustrated by jargon AI invents that only it can fathom?

You are not alone.

No one understands AI these days.

Six slides: real posts about AI jargon walls

Open the interactive explainer → It plays this deck with controls. It shows the whole flow, a live decision card, and install steps for eight agents.

Slide credits: Steve Yegge (the workflow comic); the r/ClaudeAI community: the moderator-bot summary, u/nightbunnies, u/endlesskitty, u/Careless_Leg_4905; the Swole Doge format. The ASD-STE100 subskill draws on danyuchn/asd-ste100-skill.

The fix

A wall of gray text turns into a small drawn plan with one decision card

visual-plan draws the plan. asd-ste100 keeps the words plain. Decision cards ask questions you can answer.

The skills

SkillWhat it does
visual-explainer"Visually explain how the code works." Creates an HTML file with animations and diagrams.
visual-plan"Visually plan this task." Replaces the plan mode with an HTML version of it. Less text, more interactivity.
visual-schema"Visualize my database schema." Visually see the models, relationships, and fields on a draggable canvas.
challenge-plan"Challenge this plan for over-engineering." A different model reviews the plan. It may only cut, never add.

The skills work together, but none needs the others.

  • visual-plan reuses the drawing patterns from visual-explainer.
  • challenge-plan is separate. visual-plan never runs it for you. You run it when a plan needs a check.

visual-explainer example

The animated explainer that visual-explainer produces

▶  View it live on GitHub Pages

Above: visual-explainer explains one subject, how a deploy pipeline works. A scene player walks the mechanism step by step. Source: pipeline-explainer.html.

visual-plan example

The animated visual plan that visual-plan produces

▶  View it live on GitHub Pages

Above: visual-plan plans one small feature, Add CSV export to the Reports page. It shows the change as an animation. It turns the one real decision into a card you answer in the browser. Source: plan.html.

visual-schema example

The interactive schema diagram that visual-schema produces

▶  View it live on GitHub Pages

Above: visual-schema draws a small bookstore database. The tables come from the model source. Click a table to see its relationships. Drag to pan, zoom to fit. Source: bookstore-schema.html.

Examples

Every example is one self-contained HTML file. Open the live link, or download the source and open it in a browser.

ExampleMade withOpen
Deploy-pipeline explainervisual-explainerlive · source
The visual-plan explainer (the deck above)visual-explainerlive · source
CSV-export planvisual-planlive · source
Bookstore schemavisual-schemalive · source

Install

Clone the repo once. Then copy the skill folders to where your agent loads skills.

git clone https://github.com/parthjshah95/visual-planning-skills
cd visual-planning-skills
AgentCopy the skills to
Claude Codecp -R skills/* ~/.claude/skills/
Codex / ChatGPTcp -R skills/* ~/.codex/skills/
Cursorcp -R skills/* ~/.cursor/skills/
OpenCodecp -R skills/* ~/.config/opencode/skills/
OpenClawcp -R skills/* ~/.openclaw/skills/
Hermescp -R skills/* ~/.hermes/profiles/<profile>/skills/
Windsurf (per project)cp -R skills/* <project>/.windsurf/skills/
Antigravity (per workspace)cp -R skills/* <workspace>/.agents/skills/

Each SKILL.md is self-contained.

Custom instructions

Optional: set what a finished plan must contain for your team.

A finished plan means different things to different teams. One team merges straight to trunk. Another team needs a dev environment, a monitoring window, and a sign-off. So visual-plan keeps that contract in an optional file, not in the skill.

  • Pass a file with instructions=<path>, or drop a custom-instructions.md file at your workspace root.
  • With no file, the skill uses a default: a goal, a picture of the change, the steps, a check that it worked, and the open decisions.
  • A custom-instructions.md file adds three things only: extra required sections, extra required decisions (each one becomes a card), and where the agent records the approved plan.

Example: a staged delivery pipeline

Save this as custom-instructions.md. It adds a dev test plan, a prod monitoring plan, and four fixed decisions. Change it or delete it as you need.

# Custom instructions: staged dev/prod delivery

## Required sections
- **Dev test plan**: the environment, the steps, the expected results, and the logs to check.
- **Prod monitoring plan**: one production-only check, a fixed monitoring window, the failure
  threshold, the rollback choice, and who to notify.

## Required decisions
- Pause for a human PR review before the dev merge? (default: no, for low-risk changes)
- Confirm the dev test steps and expected results.
- Confirm the prod validation steps and the rollback choice.
- Is extended monitoring needed? If yes, give the window and thresholds.

## Record the approved plan in
- The tracker ticket. Move the ticket to "ready to start" on approval.

License

MIT. See LICENSE.

Contributors

parthjshah95

24 commits

parthjshah95/visual-planning-skills

Tool-agnostic Claude skills — visual-explainer, visual-plan, and challenge-plan: single-file interactive HTML explainers and browser-reviewed plans.

11

stars

24

commits

HTML

primary language

Sep 3, 2026

updated

README

Visual Planning Skills

Struggling to understand the giant walls of text your AI throws at you? Frustrated by jargon AI invents that only it can fathom?

You are not alone.

No one understands AI these days.

Six slides: real posts about AI jargon walls

Open the interactive explainer → It plays this deck with controls. It shows the whole flow, a live decision card, and install steps for eight agents.

Slide credits: Steve Yegge (the workflow comic); the r/ClaudeAI community: the moderator-bot summary, u/nightbunnies, u/endlesskitty, u/Careless_Leg_4905; the Swole Doge format. The ASD-STE100 subskill draws on danyuchn/asd-ste100-skill.

The fix

A wall of gray text turns into a small drawn plan with one decision card

visual-plan draws the plan. asd-ste100 keeps the words plain. Decision cards ask questions you can answer.

The skills

SkillWhat it does
visual-explainer"Visually explain how the code works." Creates an HTML file with animations and diagrams.
visual-plan"Visually plan this task." Replaces the plan mode with an HTML version of it. Less text, more interactivity.
visual-schema"Visualize my database schema." Visually see the models, relationships, and fields on a draggable canvas.
challenge-plan"Challenge this plan for over-engineering." A different model reviews the plan. It may only cut, never add.

The skills work together, but none needs the others.

  • visual-plan reuses the drawing patterns from visual-explainer.
  • challenge-plan is separate. visual-plan never runs it for you. You run it when a plan needs a check.

visual-explainer example

The animated explainer that visual-explainer produces

▶  View it live on GitHub Pages

Above: visual-explainer explains one subject, how a deploy pipeline works. A scene player walks the mechanism step by step. Source: pipeline-explainer.html.

visual-plan example

The animated visual plan that visual-plan produces

▶  View it live on GitHub Pages

Above: visual-plan plans one small feature, Add CSV export to the Reports page. It shows the change as an animation. It turns the one real decision into a card you answer in the browser. Source: plan.html.

visual-schema example

The interactive schema diagram that visual-schema produces

▶  View it live on GitHub Pages

Above: visual-schema draws a small bookstore database. The tables come from the model source. Click a table to see its relationships. Drag to pan, zoom to fit. Source: bookstore-schema.html.

Examples

Every example is one self-contained HTML file. Open the live link, or download the source and open it in a browser.

ExampleMade withOpen
Deploy-pipeline explainervisual-explainerlive · source
The visual-plan explainer (the deck above)visual-explainerlive · source
CSV-export planvisual-planlive · source
Bookstore schemavisual-schemalive · source

Install

Clone the repo once. Then copy the skill folders to where your agent loads skills.

git clone https://github.com/parthjshah95/visual-planning-skills
cd visual-planning-skills
AgentCopy the skills to
Claude Codecp -R skills/* ~/.claude/skills/
Codex / ChatGPTcp -R skills/* ~/.codex/skills/
Cursorcp -R skills/* ~/.cursor/skills/
OpenCodecp -R skills/* ~/.config/opencode/skills/
OpenClawcp -R skills/* ~/.openclaw/skills/
Hermescp -R skills/* ~/.hermes/profiles/<profile>/skills/
Windsurf (per project)cp -R skills/* <project>/.windsurf/skills/
Antigravity (per workspace)cp -R skills/* <workspace>/.agents/skills/

Each SKILL.md is self-contained.

Custom instructions

Optional: set what a finished plan must contain for your team.

A finished plan means different things to different teams. One team merges straight to trunk. Another team needs a dev environment, a monitoring window, and a sign-off. So visual-plan keeps that contract in an optional file, not in the skill.

  • Pass a file with instructions=<path>, or drop a custom-instructions.md file at your workspace root.
  • With no file, the skill uses a default: a goal, a picture of the change, the steps, a check that it worked, and the open decisions.
  • A custom-instructions.md file adds three things only: extra required sections, extra required decisions (each one becomes a card), and where the agent records the approved plan.

Example: a staged delivery pipeline

Save this as custom-instructions.md. It adds a dev test plan, a prod monitoring plan, and four fixed decisions. Change it or delete it as you need.

# Custom instructions: staged dev/prod delivery

## Required sections
- **Dev test plan**: the environment, the steps, the expected results, and the logs to check.
- **Prod monitoring plan**: one production-only check, a fixed monitoring window, the failure
  threshold, the rollback choice, and who to notify.

## Required decisions
- Pause for a human PR review before the dev merge? (default: no, for low-risk changes)
- Confirm the dev test steps and expected results.
- Confirm the prod validation steps and the rollback choice.
- Is extended monitoring needed? If yes, give the window and thresholds.

## Record the approved plan in
- The tracker ticket. Move the ticket to "ready to start" on approval.

License

MIT. See LICENSE.

Contributors

parthjshah95

24 commits

Languages

HTML

99.6%