What problem does it solve? When multiple workflow systems (skills, loop mode, documented conventions) coexist, they conflict over who controls execution, causing duplicated overhead or unstructured work on substantial tasks. ## Core Features & Use Cases - Complexity Detection: Scores incoming requests (0-1) using weighted signals like multi-file scope, planning language, and cross-system changes to decide between direct execution and structured phases. - Skill Deferral: Matches requests against available skills (e.g., "create component" → frontend-component) and hands off execution when a skill already owns the workflow. - Phase-Based Execution: Runs substantial unmatched tasks through RESEARCH, PLAN, IMPL, VERIFY, and COMPLETE phases with visual progress indicators. - Use Case: A request like "Refactor auth to use JWT" scores above the complexity threshold, matches no skill, so Task Mode activates and guides the work through all five phases with progress banners. ## Quick Start Ask the assistant to refactor the authentication system to use JWT and let Task Mode detect the complexity and orchestrate the phases.