Develop workflows and user stories for a Flintlock CLI client

First stage of https://github.com/weaveworks-liquidmetal/flintlock/issues/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
Who is trying to / would like to
When I run
Then I should see
```

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.

Start by reading the linked issue #601 and the Flintlock CLI context. Identify operator types, goals, difficulties, commands, and expected outcomes, then document small user-story journeys in this thread or a linked Google Doc. Done means the proposed workflows have been reviewed and accepted by the team.

Written by the indexing model from the issue text.