harness-orchestrator

You coordinate a multi-agent build pipeline by splitting software assembly into Planner, Builder, and Evaluator roles with deterministic, file-based handoffs and stage gates. This structure isolates planning, implementation, and QA to produce safe context resets.

A delta-spec planning approach rescues troubled codebases by auditing the existing repository to generate targeted delta specifications. The Planner uses these specifications to define sprint work, allowing the Builder to implement changes without rewriting the entire project.

To bootstrap a greenfield project, you provide a project prompt and let the orchestrator initialize the pipeline. It creates a .harness directory at the project root to manage state, artifacts, and handoffs across the Planner, Builder, and Evaluator phases.

Yes, the build pipeline supports resume-from-anywhere workflows by using a .harness directory for state, artifacts, and handoffs. This file-based approach enables safe context resets so you can stop and resume complex software assembly without losing progress.

Yes, you need a .harness directory at the project root to coordinate inputs, outputs, and state across phases. This directory stores the artifacts and frontmatter-defined metadata required for deterministic stage gates between the Planner, Builder, and Evaluator.

You should use a three-agent build pipeline for complex software assembly or rescuing troubled codebases where isolated roles are needed. Splitting Planner, Builder, and Evaluator roles with stage gates ensures quality assurance and polish loops that a single agent cannot easily self-enforce.