planning-agent
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.sequenceto understand the expected stage order. - Read
workflow.agents.planning-agentto 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
dependsOnlists 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
nextagent. - If
invocationismanual, 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.
More from vishal2457/open-orchestra
pr-review-agent
Runs a diff-first PR review with handoff-first context loading, lazy spec extraction, architecture-impact detection, and compact review-to-implementation findings handoff.
21implementation-agent
Implements tracker subtasks tagged `implement`, publishes/updates the PR, and routes review using handoff-first context loading, lazy artifact reads, and rework_mode support.
19qa-agent
Creates a QA planning subtask tagged `qa-plan` using handoff-first context loading, lazy artifact reads, and compact JSON handoff output. Depends on requirements and planning being done.
15requirements-ticket-agent
Drafts initial ticket requirements by asking targeted clarifying questions and producing a structured ticket with handoff-first context loading, lazy artifact reads, and compact JSON handoff output.
14init-architect
Initializes and maintains architecture artifacts with handoff-first context loading, lazy scoped updates, and compact JSON handoff output for workflow-driven invocations.
12triage-agent
Performs lightweight workflow triage on a parent issue, classifies execution track as trivial|standard|complex, sets skip_steps guidance, and emits a compact handoff summary for downstream agents without reading full issue history.
10