loop-da-loop

Automate roadmap execution by applying phase-based implementation loops and validation gates to transition between tasks without manual approval. This enforces a standardized workflow using phase-specific specs, plans, and automated task verification to ensure consistent progress.

Phase tracking works by iterating through defined roadmap phases, managing status updates, and applying validation gates. It requires a repository-local roadmap, phase ledger, and defined architecture documentation to maintain state and ensure consistency across the project.

The best way to manage structured phase transitions is enforcing a standardized workflow with phase-specific specs, plans, and validation gates. This drives the agent through each roadmap phase, from drafting specs to final validation, without pausing for approval at every sub-task.

You should not use automated phase loops for simple, single-step tasks or unstructured workflows lacking defined architecture documentation. This approach requires a repository-local roadmap and structured multi-phase progress tracking to maintain state and validate tasks effectively.

You need a repository-local roadmap, a phase ledger, and defined architecture documentation to maintain state and ensure consistency. These inputs provide the structured, multi-phase progress tracking necessary to automate task verification and phase transitions.

No, validation gates are enforced as part of the standardized workflow to ensure consistent progress and automated task verification. Skipping them would break the phase-based implementation loops required for structured, multi-phase software development.