plan-feature

# Plan Feature Two-phase pre-implementation planning: clarify requirements via interview, then compile a complete PRD. ## Phase 1: Discovery Help clarify requirements and scope through structured questioning. ### Interview Framework The interview is a fog-of-war walk across four quadrants of the unknown. Open by listing the **known knowns** (what the user has already decided), then work the questions below to surface **known unknowns** (open questions they're aware of), **unknown knowns** (constraints they hold but haven't said — the questions in 2–4 exist to shake these loose), and close by hunting **unknown unknowns** ("what would surprise us mid-build? what reference implementation should we read first?"). A discovery that ends with all four quadrants visited produces a PRD that doesn't get re-planned in week two. ### Goal Quality Bar (gate before interviewing) Before opening the interview questions below, try to state the goal in one line that answers five things: - What's true when this is done? - What evidence shows it — a command, a test, a metric, a reviewed artifact? - What threshold counts as success — pass/fail, or a number? - What's explicitly out of scope, where that would matter? - What's the stop condition — the point where you ask the user instead of guessing? If a clean one-liner falls out, skip straight to Phase 2's clarifying questions — the interview below exists for when it doesn't. Reject pure activity goals — "make progress," "keep investigati...