plan-runner:run

To execute a Markdown plan with parallel agents, you provide a file path to the plan-runner. It analyzes the plan into file-disjoint waves, dispatches up to six development and verification agents per wave, and commits results iteratively.

Automated bug aggregation works by running per-wave verification during plan execution. When issues are found, the system aggregates the bugs and automatically generates a targeted fix plan for iterative re-planning and resolution.

Yes, you can orchestrate workflow automation for large Markdown plans. The system coordinates a parallel agent swarm, breaking execution into file-disjoint waves of up to six agents to ensure scalable task dispatch and comprehensive cycle orchestration.

The best way to run parallel development tasks with per-wave verification is using a manifest-driven workflow. This approach dispatches development and verification tasks simultaneously, committing results per wave and triggering automatic re-planning when necessary.

You need a Markdown plan file path to run plan execution cycles. The required input is a structured Markdown document that the orchestrator analyzes to dispatch parallel agents and manage timing, manifests, and verification.

Plan execution requires file-disjoint waves to prevent conflicts when dispatching up to six parallel agents. This orchestration method ensures scalable task dispatch, per-wave commits, and structured verification without manual coordination.