kickofflisted

# Nebu Kickoff Clarify enough to avoid wrong work, then move. One skill for the full pre-execution phase: design exploration, scope clarification, and execution planning. ## Three entry points **Design exploration** (fuzzy/exploratory): 1. Read existing code, docs, plans, and constraints first. 2. Ask one focused question at a time; prefer multiple choice when it fits. 3. Make assumptions explicit, especially around non-goals, scale, security, and ownership. 4. Propose 2-3 viable approaches with a recommendation and clear tradeoffs. 5. Once direction is chosen, stop exploring and move toward execution. **Scope clarification** (ambiguous/behavior-changing): 1. Inspect relevant code, docs, or current behavior first. 2. If task is obvious and local, state the working assumption and start. 3. If ambiguity would change implementation, ask one focused question at a time. 4. Focus on: what outcome matters, what is in/out of scope, what must not change, what proof counts as done. 5. Once path is clear, move into execution without extra approval loops. **Execution planning** (multi-file/phase): 1. State goal in one or two sentences. 2. List files or areas likely to change. 3. Order work chunks by meaningful progress, not micro-steps. 4. Note key risks or open questions. 5. Define validation needed before claiming done. 6. Skip plan for one or two obvious edits. Use short bullets for normal multi-step work. Fuller plan only when sequencing or coordination risk is high. 7. If repo