gemini-cli-extensions / gemini-cli-extensions/conductor
How to modify the track's spec/plan?
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 295
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
After run the /conductor:newTrack blah blah. The spec.md and plan.md are created. Then I found something is not as what expected or some test cases are missing from the plan. What's the suggested workflow to modify the track's spec/plan in this case?
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 with the /conductor:newTrack entry point and the generated spec.md and plan.md files. Trace the existing track workflow to determine how changes and missing test cases are handled; done means documenting the supported modification workflow clearly.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100