quality-gates

To prevent over-engineering, apply YAGNI principles during task planning to ensure solutions strictly match project scope. This approach blocks progress on features that exceed requirements, requesting clarification or task breakdown before development begins.

Blocking conditions in task planning are critical questions, missing dependencies, or failed attempts that halt development progress. Identifying these thresholds before work begins ensures tasks are well-defined and feasible, preventing wasted effort and rework.

Assess task complexity using a 1-5 scoring scale to determine if task breakdown is needed. If a task scores high in complexity, it triggers a quality gate that requests further clarification or decomposition before development proceeds.

Automated quality gate enforcement works without external dependencies, relying on internal scripts, references, and checklists. It analyzes task requirements directly to identify blockers and apply YAGNI principles independently.

The best way to handle workflow escalation for unmanageable tasks is to trigger complexity assessment and task breakdown. This escalates complex items by blocking progress and requesting clarification until requirements are clear and dependencies are met.