Open
Description
The problem you're addressing (if any)
This task should be done first to set an example as to how the features should be divided. Both too specifically as well as too broadly extracted features can have a diminishing result on the scope definition process. While the list produced here isn't unchangeable (e.g. new features can be added in the future, when new tests are developed), for the purpose of this issue it should be treated as such. The expected number of features is up to discussion.
Describe the solution you'd like
Deliverable: a list of features (as a comment in this issue?) that will be used in second task.
Where is the value to a user, and who might that user be?
No response
Describe alternatives you've considered
No response
Additional context
No response