harness-work

Automating task execution from a markdown plan requires a unified workflow skill that processes Plans.md end-to-end. This skill bridges plan-to-completion by automating lifecycle stages from TODO to done, handling solo, parallel, and breezing execution modes with auto-selection.

Orchestrating parallel team tasks is best handled by execution modes that support concurrent runs. This skill automates parallel workflow orchestration using explicit flags like --parallel, generating sprint contracts and applying reviewer checks to enforce guardrails across the team.

Yes, a Plans.md file is required to start automated sprint execution. You must also define a Definition of Done, and can optionally integrate sprint-contract scripts, reviewer checks, and Codex or internal reviewers to enforce workflow guardrails.

Automated workflow orchestration handles CI failures by triggering automatic re-planning to keep work moving. When continuous integration fails during task execution, the system intervenes, adjusts the plan, and applies rollback mechanisms to maintain progress.

Yes, you can control workflow automation modes for single tasks using explicit flags. The system supports auto-mode selection by default, but you can enforce specific behaviors like --breezing or --codex to dictate how individual or full parallel team runs are executed.

Ready-for-review validation in automated task orchestration is the process of verifying that completed work meets sprint contracts before approval. It enriches reviewer checks and ensures lifecycle completeness from cc:TODO to cc:完了 with automated reporting.