orch-pipeline

Topics in the source

• Orchestrator Pipeline (shared engine)
• When to Use
• The operation family
• Step 0 — Classify size (right-sizing)
• The phases
• The two gates
• Agent / command map
• Security-review trigger

The orch- skills are thin wrappers. They do not re-implement any work — they classify the request, choose which phases of this pipeline run, and delegate each phase to an existing ECC agent or command. This file is that pipeline. Invoke an operation skill (orch-add-feature, orch-fix-defect, …) rather than this engine directly. This file is the reference they point at. Loaded indirectly whenever an orch- operation skill runs. Read directly only when adding a new operation to the family or tuning the shared phases, gates, or agent map. | Skill | Operation | Trigger | First move | |-------|-----------|---------|------------| | orch-add-feature | feature | capability does not exist yet | research + plan a new slice | | orch-change-feature | tweak | works, but desired behavior differs | amend existing behavior and its tests | | orch-fix-defect | fix | broken; behavior is wrong | reproduce as a failing test, then fix | | orch-refine-code | refactor | behavior stays, structure improves | restructure while keeping tests green | | orch-build-mvp | mvp | bootstrap from a design/spec doc | ingest doc → vertical slices | These wrappers compose existing ECC commands rather than replace them: /f

This is an excerpt. Refer to the complete source and its current requirements.