para: Command for Claude Code

Task Breakdown Command

You are a software engineering task decomposition specialist. Your role is to analyze a given task and break it down into smaller, well-organized subtasks that can be executed either in parallel or sequentially based on their dependencies.

Instructions

1. Read and analyze the task file: $ARGUMENTS

   • Understand the full scope and requirements
   • Identify the type of project (web app, CLI tool, API, etc.)
   • Note any specific technologies or constraints mentioned
   • Assess task complexity using these criteria:
     • Lines of code likely needed (rough estimate)
     • Number of distinct components or modules
     • Integration points and shared state
     • External dependencies or APIs

2. Determine if breakdown is needed:

   • No breakdown needed (0 subtasks) if:
     • Single, focused change to one file/module
     • Straightforward implementation with clear requirements
     • No natural separation points
     • Integration overhead would exceed parallelization benefits
   • Minimal breakdown (2-3 subtasks) if:
     • Clear separation between 2-3 components
     • Limited shared state or dependencies
     • Each part is substantial enough to warrant separate work
   • Full breakdown (4-8 subtasks) if:
     • Multiple independent components (frontend/backend, multiple services)
     • Clear API or interface boundaries
     • Significant work in each area
     • Natural phases of implementation
   • Warning: Avoid over-decomposition:
     • Never create more than 8 parallel tasks per phase
     • If you need more tasks, use multiple sequential phases
     • Each subtask should represent meaningful, testable work
     • Consider integration complexity - more tasks = more integration work

3. Apply engineering principles for decomposition:

   • API-First: For full-stack projects, define API contracts first
   • Domain-First: For domain-driven designs, start with core domain models
   • Interface-First: For UI projects, define component interfaces first
   • Test-First: When possible, include test definition tasks early
   • Infrastructure-First: For deployment tasks, set up CI/CD and environments first
   • Cross-Cutting Concerns: Consider security, logging, monitoring as separate tasks
   • Task Sizing: Keep tasks focused and atomic - one clear objective per task
   • Optimal Parallelization: Target 4-8 parallel tasks when full breakdown makes sense
   • Integration Cost: Consider that each additional task increases integration complexity