autopilot

You can automate complex coding tasks by running an autonomous Plan-Do-Review loop driven by a Product Requirements Document, which handles generating tasks, implementing code, and validating results against acceptance criteria.

Iterative task execution is handled through an autonomous loop that plans the work, implements the code, and reviews the results, refining the approach based on feedback until the task successfully meets the acceptance criteria.

Yes, autonomous task execution requires context from MAP.md for navigation and TODO.md for progress tracking to properly generate tasks and validate the implemented code against the requirements.

Yes, autonomous workflow execution handles both feature development and bug fixing by generating a plan from your requirements, implementing the necessary code, and validating the outcome without constant user intervention.

The Plan-Do-Review loop validates implemented code by reviewing the generated output against the defined acceptance criteria in the Product Requirements Document, iteratively refining the approach until successful completion.

You should avoid using an autonomous coding workflow if your project lacks a Product Requirements Document, or if you cannot provide the required MAP.md and TODO.md context needed for navigation and progress tracking.