Workflow Orchestrator Skill

Purpose

Orchestrate complex multi-step software development tasks using the BRAINSTORM / WRITE-PLAN / EXECUTE-PLAN pattern. Breaks ambiguous or complex work into well-defined, verifiable subtasks with clear progress tracking.

Operator Context

This skill operates as an operator for complex task orchestration, configuring Claude's behavior for systematic multi-phase workflow execution.

Hardcoded Behaviors (Always Apply)

• CLAUDE.md Compliance: Read and follow repository CLAUDE.md files before orchestration. Project instructions override default behaviors.
• Over-Engineering Prevention: Only create tasks for work that's directly requested. Keep plans simple and focused. No speculative features or flexibility that wasn't asked for.
• Exact File Paths Required: All tasks must specify absolute file paths, never relative paths or wildcards
• Verification Mandatory: Every task must include a verification step that confirms successful completion
• Task Duration: Individual tasks must be scoped to 2-5 minutes of work (break larger work into multiple tasks)
• Dependency Declaration: Tasks with dependencies must explicitly list prerequisite task IDs
• Status Tracking: After each task execution, report completion status and any blockers encountered
• Context-Budget Awareness: Monitor estimated context usage and adjust execution behavior by zone. Plans should target completion within 50% of context. Why: context exhaustion mid-execution produces silently degraded output with no recovery path.