What problem does it solve? When a request does not clearly map to a single workflow, or bundles several unrelated asks across files and domains, it is unclear which command should handle it. This Skill acts as the DoFlow dispatcher: it announces session status, decomposes multi-part requests into validated work packages, routes each package to the right /do-* skill, selects the best available search or analysis tool, and produces scoped effort estimates before any work begins. ## Core Features & Use Cases - Command Dispatch & Session Status: With no arguments it announces the DoFlow session and shows the core command reference; with a known /do-* command it forwards directly to that skill. - Multi-Part Task Decomposition: Splits bundled requests into sequenced or independent work packages, proposes a task class per package, and has the runtime validate each class before routing (depths: shallow, normal, deep). - Capability & Tool Routing: Queries the live capability router to pick the right provider for search, dependency tracing, blast-radius analysis, or test execution, with fallback chains when Semble or Graphify are unavailable. - Effort Estimation: Produces range-based estimates anchored in git history and file scope, stating the assumptions that set the range width. - Use Case: A user asks "first refactor the auth module, then document the API, then review the changes." The Skill decomposes this into three packages, validates a task class for each, and routes them to do-implement, do-document, and do-code-review in sequence. ## Quick Start Ask the assistant to break down and route a multi-part request, for example: "Use /do to plan out fixing the login bug, updating the docs, and reviewing the changes."