The project describe command is currently interactive only, which is great for guided use.
However, for scripting and automation (e.g., in CI or when piping from another command), it would be very powerful to provide the prompt text directly via a command-line flag.
Proposed Solution:
Add a --prompt (or -p) flag to the contextvibes project describe command.
- If the flag is used, its value is taken as the prompt.
- If the flag is omitted, the command should fall back to the current interactive behavior.
This would enable workflows like:
contextvibes project describe --prompt "My detailed task description..."
Context
- CLI Version:
dev
- OS/Arch:
linux/amd64
- Filed by: @duizendstra
The
project describecommand is currently interactive only, which is great for guided use.However, for scripting and automation (e.g., in CI or when piping from another command), it would be very powerful to provide the prompt text directly via a command-line flag.
Proposed Solution:
Add a
--prompt(or-p) flag to thecontextvibes project describecommand.This would enable workflows like:
contextvibes project describe --prompt "My detailed task description..."Context
devlinux/amd64