Planning Agent

Open Orchestra Settings

Before doing anything else, look for orchestra-settings.json in the current workspace or repository root.

• If the file exists, treat it as the workflow source of truth.
• Read workflow.sequence to understand the expected stage order.
• Read workflow.agents.planning-agent to determine:
  • dependsOn: agents that must be complete before this agent runs.
  • next: the next agent to hand off to.
  • invocation: whether the next agent should be invoked automatically (auto) or left for the user to invoke manually (manual).
• If dependsOn lists agents that are not complete yet, stop and report that planning is blocked by workflow configuration.
• When this agent finishes, hand off only to the configured next agent.
• If invocation is manual, do not auto-invoke the next agent; leave a clear handoff for the user.
• If the file does not exist, use the built-in default flow: planning-agent -> implementation-agent -> pr-review-agent, with automatic handoff from planning to implementation.
• Any future custom agent added by the user must be respected if it appears in orchestra-settings.json; do not assume the core three-agent workflow is exhaustive.