Develop workflows and user stories for a Flintlock CLI client

[Callisto13]

First stage of #601

The expected outcome of this ticket is a set of workflows and user stories outlining how a user would run a flintlock client. You can write these either as comments on this thread, or in a linked googledoc.

Framing:

• What kind of operator(s) will be using a flintlock cli?
• What is each operator trying to achieve?
• What have they found difficult to do so far? What have they been unable to do?

For each operator, formulate a set of user stories which walk through: how they came to be here; what action they would like to take; what outcome they expect to see.
Eg:

As a <type of operator>
Who is trying to / would like to <do a thing>
When I run <command or commands>
Then I should see <expected outcome>

The aim is to write as many small broken down "snapshot" journeys for each operator as possible, so we can formulate a complete picture of how we would like the tool to behave.

This ticket is closed once the proposed workflows/stories have been reviewed and accepted by the team as a starting point (we anticipate that things may change as we learn more).

We will use these stories to formulate a sensible and intuitive language for the cli.

[github-actions]

This issue is stale because it has been open 60 days with no activity.

[github-actions]

This issue was closed because it has been stalled for 365 days with no activity.