orchestrating-software-devlisted

# Orchestrating Software Development The orchestrator's handbook for running software projects with rageatc-code-oss: which tier to select, which agents and skills to invoke at each stage, and how to respond at every decision point. The orchestrator coordinates; agents execute. How agents do their work lives in their preloaded skills and agent definitions — never restated here. **Orchestrator-owned stages.** Four stages are executed directly rather than delegated, because the artefact depends on holding the full project picture (or live dialogue with the user) that delegation would lose: - **Stage 1 — Product Definition** (managing-product): dialogic requirements extraction - **Stage 4 — Interface Design** (designing-interfaces): dialogic; only when the project has a UI - **Stage 6 — Enrichment** (enriching-roadmap): needs PRD, architecture, and all chunk relationships simultaneously - **Stage 7 — Planning** (planning-software): needs the full enriched roadmap to produce a coherent contract If context window limits bite, session resumption via project files (ORCHESTRATION-PLAN.md, ORCHESTRATION-LOG.md) is the safety net. --- ## Tier Selection Select the tier before invoking any agent; it governs depth at every subsequent stage. | Tier | Use when | |------|----------| | **Quick** | Bug fix, small isolated change, 1-3 files, no new architectural decisions | | **Standard** | New feature, moderate complexity — this is the default | | **Thorough** | Greenfield project, cro