nw-dor-validationlisted

# DoR Validation and Antipattern Detection ## Definition of Ready Checklist (8 Items - Hard Gate) All items must PASS with evidence. Each FAIL blocks handoff. ### Item 1: Problem Statement Clear and Validated Domain language (not technical), describes real user pain, testable. Pass: "Maria wastes 30 seconds typing credentials on every visit" Fail: "Users need authentication" | "Implement login feature" ### Item 2: User/Persona with Specific Characteristics Real name, specific role, clear context. Pass: "Maria Santos, returning customer (2+ orders), using trusted MacBook" Fail: "User" | "Customer" | "End user" | "Authenticated user" ### Item 3: At Least 3 Domain Examples with Real Data Min 3 examples, real names (not user123), real values, different scenarios (happy/edge/error). Pass: "Example 1: Maria on MacBook, 5 days since login, goes to dashboard" Fail: "User logs in successfully" | "Test with valid credentials" ### Item 4: UAT Scenarios Cover Happy Path + Edge Cases Given/When/Then format, 3-7 scenarios, real data, covers happy + edge. Pass: "Given Maria authenticated on 'MacBook-Home' 5 days ago..." Fail: "Test login works" | "Given a user When they login Then success" ### Item 5: Acceptance Criteria Derived from UAT Checkable (checkbox), traceable to UAT, outcome-focused (not implementation). Pass: "Sessions older than 30 days require re-authentication" Fail: "Use JWT tokens" | "System should work correctly" ### Item 6: Story Right-Sized (1-3 Days, 3-7 Scenario