What problem does it solve? When a user describes a new feature in plain conversation, it is easy to jump straight into code without scoping or design, producing bloated or misaligned implementations. This Skill watches the user's latest message, detects feature-shaped work that plausibly exceeds ~75 lines of code, and recommends the right entry point into the feature development chain before any code is written. ## Core Features & Use Cases - Scope estimation: Silently estimates the implementation size of the request and skips dispatch for small fixes, renames, doc edits, or explicitly throwaway work. - Entry-point recommendation: Chooses between /feature-storm for vague, product-level requirements and /feature-design for clear requirements needing technical design. - Single-question routing: Presents one AskUserQuestion with the recommended skill, the alternative, and a continue-without-dispatch option, then hands over via the Skill tool. - Use Case: A user writes "Add reminders to the todo app." The Skill detects non-trivial feature work, recommends /feature-storm, and on acceptance invokes it with the original request. ## Quick Start Describe a new feature you want to build in a normal message, and the dispatcher will offer to route you into the right feature planning skill.