Sessions
Give Uno a useful task
A clear goal makes the result easier to trust and review.
Tell Uno what should change, why it matters, and how you will judge the result.
Include four things
- Outcome: the behavior you want, with an example.
- Context: the repository, relevant files, issue, or reproduction steps.
- Constraints: interfaces, dependencies, or design choices to preserve.
- Verification: tests, acceptance criteria, and the desired delivery artifact.
The checkout page loses the discount when a customer changes quantity.
Reproduce it with a discounted item, then change quantity from 1 to 2.
Fix the total calculation without changing the checkout API.
Add a regression test for the discount and quantity interaction.
Run the checkout tests and open a pull request with the evidence.Keep the first task bounded
A small bug, a missing test, or a single feature is a useful starting point. Split independent outcomes into separate sessions. For larger changes, ask Uno to investigate and propose a plan before implementing.
Answer questions where the work happens
When Uno needs a decision, reply in the session. New guidance should name what changes and what remains required. Review the final output against your original acceptance criteria.
For tracked delivery, use Tasks (Alpha). For an outcome that needs agreement first, create a specification.