orchestrator-workflow

name	orchestrator-workflow
description	Coordinate a feature or bug request from intake through promotion, planning, execution, validation, and review by selecting the correct small or large path and delegating to migrated Codex specialists when available.

Orchestrator Workflow

Top-level delivery orchestration workflow for Codex.

Required Shared Skills

Always apply:

• policy-compliance-order
• feature-promotion-lifecycle
• repo-automation-adapter
• atomic-plan-contract
• acceptance-criteria-tracking
• pr-context-artifacts
• pr-base-branch-merge-base

Use as needed:

• csharp-change-budget-router
• powershell-change-budget-router
• feature-review

Role

• Coordinate the mission from intake through completion.
• Resolve required specialist delegation mechanically instead of by judgment.
• Required delegated specialists:
  • atomic-planner
  • atomic-executor
  • feature-review
  • feature-reviewer
  • task-researcher
  • prd-feature
  • staged-review
  • epic-review
  • status-updater
  • python-typed-engineer
  • powershell-typed-engineer
  • csharp-typed-engineer
  • typescript-engineer
  • commit-steward
• Deterministic availability rule:
  • if the host exposes spawn_agent and the required .codex/agents/<name>.toml file exists, treat that delegated specialist as available,
  • do not infer unavailability from missing nicknames, missing prior agent instances, or lack of a dedicated launcher alias.
• Every required delegated specialist must exist as a native Codex agent under .codex/agents/. If a required agent file is missing, set blocked_reason to spawn_agent_unavailable and stop.
• Required delegated steps MUST delegate or stop execution.
• If a required delegated handoff cannot be started, resumed, or completed with a receipt, persist blocked state and stop. Do not perform that step directly.
• Direct local implementation is prohibited. Non-implementation coordination steps may execute locally only when they are not designated below as required delegated handoffs.

Root-only epic boundary

This workflow handles one feature or bug. It must never delegate to epic-planner or epic-orchestrator. When intake is epic-scale or names an epic manifest, stop before delegation, emit EPIC_ENTRY_REQUIRES_ROOT, and direct the user to root-session epic-plan, epic-run, or epic-orchestrate. An unauthorized epic start is rejected by the root-provenance system under EPIC_INVOCATION_ORIGIN_BLOCKED.

Epic preparation child

The literal marker Preparation mode: true selects route_id: preparation. Complete promotion, research, feature documents, atomic planning, and preflight only. After PREFLIGHT: ALL CLEAR, commit the prepared documents and plan and stop at S5_atomic_execution. Execution, review, PR, and CI statuses are not-applicable; no DONE transition is valid.

Checkpoint Contract

Canonical checkpoint path:

• artifacts/orchestration/orchestrator-state.json

Canonical route matrix:

• config/orchestration-routing.json

Persist and reuse these fields exactly:

• objective
• change_budget_estimate
• path_selected
• promotion-type
• short-name
• pre-issue-branch
• final-branch
• branch-rename-status
• relativeFile
• long-name
• issue-num
• feature-folder
• work-mode
• plan-path
• review-status
• remediation-inputs-path
• remediation-plan-path
• remediation-pass
• commit-context-path
• pr-context-base-branch
• completed_steps
• next_step
• last_updated
• step5_status
• step6_status
• step7_status
• step8_status
• step9_status
• step10_status
• delegation_receipts
• blocked_reason
• route_id
• required_agents
• required_skills
• required_mcp_tools
• skill_receipts
• mcp_call_receipts
• local_execution_overrides
• delegation_bypasses
• lifecycle_operations
• pre-implementation-violation

Plan-path invariant:

• ${plan-path} is resolved only after ${feature-folder} exists.
• The orchestrator MUST enumerate existing ${feature-folder}/plan*.md files in deterministic filename order before planner delegation.
• If any existing plan file is present, ${plan-path} MUST be that first existing file. Do not persist or delegate against ${feature-folder}/plan.md when a timestamped scaffolded plan already exists.
• If checkpoint state conflicts with the resolved existing plan file, correct checkpoint state before delegation and do not create a duplicate plan.

For small-path runs, also persist:

• bootstrap_mode
• phase0_execution_summary
• small_path_qc_summary
• small_path_audit_artifacts
• resume_after_manual_bootstrap

Status enums:

• step5_status / step6_status / step7_status / step8_status / step9_status / step10_status MUST use one of:
  • not-applicable
  • pending
  • delegated
  • verified
  • blocked

Blocked-reason enum:

