Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

newTrack writes spec.md, plan.md, metadata.json and index.md to conductor folder

Open
#159 2 comments 11 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
cli

Research direction

Start by locating the newTrack command and the code that creates the conductor/tracks/ folder. Reproduce the issue with a new track and trace where spec.md, plan.md, metadata.json, and index.md are written. Done means all four files are created only in the track folder and the conductor/index.md file is left unchanged.

Written by the indexing model from the issue text.

Description

For some reason newTrack has started writing spec and plan files to the incorrect location. Instead of writing to the conductor/tracks/ folder, :newTrack writes spec.md, plan.md, metadata.json and index.md to conductor folder. This also overwrites the index.md file in the conductor folder. It then detects the issue, and needs to restore index.md from git, and try again. It now does this consistently on every newTrack I add

Dominant language
Python
Stars
3.7k
Forks
297
Avg merge
9m
Merged PRs (30d)
1

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from gemini-cli-extensions/conductor

All issues in gemini-cli-extensions/conductor

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.