plan-it
Stop reading walls of markdown. Start seeing your plan.
An HTML-first planning skill for Claude Code, Cursor, and 15 other agents. One file. Survives /clear. SHA-256 attested.
npx skills add OthmanAdi/plan-it
The pitch
Markdown plans don't get read.
You write a phase breakdown. You drop a hundred bullets. The agent skims. You skim. By phase 3 nobody knows what was decided in phase 1. By phase 5 the plan is a wall of text nobody opens.
plan-it gives you a single plan.html instead. Tabs. Drag-cards. Sliders. Mockups. Copy-as-markdown when you need it back as text. Embedded JSON as the canonical state. Open it in your browser. Drag a card. Watch a checkbox. Read it like a dashboard, not a thread.
It survives /clear because the file lives on disk and the hooks re-inject the active phase on every prompt. It's tamper-protected by SHA-256. It ships across 17 IDEs day 1.
/plan implementation-plan
/plan-render
Two commands. You're in.
What you get
10 ready-to-use HTML templates across all 9 categories Thariq named in the gallery:
| Template | What it does |
|---|
| implementation-plan | Phases + mockups + data-flow diagram + risk table |
| three-approaches | Side-by-side approach comparison with pros/cons/effort meters |
| ticket-triage | Drag-and-drop Now/Next/Later/Cut board with markdown export |
| feature-flag-editor | Grouped toggles + dependency warnings + diff-copy |
| module-map | Inline SVG architecture diagram with pan/zoom |
| annotated-pr | Unified diff with margin annotations + severity tags |
| living-design-system | Color/type/spacing/component variants, click to copy CSS var |
| animation-sandbox | Sliders for duration + easing, copy-as-CSS button |
| weekly-status | Shipping/Slipping/Blocked + sparkline of slip days |
| incident-timeline | Minute-by-minute post-mortem with log excerpts + action items |
Plus a CLI to bring them up: /plan, /plan-render, /plan-attest, /plan-status, /plan-export markdown, /plan-goal, /plan-loop.
Why HTML, not markdown
Thariq Shihipar called it on 2026-05-08:
"The format the agent emits is the control surface the human inspects, not a wrapper around it."
With Opus 4.7 at 1M tokens, the cost argument for markdown is dead. The constraint that's left is engagement. A plan only matters if it gets read. HTML preserves spatial layout, interactivity, comparisons, mockups, all the things markdown linearizes away.
plan-it is the persistent skill for that thesis. Web-artifacts-builder makes one-shot artifacts. Playground makes throwaway tools. Frontend-design produces components. None of them survive /clear. None mirror to 17 IDEs. None ship SHA-256 attestation. plan-it does all three.
What plan-it ships
| Capability | plan-it |
|---|
Persistent across /clear | yes |
| Multi-IDE adapters | 17 |
| SHA-256 tamper attestation | yes |
| Lifecycle hooks | 5 |
| HTML output | yes |
| Planning-specific templates | 10 |
| Single-file offline (no CDN) | yes |
| Bidirectional Markdown export | yes |
| Parity-locked version bumper across IDE mirrors | yes |
| Pytest coverage | 207 green |
The thesis we ship on
"HTML is the new markdown. I've stopped writing markdown files for almost everything and switched to using Claude Code to generate HTML for me."
Thariq Shihipar, Anthropic engineer
plan-it is the persistent, multi-IDE planning skill for the era that line opened.
Install
Claude Code plugin marketplace
/plugin marketplace add OthmanAdi/plan-it
/plugin install plan-it@plan-it
Any agent-skills-compliant IDE
npx skills add OthmanAdi/plan-it
Manual
git clone https://github.com/OthmanAdi/plan-it
ln -s "$PWD/plan-it/skills/plan-it" ~/.claude/skills/plan-it
Supported platforms (17)