• blocked_reason MUST be one of:
  • none
  • checkpoint_conflict
  • lifecycle_preconditions_missing
  • spawn_agent_unavailable
  • delegation_launch_failed
  • delegate_no_receipt
  • delegate_contract_incomplete
  • validator_failed
  • user_requested_stop
  • review_status_missing
  • commit_context_missing
  • no_staged_changes
  • pre_implementation_gate_violation

Pre-implementation violation schema:

• pre-implementation-violation MUST be either null or an object with:
  • violated_gate
  • attempted_action
  • known_mutated_files
  • corrective_next_step
  • recorded_at

Delegation receipt schema:

• delegation_receipts MUST be a list of objects with:
  • step
  • agent_name
  • agent_id
  • skill_source
  • started_at
  • completed_at
  • result_signal
  • artifact_paths

Skill receipt schema:

• skill_receipts MUST be a list of objects with:
  • skill
  • required
  • acknowledged_at_phase
  • evidence

MCP receipt schema:

• mcp_call_receipts MUST be a list of objects with:
  • tool
  • ok
  • evidence

Completion-state invariants:

• route_id MUST identify an entry in config/orchestration-routing.json.
• required_agents, required_skills, and required_mcp_tools MUST exactly match the selected route matrix entry.
• every required agent MUST have a matching delegation_receipts[].agent_name.
• every required skill MUST have a matching required skill_receipts[].skill with non-empty evidence.
• every required MCP tool MUST have a successful mcp_call_receipts[].tool receipt with non-empty evidence.
• local_execution_overrides and delegation_bypasses MUST be empty lists at completion.
• every recorded lifecycle_operations[] item MUST use surface: "mcp".

Required-delegation step map:

• small path:
  • Step 5 -> atomic-planner
  • Step 6 -> atomic-executor
  • implementation delivery -> language-resolved generated typed-engineer profile
  • Step 9 -> atomic-executor
  • Step 10 -> feature-reviewer
• large path:
  • Step 7 -> atomic-planner
  • Step 8 -> atomic-executor
  • Step 9 -> feature-reviewer
• remediation planning:
  • review-triggered remediation planning -> atomic-planner
  • remediation preflight clearance -> atomic-executor
  • remediation execution -> atomic-executor
  • remediation commit message -> commit-steward
  • remediation re-review -> feature-reviewer

Deterministic Handoff Result Contract

Do not advance on summaries alone when an exact result signal is required.

• feature review result:
  • REVIEW_STATUS: PASS
  • REVIEW_STATUS: REMEDIATION_REQUIRED
  • FEATURE_FOLDER: <path>
  • POLICY_AUDIT: <path>
  • CODE_REVIEW: <path>
  • FEATURE_AUDIT: <path>
  • REMEDIATION_INPUTS: <path-or-NONE>
  • REMEDIATION_PLAN: <path-or-NONE>
• remediation preflight result:
  • PREFLIGHT: ALL CLEAR
  • PREFLIGHT: REVISIONS REQUIRED
• commit-steward result:
  • one fenced text code block only

If an exact signal or required path field is missing, set the relevant step to blocked, set blocked_reason to delegate_contract_incomplete, and stop.

Resume Rules

1. Read the checkpoint first when it exists.
2. If the recorded mission is incomplete, resume from next_step.
3. If the checkpoint belongs to an unrelated in-progress mission, stop with blocked_reason: checkpoint_conflict.
4. Do not rename, back up, or create sidecar checkpoint files to work around a canonical checkpoint conflict.
5. Restart only when the user explicitly requests restart.
6. Do not recompute persisted variables when valid stored values already exist.

Routing Rules

1. Estimate the likely touched production files and test files first.
2. Determine the dominant implementation language.
3. If the scope is primarily C#, use csharp-change-budget-router.
4. If the scope is primarily PowerShell, use powershell-change-budget-router.
5. If the scope is mixed-language, ambiguous, or unsupported by an existing change-budget router, fail closed to the large path.
6. Treat any request outside the applicable small-path budget as large path.
7. Select route_id from config/orchestration-routing.json and persist the exact required agent, skill, and MCP lists from the matrix before starting lifecycle automation.
8. Keep topology routing separate from C1-C4 model routing. Persist both topology and model-routing receipts and select the exact generated Codex deployment agent before every delegation.
9. Use Terra/High for standalone ceiling-C3 work. Use Sol/High for C3 epic children or C3 work in an orchestration whose monotonic ceiling is C4. Do not infer this overlay from file count.

Small Path

Use the small path only when the applicable language router clears it.

Required behavior:

