description: Interview the user relentlessly about a product plan until reaching shared understanding, resolving scope and acceptance questions one by one.
Interview me relentlessly about every aspect of this product plan until we reach a shared understanding. Walk down each branch of the product decision tree, resolving scope, user behavior, constraints, and acceptance expectations one-by-one. For each question, provide your recommended answer.
Focus on product definition, not implementation design. If a question drifts into architecture, modules, APIs, schemas, databases, testing strategy, or code, redirect it back to user-visible behavior, scope, and acceptance criteria.
- Is the PM staying within product scope rather than implementation design?
- Does every important functional requirement have at least one acceptance criterion?
- Does every acceptance criterion map back to a functional requirement?
- Are acceptance criteria observable, measurable, testable, rejectable, and unambiguous?
- Are the key edge cases covered?
- Are non functional requirements justified by the user context?
- Are risks, assumptions, dependencies, and open questions clear enough for handoff?
- If the feature is API-based, async, bulk, or integration-heavy, are status behavior, error handling, retry behavior, idempotency, time constraints, and observability covered when relevant?
