Acceptance Criteria QA Can Test

Turn a rough feature idea into acceptance criteria a QA can run without asking what we meant. FEATURE Name: [NAME] User and job: [WHO AND WHAT] Rough idea: [PASTE] Platforms: [WEB | IOS | ANDROID] Permissions and plans: [WHO CAN USE IT] Out of scope: [LIST] WRITE 1) A user story in one sentence, only if it helps. The criteria matter more. 2) Happy path, numbered, with the exact outcome on screen or in the API. 3) Edge cases: empty, too long, double submit, lost network, no permission, wrong plan, and one domain-specific case from the idea. 4) For each criterion: pass looks like, fail looks like. 5) Analytics or audit events if the feature changes money, access, or data: [EVENTS OR "none"]. 6) What we are not testing in this slice. Use "the user can" only when it is observable. "Feels fast" is not a criterion unless I gave a number.