1. Set ${work-mode} to minor-audit.
2. Use feature-promotion-lifecycle as the source of truth for lifecycle variables, branch naming, and ${plan-path} resolution.
3. Route all promotion, issue, and feature-folder automation through repo-automation-adapter.
4. Enforce lifecycle preconditions before any active-folder authoring:
   • route metadata persistence must be complete in the canonical checkpoint before potential-entry creation
   • ${pre-issue-branch} must be created or verified before potential-entry creation
   • ${relativeFile} must resolve to a real potential markdown path and must not be NONE, TBD, or empty
   • ${issue-num} must be numeric before final branch rename or new_active_feature_folder runs
   • final branch rename must complete before new_active_feature_folder runs
   • do not create or edit ${feature-folder}/issue.md, ${feature-folder}/spec.md, ${feature-folder}/user-story.md, or plan*.md until potential-entry creation, promotion, final branch rename, and folder creation all succeed
   • if any lifecycle precondition fails, set the relevant step status to blocked, set blocked_reason to lifecycle_preconditions_missing, and stop
5. Enforce minor-audit folder integrity:
   • ${feature-folder}/issue.md must exist
   • ${feature-folder}/spec.md must be absent
   • ${feature-folder}/user-story.md must be absent
6. Spawn atomic-planner to create or revise the minimal plan at ${plan-path}.
   • Include the directive DIRECTIVE: MINIMAL-AUDIT PLAN REQUIRED
   • Require the same ${plan-path} to be updated in place
   • Do not continue until the planner reports PREFLIGHT: ALL CLEAR
   • Record a delegation receipt and set step5_status to verified before continuing
   • If the handoff cannot be started or does not return a receipt, set step5_status to , set , and stop

• MUST delegate to atomic-executor for validation and checklist updates
• Record a delegation receipt and set step9_status to verified before continuing
• If the handoff cannot be started or does not return a receipt, set step9_status to blocked, set blocked_reason, and stop

11. Run reduced audit:

• MUST delegate to feature-reviewer
• require the exact REVIEW_STATUS and artifact-path fields from the review result
• Record a delegation receipt and set step10_status to verified before continuing
• If the handoff cannot be started or does not return a receipt, set step10_status to blocked, set blocked_reason, and stop

12. If review returns REVIEW_STATUS: REMEDIATION_REQUIRED, run the shared remediation loop.

• Treat the returned REMEDIATION_INPUTS and REMEDIATION_PLAN paths as mandatory inputs
• If any required remediation handoff cannot be started or does not return a receipt, set blocked_reason and stop

Large Path

Use the large path for any request that exceeds or bypasses the small-path router.

Required behavior:

1. Set ${work-mode} to:
   • full-feature for feature work
   • full-bug for bug work
2. Use feature-promotion-lifecycle as the source of truth for lifecycle variables, branch naming, and ${plan-path} resolution.
3. Route all promotion, issue, and feature-folder automation through repo-automation-adapter.
4. Enforce lifecycle preconditions before any active-folder authoring:
   • route metadata persistence must be complete in the canonical checkpoint before potential-entry creation
   • ${pre-issue-branch} must be created or verified before potential-entry creation
   • ${relativeFile} must resolve to a real potential markdown path and must not be NONE, TBD, or empty
   • ${issue-num} must be numeric before final branch rename or new_active_feature_folder runs
   • final branch rename must complete before new_active_feature_folder runs
   • do not create or edit ${feature-folder}/issue.md, ${feature-folder}/spec.md, ${feature-folder}/user-story.md, or plan*.md until potential-entry creation, promotion, final branch rename, and folder creation all succeed
   • if any lifecycle precondition fails, set the relevant step status to blocked, set blocked_reason to lifecycle_preconditions_missing, and stop
5. Complete the requirements-authoring steps before planning:
   • fill the potential entry details
   • create or refresh research artifacts
   • complete spec.md and user-story.md when the selected work mode requires them
6. Prefer dedicated migrated specialists for those authoring steps when they exist.
7. When those specialists are not yet migrated, perform the authoring steps directly without changing template headings.
8. Spawn atomic-planner to finalize ${plan-path} and require PREFLIGHT: ALL CLEAR. Hard enforcement for Step 7:
   • Before spawning atomic-planner, resolve ${plan-path} by enumerating existing ${feature-folder}/plan*.md files. Reuse the first existing file in deterministic filename order, including timestamped scaffolded plans.

Shared Remediation Loop

Apply this loop after any required review returns REVIEW_STATUS: REMEDIATION_REQUIRED.

