Write clear, testable acceptance criteria for user stories and feature delivery; use when defining done conditions, creating measurable requirements, applying INVEST checks, documenting negative scenarios, and aligning product, engineering, and QA on expected outcomes.
Does it follow best practices?
Evaluation — 91%
↑ 1.17xAgent success when using this tile
Validation for skill structure
Your team is developing a B2B SaaS platform for inventory management, and the current user onboarding process is causing significant customer churn. New users sign up but abandon the platform within the first week because they can't figure out how to set up their inventory systems effectively.
The customer success team reports that users get overwhelmed by the initial setup process - they need to configure their product catalog, set up warehouse locations, define user roles, and integrate with their existing systems. Currently, there's no guided flow, and users are dropped into a complex dashboard with no clear next steps.
The business team wants to reduce time-to-value from 2 weeks to 3 days, and increase activation rates from 35% to 65%. They've identified a step-by-step onboarding flow as the key to achieving these metrics.
The product team needs to design an onboarding experience that guides new users through essential setup tasks while being flexible enough to accommodate different business types and sizes.
Create comprehensive acceptance criteria for the user onboarding workflow. Your document should include:
Save your work as onboarding-workflow-criteria.md.
The following files are provided as context. Extract them before beginning.
=============== FILE: inputs/onboarding-research.md ===============