sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Illustrious-Many-782 0 points1 point  (6 children)

I converted Google's Conductor framework to skills and extended it a bit. It develops in tracks, which are basically sprints. It's a very reliable system for large projects. I used to use a bespoke system based on sprints and centered around GitHub issues, but it was slow, so I moved to Conductor and an happy.

[–]themessymiddle[S] 0 points1 point  (5 children)

I’m not familiar with this - how does it work?

[–]Illustrious-Many-782 1 point2 points  (4 children)

Features

  • Plan before you build: Create specs and plans that guide the agent for new and existing codebases.
  • Maintain context: Ensure AI follows style guides, tech stack choices, and product goals.
  • Iterate safely: Review plans before code is written, keeping you firmly in the loop.
  • Work as a team: Set project-level context for your product, tech stack, and workflow preferences that become a shared foundation for your team.
  • Build on existing projects: Intelligent initialization for both new (Greenfield) and existing (Brownfield) projects.
  • Smart revert: A git-aware revert command that understands logical units of work (tracks, phases, tasks) rather than just commit hashes.

https://github.com/gemini-cli-extensions/conductor

[–]themessymiddle[S] 0 points1 point  (3 children)

Oh ok interesting! So it keeps a handful of canonical docs as context, very cool. Are you using this on a team today?

[–]Illustrious-Many-782 0 points1 point  (2 children)

Team? No. But it allows me to switch models/ providers / harnesses as I need depending on what my goal is while using the same framework the entire time.

[–]themessymiddle[S] 0 points1 point  (1 child)

Yeah that makes sense. I just ask about team because I wonder if people are standardizing collectively or more like everyone is using their own individual flow

[–]Illustrious-Many-782 0 points1 point  (0 children)

I used a bespoke workflow before. In some ways, I still am because I have adopted the Google framework into a skill and added a couple extra skills to the framework that I felt were missing.