pm-clarify-guardlisted

# PM Clarify Guard Runs after speckit-clarify produces its candidate question list. Filters to business-level only before the client sees anything. ## Why This Exists speckit-clarify may surface technically framed questions (API design, database choice, performance SLAs in engineering units). The client cannot meaningfully answer these — they belong to the developer layer. This guard strips or rephrases them so every question the client sees is answerable without technical knowledge. ## Step 1 — Review Candidate Questions Read the questions speckit-clarify generated. For each, classify: **KEEP — business-level:** - User behaviour and journey ("What does the user do when X fails?") - Business goals and measurable outcomes ("What does success look like in 90 days?") - Scope clarifications ("Does this apply to guest users as well as logged-in users?") - Priority trade-offs ("If we can only ship one of these, which matters most?") - Edge cases in the user experience ("What should happen if the user's session expires mid-flow?") **REMOVE or REPHRASE — technical:** - API design, endpoints, request/response schemas - Database, storage, or infrastructure choices - Framework, library, or technology selection - Performance targets in engineering units (ms, TPS, cache hit rate) - Architecture patterns (microservices, event sourcing, etc.) - Deployment or DevOps specifics **Rephrase rule**: If the question has a legitimate business intent buried in technical framing, extract the