What problem does it solve? Complex tasks like end-to-end feature development or multi-phase infrastructure changes require coordinating multiple skills, tools, and context sources in the right order, and ad-hoc execution leads to missed validation, context overload, and no rollback path. ## Core Features & Use Cases - Orchestration Planning: Breaks a task into discrete phases, maps required skills to each phase, and defines dependencies between steps. - Context Loading Strategy: Specifies which files, APIs, or databases to load incrementally per phase to avoid context window overflow. - Validation & Rollback: Defines validation checkpoints, success criteria, and rollback procedures for every destructive step. - Use Case: Adding a new Docker service to a homelab by orchestrating a change-planning phase, a docker-compose editing phase, deployment preparation, and execution with verification and rollback instructions. ## Quick Start Create an orchestration plan for adding a new Docker service to my homelab that combines change planning, compose editing, and deployment with validation checkpoints and rollback steps.
