builder-loop

Automating end-to-end build loops involves orchestrating planning, skill forging, and execution to produce reusable project skills. This approach creates plan-driven workflows that steadily improve a project by automating the cycle from initial brief to automated validation.

Skill forging in a plan-driven workflow is the process of creating minimal, reusable skills under a structured directory like skills/<type>/<name>/. It automates the generation of specific capabilities, syncing them for the active agent to maintain a living codebase ready for checks.

Generating and updating IMPLEMENTATION_PLAN.md and prd.json requires an orchestrator that writes the project plan and manages artifacts. This is achieved by feeding a short project brief into an end-to-end build loop that automatically produces and maintains these plan artifacts.

Automated planning and execution cycles are designed specifically for repeatable build cycles in software engineering. By orchestrating a project architect to write plans and a completion director to execute tasks, the system maintains a living codebase ready for automated build validation.

You do not need a full specification to start an automated skill factory. Providing a short project brief is sufficient to begin the end-to-end loop, which then orchestrates the planning, skill forging, and execution phases automatically to produce reusable project skills.

An automated build loop needs a project architect and completion director to properly orchestrate the end-to-end cycle. The architect writes the plan while the director executes tasks, ensuring the skill factory produces minimal reusable skills and maintains a codebase ready for validation.