User Story
Before listing features, explain who has the problem, what they need, and why it matters.
The user, reason, and completion conditions are still unknown.
✓ Content remains after refresh
✓ Editing can continue on another device
Name a specific user: Describe the person and situation instead of hiding different needs behind “all users.”
Replace the feature label with a goal: A save button is a solution; continuing an unfinished itinerary later is the result the user needs.
Add checkable conditions separately: Keep the story brief, then put scope, exceptions, and completion conditions in Acceptance Criteria or a Use Case.
You can say this to an AI Agent
Turn “save a trip” into a user story that states the target user, goal, and reason. Use only the facts I provide, and list unsupported user claims or business rules as open questions. Then add directly checkable acceptance criteria without deciding the button position or database structure.
Select page elements for precise AI edits
Click a button, text, or card, note the change, then copy its exact location to AI.
Open Selector Pro website↗