Planning plugins

Guides you through decomposing a coding project into an execution plan you own instead of generating a plan for you. Mines your docs, tickets, and codebase for the real work and dependencies while you make every scoping, sequencing, and milestone decision — ending with an outline of steps, milestones, and tickets, verified claim by claim against your sources, plus a handoff to doc-coach for the shareable writeup.

1 skill

Plan work before it starts — author a human-gated spec with its task DAG, and write short tickets someone else can pick up, with no guessed claims.

31 skills

Project framework orchestrator (6-phase workflow)

12 skills · 6 commands · 7 agents · hooks

Issues, native sub-issues, Projects v2, Milestones, and Discussions behind a portable MCP core plus a Claude Code progressive-enhancement layer. Every issue/discussion body carries MIF-conformant frontmatter authored via mif-docs.

8 skills · 2 agents

Guided feature planning — interviews the user, explores the codebase, and writes a structured implementation plan to ~/.claude/plans/

7 skills

UltraPlan 6-phase planning + 11 Clear Thought thinking frameworks

1 skill · 4 agents · hooks

Planning craft: write-plan, work-breakdown, three-point estimate.

5 skills

Development-time bug capture: diagnostics discovered while code is being written become structured, MIF-conformant, lifecycle-managed GitHub issues. Portable MCP core plus opt-in Claude Code enhancement packs; composes with github-pull-requests and github-sdlc-planning.

3 skills

A relentless interview to sharpen a plan or design — frontier-driven rounds of numbered questions with recommended answers. Ported from mattpocock/skills by Matt Pocock (MIT).

2 skills

Takes a PM ticket, builds a full implementation plan with real file paths and code skeletons, then derives a velocity cost estimate from that plan — evidence-based estimation via /estimate

1 skill

Spec sheet before you build — every module, field and screen 5 top open-source apps have

1 skill

Drive a fresh repo through Stage-1 planning artifacts (vision, roadmap, requirements, open questions, architecture options, decisions) and prepare hand-offs for design system + pitch deck, information architecture, screen design, and implementation slate. Stage 2 creates and publishes a Claude Design design system via its setup form first, then generates a deck that inherits it. Resumes from whatever already exists in docs/.

1 skill

Scaffold a new feature: gather requirements, create an isolated workspace, and produce a development plan before writing code

1 skill

Plan and implement features as a stack of short-lived, independently-green PRs using trunk-based development

1 skill

Turn a long list of choices into a self-contained interactive HTML page and read the answers back as structured data.

1 skill

Challenge a feature request before any code: confirm the real problem, check existing capability, weigh alternatives, pass decision gates.

1 skill

Plan a feature, verify every claim against the current code, then build an interactive user-story storyboard page.

1 skill

Full pull-request lifecycle control: create, classify (type/size/risk labels), review-route, link to issues, and couple to Projects v2. Depends on github-sdlc-planning for its shared MIF comment-block reader and Projects v2 tools.

1 skill

Relentless one-question-at-a-time design interview and docs-aware plan stress testing triggered by "roast me".

1 skill

Get grilled on your idea until every design decision is settled.

1 skill