gemini-cli-extensions / gemini-cli-extensions/conductor
Enhancing Determinism and Context Alignment in conductor:newTrack
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 295
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
I am using conductor:newTrack to generate spec.md and plan.md. However, I have encountered two main challenges regarding the quality and consistency of the generated output:
1、Alignment with Existing Docs: I need the agent to strictly follow provided reference materials, such as API specifications (Swagger/OpenAPI), business logic definitions, and Database schemas (DDL). Currently, the generated spec.md sometimes deviates from these source-of-truth documents.
2、Output Variance (Stability): With the same input prompt and reference files, the generated spec.md and plan.md vary significantly across different runs. This lack of idempotency makes it difficult to maintain a stable development track.
Current Environment
gemini-cli: 0.33.1
conductor: 0.4.1
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
The issue identifies conductor:newTrack as the entry point and describes generated spec.md and plan.md as the outputs. Review how this entry point uses the referenced API specifications, business logic definitions, and database schemas; done means the outputs consistently follow those sources and remain stable across repeated runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100