skill-orchestrator-patterns

# Orchestrator Patterns This skill defines reusable patterns for the Orchestrator's pipeline stages, enabling compressed prompts. > [!IMPORTANT] > **Reference this skill for Stage Cycle logic.** > The Orchestrator uses these patterns instead of verbose per-scenario instructions. ## Stage Dispatch Table | Stage | Agent Prompt | Reviewer Prompt | Max Cycles | Skill | Next Stage | |-------|--------------|-----------------|------------|-------|------------| | Analysis | `02_analyst` | `03_task_reviewer` | 2 | `skill-archive-task` | Architecture | | Architecture | `04_architect` | `05_architecture_reviewer` | 2 | `architecture-design` | Planning | | Planning | `06_planner` | `07_plan_reviewer` | 2 (1 rev) | `planning-decision-tree` | Execution | | Execution | `08_developer` | `09_code_reviewer` | 2 (1 fix) | `developer-guidelines` | Next Task / Completion | --- ## Pattern: Stage Cycle ### Applicability - Stages with Init → Review → Revision flow - Applies to: Analysis, Architecture, Planning, Execution ### Init Phase ``` INPUT: {stage_name}, {agent_prompt}, {artifact_path} FLOW: 1. Read agent prompt 2. Pass required context to agent 3. Wait for result: { artifact_file, blocking_questions } DECISION: - IF blocking_questions → STOP, ask user (Scenario 14) - ELSE → proceed to Review ``` ### Review Phase ``` INPUT: {artifact_file}, {reviewer_prompt}, {iteration} FLOW: 1. Read reviewer prompt 2. Pass artifact + context to reviewer 3. Wait for result: { review_file, has_cr...