Structure user stories for RFCs/Versions

[lubianat]

• User stories transformations #84 does a great job in capturing user stories for transformations

We could think of ways to structuring user stories for other RFCs/versions in a way that we can:

• Share clearly the uses that are enabled by a particular feature/version
• Track/check uses covered and uses still missing
• Collect new stories

It could be GitHub issues (one for each RFC? version?), image.sc posts, a documentation page...

[lubianat]

There is also:

• Metadata: User stories for named channels #173

[lubianat]

We could associate User Stories with status, e.g.:

no coverage | planned (RFC) | possible (spec)