Proposal: Use GitHub Projects to track who’s working on what

[theepicsaxguy]

I’d like to propose that we start using GitHub Projects to track active work and who’s assigned, so we avoid duplicating effort and make it clearer where things are heading.

Context/motivation:

• The project is still early-stage; folks are picking up tasks ad hoc.
• I already see overlap risks (e.g., multiple people exploring UI/agent features, auth, STT, etc.).

What I’m suggesting:

• Stand up a GitHub Project for this repo.
• Add a lightweight workflow: when someone starts on an issue/feature, add an item to the Project and assign yourself.
• Keep a few columns (Backlog → In Progress → In Review → Done) and surface owners/status.
• Optionally track higher-level themes (e.g., UI polish, auth, STT, cost/usage analytics, agent skills) so newcomers can see direction at a glance.

Why?:

• Reduces duplicate work and context collisions.
• Gives contributors visibility into active efforts and priorities.
• Makes it easier for maintainers to coordinate and for new folks to onboard.

Thanks!

[oneishaansharma]

Sounds like the way to go. What do you think @chriswritescode-dev ?
@namanrajpal had a similar post about getting a roadmap going.
would be helpful imo

[chriswritescode-dev]

sounds good to me I added the project and the issues so should be good to access now. Let me know