plan-builder

Write implementation plans with appropriate templates based on complexity. Provides minimal, standard, and comprehensive templates for different scope levels.

⭐13stars🔀0forks📁View on GitHub🕐Updated Jan 3, 2026⬇️1downloads

When & Why to Use This Skill

The Plan Builder skill automates the creation of structured software implementation plans by selecting the optimal template based on task complexity. It solves the problem of inconsistent documentation and poorly defined scopes by providing minimal, standard, and comprehensive frameworks. This ensures that every technical task—from minor bug fixes to major architectural overhauls—is backed by thorough research, clear acceptance criteria, and well-defined execution steps, significantly boosting engineering team productivity and documentation quality.

Use Cases

  • Bug Fix Documentation: Quickly generate minimal implementation plans for simple patches to ensure clear acceptance criteria and file tracking without administrative overhead.
  • Standardized Feature Development: Use standard templates for typical development tasks to provide context, research links, and risk assessments for peer reviews.
  • Architectural Overhauls: Leverage comprehensive templates for large-scale features and system changes that require multi-phase planning and stakeholder alignment.
  • Specialized Technical Context: Automatically include dedicated sections for UI design references or DevOps infrastructure when the task scope requires it.
nameplan-builder
descriptionWrite implementation plans with appropriate templates based on complexity. Provides minimal, standard, and comprehensive templates for different scope levels.
allowed-toolsRead, Write, Edit

Plan Builder

Write implementation plans using the appropriate template based on complexity.

Template Selection

Complexity When to Use Template
Minimal Simple bugs, small improvements, clear single-file changes resources/minimal.md
Standard Most features, complex bugs, team collaboration resources/standard.md
Comprehensive Major features, architectural changes, multi-phase work resources/comprehensive.md

Selection Criteria

Use Minimal When

  • Fix is obvious and localized
  • Single file or 2-3 related files
  • No architectural decisions needed
  • Clear acceptance criteria from description

Use Standard When (Default)

  • Multiple components affected
  • Requires research or external docs
  • Team needs context for review
  • Has dependencies or risks

Use Comprehensive When

  • New system or major feature
  • Multiple phases of work
  • Architectural decisions required
  • Cross-cutting concerns (security, performance)
  • Involves multiple teams or stakeholders

Plan Output

Write plans to: docs/plans/[YYYYMMDDHHMMSS]_<title>.md

Include in every plan:

  • Research findings with file paths (e.g., src/models/user.rb:42)
  • External documentation URLs
  • Related issues/PRs if known
  • Acceptance Criteria from user input (populated from blueprint Step 2)

Conditional Sections

UI Features

Include "Design System Reference" section when feature involves:

  • Pages, components, forms, buttons, modals
  • Visual design elements

DevOps Features

Include "Infrastructure Context" section when feature involves:

  • Terraform/OpenTofu, Ansible, cloud resources
  • Docker, CI/CD, infrastructure

Anti-Patterns

Don't Do
Use comprehensive for simple bugs Match template to actual complexity
Skip Acceptance Criteria Always include testable criteria
Leave placeholder text Fill all sections or remove them
Over-plan obvious changes Minimal template exists for a reason