What problem does it solve? Non-trivial development work in Claude Code often overloads a single session with implementation details, leaving too little context for judgment, review, and verification. This Skill keeps requirements, architecture, planning, and publication in the main session while routing bounded implementation and exploration to reusable subagents. ## Core Features & Use Cases - Model and effort routing: Selects between Fable, Opus, Sonnet, and Haiku aliases with documented escalation triggers so expensive tiers are used only when justified. - Orchestration primitives: Chooses between direct main-session work, Agent-tool subagents, experimental agent teams, and dynamic workflows based on task shape. - Five-phase workflow: Covers analysis and planning, bounded delegation with self-contained worker contracts, main-session review of every diff, targeted fix rounds, and verified publication. - Use Case: When implementing a multi-file feature, the main session writes a file-level plan, delegates two independent work items to Opus subagents, reviews their diffs, runs verification commands itself, and only then commits and reports. ## Quick Start Ask the agent to orchestrate a non-trivial feature or refactor using the maestro workflow, delegating bounded implementation items to subagents while keeping review and commits in the main session.