planning-code-feature

<skill_overview> Structure and plan new features before implementation to ensure clear scope, deliverable increments, and manageable complexity New feature request needs to be planned User story needs decomposition into tasks Feature spans multiple components or modules Need to clarify scope and acceptance criteria Complex feature requiring incremental delivery </skill_overview> <clarification_strategy> <when_to_ask> Feature scope is vague or too broad Multiple valid interpretations of requirements Need to clarify edge cases and constraints Unclear acceptance criteria or "definition of done" Trade-offs between complexity and delivery time Dependencies on external systems or teams </when_to_ask> <how_to_ask> Use the "question" tool to ask clarifying questions Ask about user value and expected outcomes Focus on concrete behaviors, not abstract features Batch related questions together (max 2-3 at once) </how_to_ask> <good_question> You want a "user notifications" feature. I see two approaches: email-only or email + in-app. Should this include in-app notifications, or email is enough for now? </good_question> <good_question> The feature requires displaying user data. We can show last 10 items (simple) or implement pagination (proper). How many items do users typically have? Should I implement pagination from the start? </good_question> <bad_question> What do you want the feature to do? <why_bad>Too vague, doesn't show any analysis effort</why_bad> </bad_question> </clarification_strategy> <planning_phases> Understand the user value — who benefits and how? Identify core functionality vs nice-to-haves Define what's explicitly OUT of scope List constraints (time, tech, dependencies) Use "question" tool to clarify ambiguous requirements Clear scope statement with in/out boundaries <validation_questions> Can someone walk me through what success looks like? What could go wrong that we haven't talked about? What needs to exist before we can start this work? </validation_questions>