What problem does it solve?
Orchestrate converts an approved implementation plan into small, isolated, context-safe tasks organized into sequential batches and explicit dependency edges so DAG-aware runners and multi-provider builders can execute work in parallel without conflicts. It enforces messaging standards, validates pipeline state, prevents file-level merge conflicts, and ensures the pipeline advances reliably from plan to build.
Core Features & Use Cases
- Messaging enforcement: mandates loading the standardized messaging format before any pipeline actions to ensure consistent outputs.
- State and artifact handling: verifies pipeline stage, reads the approved plan and optional spec, and records tasks as a JSON artifact in the pipeline store.
- Strategy selection and task decomposition: auto-detects or presents build strategies, decomposes plans into well-sized tasks with acceptance criteria, relevant files, interfaces, and builder subroles.
- Batching and dependency validation: groups tasks into parallel-safe batches while encoding depends_on edges for DAG-aware execution and validates no circular or self-dependencies exist.
- Conflict prevention and safety checks: checks for file creation/modification overlaps within batches and enforces sizing and timeout guidelines to avoid oversized tasks.
- Use cases: breaking an approved feature plan into per-file implementation tasks for parallel builders, converting a bug-fix plan into prioritized fix tasks, or preparing a prototype plan for staged implementation.
Quick Start
Ask the orchestrate stage to break the approved plan file into executable task batches, pick or confirm the suggested strategy, and save the resulting tasks artifact to advance the pipeline to build.
