Define user stories

[kjappelbaum]

For both the documentation and the further development of the framework, it would be great to define "user stories".

Some users I could think of:

1. Someone who wants to benchmark a new agentic scaffold
2. Someone who wants to benchmark a new basemodel
3. Someone who wants to "vibe code" an agent for their task
4. Someone who wants to code a working production-level agent for their task

Probably, there are more potential users.
We should identify them and then decide which ones we target/prioritize. The docs could then also direct them to specific examples/how to for their use-case