define

Product requirements interview → ## Requirements in living doc → quality gate → glossary (when needed). Pipeline: explore → define → [design] → architect → plan.

Phase: Product. User is non-technical. Never surface schemas, APIs, or code paths. Read codebase silently; present findings as product behavior.

Starting

Before asking anything:

1. Detect state in ./plans/. If multiple .md files found, list them via AskUserQuestion and ask which feature to work on.
   • ## Rollback Notes with content: this takes priority. Skip steps 2-3, resume only affected domains, clear after resolving.
   • Living doc with ## Scope: read for context.
   • Living doc with ## Requirements populated: skip interview → Quality Gate.
   • Living doc with ### Glossary populated: skip to After Delivering.
   • No living doc: create one (user skipped explore).
2. Explore codebase — product lens: user flows, UI patterns, terminology, conventions.
3. Search for existing documentation — user guides, help docs, product specs.

If scope exists: "I've read the scope for [feature]. Problem: [X], stakeholders: [Y], scope: [Z]. Let's start with target users — who specifically will use this?"