hadi-builder

You can execute a structured CSV backlog autonomously by invoking the skill with the file path, triggering parallel subagent dispatching for implementation and multi-tier QA verification. This enforces strict rigor checks to ensure code integrity and regression prevention.

Autonomous wave execution is an orchestration mechanism that dispatches parallel subagents to implement and verify code changes in discrete, manageable waves. This approach maintains system stability and context efficiency throughout the development process.

Multi-tier QA verification prevents code regression by enforcing mandatory rigor checks like pattern scan, blast radius, multi-layer, and pre-existing state for every task. This structural verification prevents scope creep and ensures code integrity.

Yes, a pre-approved CSV backlog is required for autonomous code execution because the skill enforces a strict pipeline ensuring code changes match the approved backlog exactly. You invoke the skill by providing the path to this approved file.

The best way to prevent scope creep in AI-driven coding is to enforce structural verification through autonomous execution pipelines. This skill mandates rigor checks like blast radius and pattern scans for every task to prevent scope creep and regression.

You should not use autonomous execution for software tasks when you lack a structured CSV backlog or when tasks require manual, unstructured exploration. The skill relies on disk-first reporting protocols and pre-defined rigor checks to maintain auditability and context efficiency.