plannotator-setup-goal

# Setup Goal Turn an idea into a goal package at `goals/<slug>/` through structured discovery, user interview, and codebase exploration. ## Phases ### 1. Rearticulate State back what the user wants in your own words. If the conversation already has rich context, summarize it. If the goal is bare or vague, do minimal shallow exploration of the codebase to ground your understanding. Keep it to 2-3 sentences. Wait for the user to confirm or correct before continuing. ### 2. Interview (grill me) Interview the user such that you can derive every "fact" this goal should produce, & until you reach a complete shared understanding of the desired outcomes. The following question areas should help you determine facts about the outcome. - What the feature/change is - Who it's for - What problem it solves - What behavior changes - What success looks like - What's in and out of scope (The most important area to determine facts) - What edge cases to consider - What constraints or precedent apply Ask questions **one at a time**, waiting for feedback before continuing. For each question, provide your recommended answer. Use the question/answer tool if available. **If a question can be answered by exploring the codebase, explore the codebase instead of asking.** Stop when you feel confident in being able to describe the facts of the goal outcome. Don't pad. ### 3. Fact Sheet A fact is a simple description of each outcome of a goal. It should be easily testable and verifiable. A fac...