gemini-cli-extensions / gemini-cli-extensions/conductor
Feature request: Extend conductor to create plan modes for different phases in the conductor track
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 295
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
Hi,
What?
I think conductor is an excellent way of codifying intent och overall planning. In our team we often jointly create conductor tracks together. This creates the right kind of overall engineering discussions that needs human planning.
What would be excellent is to be able to create more detailed plans, call it "implementation details", using plan mode for conductor and that these are archieved together with the track upon completion.
Why?
It is excellent to have these in the future and as part of both human and agent context. As they can be archived in a logical format it would be easy in the future for an agent to retrieve previous experiences and implementations too.
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
No files, tests, or entry points are named. Start by reviewing how conductor tracks are created and archived, then determine how plan modes for different conductor phases should be represented and stored. Done means implementation details can be created for phases and archived with the completed track.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100