Marketplace

plan-builder

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

allowed_tools: Read, Write, Edit

$ Installieren

git clone https://github.com/majesticlabs-dev/majestic-marketplace /tmp/majestic-marketplace && cp -r /tmp/majestic-marketplace/plugins/majestic-engineer/skills/plan-builder ~/.claude/skills/majestic-marketplace

// tip: Run this command in your terminal to install the skill


name: plan-builder description: Write implementation plans with appropriate templates based on complexity. Provides minimal, standard, and comprehensive templates for different scope levels. allowed-tools: Read, Write, Edit

Plan Builder

Write implementation plans using the appropriate template based on complexity.

Template Selection

ComplexityWhen to UseTemplate
MinimalSimple bugs, small improvements, clear single-file changesresources/minimal.md
StandardMost features, complex bugs, team collaborationresources/standard.md
ComprehensiveMajor features, architectural changes, multi-phase workresources/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
  • Definition of Done 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'tDo
Use comprehensive for simple bugsMatch template to actual complexity
Skip acceptance criteriaAlways include testable criteria
Leave placeholder textFill all sections or remove them
Over-plan obvious changesMinimal template exists for a reason

Repository

majesticlabs-dev
majesticlabs-dev
Author
majesticlabs-dev/majestic-marketplace/plugins/majestic-engineer/skills/plan-builder
13
Stars
0
Forks
Updated5d ago
Added1w ago