plannar

Convert agent-produced planning content into interactive MDX documents with shadcn/ui components.

7|1|Updated May 16, 2026
One-click install
npx skills add https://github.com/ethan-krich/plannar --skill plannar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plannar
Source: https://github.com/ethan-krich/plannar/tree/main/skills/plannar
Command: npx skills add https://github.com/ethan-krich/plannar --skill plannar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plannar helps teams produce plans that people actually read by turning long, agent-written markdown into structured, interactive MDX with shadcn/ui components and Playground previews.

Core Features & Use Cases

  • MDX plan authoring workflow: Produces plan documents as MDX files saved to .plannar/plans/, with the agent editing only that directory.
  • Skimmable structure with shadcn components: Uses Tabs, Accordion, and Cards to organize “what” vs “why” and reduce token-heavy walls of text.
  • Interactive UI validation via Playground: Embeds interactive previews using <Playground> with bind state wiring and documented binding rules, without wiring previews to real APIs.
  • End-to-end planning phases: Guides the full flow—Understand in parallel Explore agents, Design with one or multiple Plan agents, Review validation, then Present the final MDX output.

Quick Start

Ask the agent for a plan by saying: Use plannar to write an MDX plan for the following task, and save it to .plannar/plans/ with Tabs, Cards, and any necessary Playground previews.

Frequently Asked Questions about plannar

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert agent-generated planning content into readable MDX documentation?

You convert agent-generated planning content into readable MDX documentation by structuring markdown into interactive files using shadcn/ui components like Tabs, Accordion, and Cards. This organizes what versus why to reduce text walls.

What is the best way to structure design docs and proposals for team consumption?

The best way to structure design docs and proposals for team consumption is applying interactive MDX formatting. Using Tabs and Accordion components separates sections like implementation breakdowns, making long plans skimmable instead of token-heavy text walls.

How do I add interactive UI previews to MDX files without connecting to real APIs?

You add interactive UI previews to MDX files by embedding a Playground component with bind state wiring. This uses documented binding rules and safe mocked previews to validate UI ideas without wiring to real APIs.

Can I use shadcn/ui components to organize implementation breakdowns in MDX?

Yes, you can use shadcn/ui components to organize implementation breakdowns in MDX. Tabs, Accordion, and Cards structure validated UI preview ideas and implementation breakdowns, reducing walls of text into skimmable sections.

What are the limitations of using interactive MDX for agent planning workflows?

A key limitation of using interactive MDX for agent planning workflows is directory restriction; the agent edits only the .plannar/plans/ directory. Additionally, embedded Playground previews must use mocked rules and cannot wire to real APIs.