implementation-agent
Implementation 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.implementation-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 implementation 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 implementation to PR review. - 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/openit
planning-agent
Reads a parent issue, inspects the live codebase, creates a Technical Plan subtask, and creates implementation subtasks. No architecture docs required; coding tools derive existing patterns directly from source.
10pr-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.
10qa-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.
6architect-agent
Reads architecture artifacts generated by init-architect and creates a high-level technical-details subtask with handoff-first context loading, lazy artifact reads, and compact JSON handoff output.
5init-architect
Initializes and maintains architecture artifacts with handoff-first context loading, lazy scoped updates, and compact JSON handoff output for workflow-driven invocations.
4pr-publish-agent
Pushes the current branch, creates a PR linked to the configured tracker issue, comments the PR link on the issue, and moves the issue to In review.
4