team-lead-orchestrator

To turn requirements into trackable tasks, you need an orchestration process that generates planning artifacts like implementation_plan.md and task.md. This approach translates broad goals into granular, actionable subtasks and clear handoffs for execution teams.

Build-then-Validate sequencing is an orchestration mechanism that enforces builder steps before validator steps during task execution. It ensures the central source of truth directs coding work sequentially, guiding handoffs to appropriate execution skills only after build phases complete.

GitOps pre-flight checks require maintaining a central source of truth and verifying readiness before handing off development tasks. You perform these checks alongside generating implementation_plan.md and task.md artifacts to ensure execution skills receive validated, deployment-ready work.

Yes, you can use task orchestration to manage handoffs between builder and validator execution skills. It directs execution to the appropriate incremental or builder skills for actual coding work, enforcing Build-then-Validate sequencing and maintaining the central source of truth until handoff.

The best way to maintain a central source of truth during software project planning is by orchestrating work through structured artifacts. Automatically generating requirements.md, implementation_plan.md, and task.md files keeps planning data synchronized until execution handoff occurs.

Task orchestration works without external dependencies to generate planning artifacts. It operates independently to translate high-level goals into requirements.md, implementation_plan.md, and task.md files, performing GitOps pre-flight checks before handing off to execution skills.