create-plan

Generate structured implementation plans with Mermaid or ASCII diagrams and dependency graphs.

1|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/dopsonbr/agent-kit --skill create-plan-dopsonbr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-plan
Source: https://github.com/dopsonbr/agent-kit/tree/main/content/skills/plan-create
Command: npx skills add https://github.com/dopsonbr/agent-kit --skill create-plan-dopsonbr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bun, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill eliminates the chaos of unstructured development by creating detailed, executable implementation plans with diagrams and dependency tracking.

Core Features & Use Cases

  • Structured Planning: Break down complex features into manageable phases with clear dependencies.
  • Visual Architecture: Generate Mermaid and ASCII diagrams to illustrate component relationships and data flows.
  • Use Case: Before implementing a new authentication system, use this Skill to create a comprehensive plan with component diagrams, testing strategies, and rollback procedures.

Quick Start

Use the create-plan skill to generate an implementation plan for adding user preferences to the API.

Core Features & Use Cases

  • Token Management: Automatically enforces 5000-token limits and suggests subplan strategies for large initiatives.

Frequently Asked Questions about create-plan

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

FAQPage Schema
How do I create an implementation plan with diagrams before coding?

Implementation planning generates structured breakdowns of features into phases with visual diagrams and dependency tracking. Use this Skill to map component relationships, data flows, and testing strategies before development begins, reducing rework and clarifying architecture decisions.

What should I include in a development plan for a complex feature?

A comprehensive plan includes sequential numbered phases, Mermaid or ASCII diagrams showing component relationships, a dependency graph tracking task ordering, and a testing strategy covering each phase. This Skill enforces these elements while staying within token limits for focused scope.

Can I use planning diagrams for refactoring or only new features?

Planning diagrams apply to feature planning, refactoring, and multi-step development work. This Skill generates executable plans with visual clarity across all three contexts, helping teams coordinate changes and anticipate integration challenges.

How does dependency tracking improve implementation planning?

Dependency graphs visualize task ordering and component relationships, revealing blockers and parallelizable work. This Skill generates these graphs automatically within plans, enabling teams to sequence work efficiently and identify critical paths before coding begins.

What's the token limit for implementation plans, and why does it matter?

Plans enforce a 5000-token hard limit with an optimal 2000–3000 range. This constraint forces focused scope definition; for larger initiatives, the Skill suggests breaking work into subplans, preventing overwhelming single-phase deployments and enabling staged rollouts.

Do I need a specific format for numbering phases in my plan?

Phases are sequentially numbered and stored under docs/plans. This standardized format ensures consistency across projects, makes plans machine-readable for tracking and automation, and improves team communication through predictable structure.