Discussion: Could the "Status" field from the :status command be more useful?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
Start by reading the implementation of /conductor:status and :newTrack to understand how the current Status field and track setup work. Resolve whether target dates, progress-based estimates, or omission of the field is intended, then define completion around a concrete status behavior and its validation.
Written by the indexing model from the issue text.
Description
When you run /conductor:status, you almost always see something like this:
✦ Project Status Overview
Date: Tuesday, January 6, 2026
Status: On Track
---
I've only ever seen the "Status:" be "On Track", which makes sense - I would assume something is off track if the rate of development isn't tracking towards a deadline, and there's currently no concept of deadlines/ETAs/Target Dates in Conductor.
It might be nice in :newTrack to ask if the user wants to put a target date. Then Conductor could extrapolate - based on the steps in the plan and the rate of development, is the track going to be completed on time? If the user doesn't set one, we could omit the Status field from the :status output, or consider other ways to make it more useful.
Another idea is to invert the relationship. Based on the progress so far, could Conductor guestimate when the track would finish? ex:
Status: In active development.
Estimate: < 2 hours of work remaining
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 297
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from gemini-cli-extensions/conductor
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gemini-cli-extensions/conductor#176 · 3 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
gemini-cli-extensions/conductor#72 · 1 reaction ·
-
how to: conductor plugin for development of micro-services where each service is in its own repoOpen
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
gemini-cli-extensions/conductor#168 · 4 comments ·
All issues in gemini-cli-extensions/conductor
Similar issues
-
namespace operations
Difficulty 1/5 Under an hour Newbie friendliness 82/100
EclipseFdn/open-vsx.org#13573 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
collective/icalendar#1854 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
rancher/rancher-ai-agent#412 ·
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
TUDelftGeodesy/DePSI#134 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HenriquesLab/rxiv-maker#335 ·