We want to iterate on the CLI in order to support a vaster amount of use-cases. The expectation is that this will be a full rewrite of the current implementation, we need not really care about backwards compatibility, but will need a documented migration path.
We want to initially build a very lean CLI and put it out to market in order to get initial feedback about different use cases that our customers might have. The list below includes some initial must-have features that is as lean as possible.
Other than specific functions of the CLI, we want to take care to make sure that the CLI is very ergonomic for developers to use. Key factors include:
- Authentication
- Distribution (installation and portability)
- LLM friendliness (e.g. LLM context in help output)
The expected outcomes of this spike should be a technical specification document (RFC).
Optional outcomes could be:
- a PoC (with real functionality, or mocked)
- a README detailing the installation instructions and functionality of the new CLI
We want to iterate on the CLI in order to support a vaster amount of use-cases. The expectation is that this will be a full rewrite of the current implementation, we need not really care about backwards compatibility, but will need a documented migration path.
We want to initially build a very lean CLI and put it out to market in order to get initial feedback about different use cases that our customers might have. The list below includes some initial must-have features that is as lean as possible.
Other than specific functions of the CLI, we want to take care to make sure that the CLI is very ergonomic for developers to use. Key factors include:
The expected outcomes of this spike should be a technical specification document (RFC).
Optional outcomes could be: