gemini-cli-extensions / gemini-cli-extensions/conductor
Feature request: turn rubber ducky context into track
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 295
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
I've found myself rubber ducking with CLI to come up with a strategy for a feature. Similar to /conductor:newTask, I'd like to have /conductor:captureNewTask (or better name) that can take that and start the process. Today if I ask CLI to "start a new task", Gemini starts trying to make new files without going through the conductor workflow.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing /conductor:newTask command and its CLI entry point; the issue names no files or tests. Define how /conductor:captureNewTask should turn an existing rubber-ducking conversation into the conductor workflow, then verify it no longer starts creating files before that workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100