What problem does it solve? Turning an approved solution into a realistic delivery plan is hard: teams skip task decomposition, hand out round-number estimates, and commit dates without consulting the people doing the work. This Skill enforces a disciplined estimation workflow so the plan you give the business is honest and defensible. ## Core Features & Use Cases - Structured Task Breakdown: Splits work by interface, handler, and business logic, then sequences tasks and identifies the critical path. - Disciplined Estimation: Applies a four-step estimation process, complexity multipliers, confidence levels, and a no-estimate rule for volatile or unclear requirements. - Business-Ready Timeline: Produces a phased timeline plus explicit assumptions, blockers, and external dependencies, ending at a human commit gate. - Use Case: Given a wallet top-up feature with a chosen architecture, produce a plan listing tasks (API contract 1d, provider integration 3d on the critical path, ledger write 1d, tests 2d), a total of ~8 man-days at medium confidence, and a two-phase rollout for the business. ## Quick Start Ask the agent to break the approved feature design into tasks, estimate the work, and identify the critical path for the delivery timeline.