1. Persist review-status, remediation-inputs-path, remediation-plan-path, and remediation-pass in the checkpoint.
2. Delegate atomic-executor in validation-only mode against the exact remediation-plan-path.
3. If the executor returns PREFLIGHT: REVISIONS REQUIRED, delegate atomic-planner to update the same remediation-plan-path in place and then repeat preflight clearance.
4. Only after PREFLIGHT: ALL CLEAR, delegate atomic-executor to execute the remediation plan exactly as written.
5. Stage all files with git add -A.
6. If staging is empty after execution, set blocked_reason to no_staged_changes and stop.
7. Use repo-automation-adapter to run MCP tool collect_commit_context, capture the returned on-disk artifact path as commit-context-path, and stop with blocked_reason: commit_context_missing if that path is unavailable.
8. Delegate commit-steward using commit-context-path as the authoritative staged-change input.
9. Commit the staged work with the exact message returned by commit-steward.
10. Use repo-automation-adapter to refresh PR-context artifacts through MCP tool collect_pr_context with the resolved base branch.
11. Delegate feature-reviewer again with the refreshed PR context.
12. If the new review still returns REVIEW_STATUS: REMEDIATION_REQUIRED, increment remediation-pass and repeat the loop. Exit only when the latest review returns REVIEW_STATUS: PASS.

Completion Gates

Do not claim mission completion until all of the following are true:

• the selected path completed end to end
• all required delegations completed with receipts
• small-path implementation has a receipt from the exact language-specific generated typed-engineer deployment profile
• all required skills have skill_receipts with evidence
• all required MCP tools have successful mcp_call_receipts
• no local execution override or delegation bypass is recorded
• the checkpoint is updated with the final state
• the canonical checkpoint path was used without sidecar replacement or backup substitution
• ${relativeFile} is a real promoted-input path and ${issue-num} is numeric when lifecycle setup was required
• ${feature-folder} and ${plan-path} are known when lifecycle setup was required
• route metadata, selected work mode, branch state, lifecycle receipts, and folder readiness are present before implementation begins
• the approved plan is executor-compliant and references the required baseline and final-QA evidence tasks
• required review artifacts exist on disk
• small path has Phase 0 evidence plus reduced audit artifacts
• large path has policy, code, and feature audit artifacts
• required baseline and final-QA evidence artifacts referenced by the approved plan exist on disk
• any required remediation artifacts exist on disk and the latest re-review is clean
• any required remediation loop run also includes a remediation execution receipt, a remediation commit receipt, and a final REVIEW_STATUS: PASS
• validator-backed checks for the approved plan, policy audit, code review, feature audit, and checkpoint state pass
• the canonical checkpoint passes validate_orchestration_artifacts with artifact_type: "orchestrator-state", require_complete: true, require_codex_topology: true, and require_codex_model_routing: true
• required GitHub checks pass for the current PR head SHA before PR/DONE completion

Hard Constraints

• Do not stop after one delegation when required downstream steps remain.
• Do not infer specialist unavailability from missing nicknames or absent prior subagent instances.
• Do not call drmCopilotExtension.* directly from this workflow.
• Do not bypass repo-automation-adapter for host-specific lifecycle steps.
• Do not rename, back up, or create sidecar checkpoint files to avoid using the canonical checkpoint path.
• Do not proceed when the canonical checkpoint belongs to another in-progress mission; stop and report the conflict.
• Do not create or edit active feature docs before route metadata persistence, pre-issue branch setup, potential-entry creation, issue promotion, final branch rename, and active-folder creation succeed.
• Do not call new_active_feature_folder before ${issue-num} is numeric, backed by promotion output, and the final branch rename is complete.
• Do not begin implementation edits, formatters, tests, staging, commits, or implementation delegation when route metadata, branch state, lifecycle receipts, or folder readiness are missing.
• Do not persist placeholder lifecycle values such as NONE or TBD for ${relativeFile}, ${issue-num}, ${feature-folder}, or ${plan-path} once lifecycle setup begins.
• Do not create replacement audit artifacts yourself for any required delegated review step.
• Do not execute required delegated steps locally as a fallback.
• Do not implement small-path production changes in the coordinating thread; the routed typed-engineer deployment is mandatory.
• Do not accept stale PR-context artifacts, unsupported checklist checkoffs, or missing required evidence as PASS outcomes.
• Do not treat Codex lifecycle hooks as the hard completion boundary; use deterministic validator and CI gates for completion enforcement.
• Do not claim completion without reporting the checkpoint path and the created or updated artifact paths.