yeah, that is exactly what i do to create in the repo. i will try to create simple github actions that will do publishing to gdocs, linear and pulling comments from those systems back(and maybe even slack). an obviously it should work with other systems too like JIRA and confluence. but i think implementation shouldn’t be hard part and anyone can do custom one quickly
I'm currently at the stage where my agentic dev loop is running and feedback is flowing, but I haven't reached true autonomy yet. I still have to control things with manual workarounds constantly. That's exactly why I'm curious about others' experiences.
The most interesting challenge to me is the transition path in practice: how do you get from the messy reality to that clean ideal picture when a team is already mid-project with their own ingrained habits and tooling preferences?
The most interesting challenge to me is the transition path in practice: how do you get from the messy reality to that clean ideal picture when a team is already mid-project with their own ingrained habits and tooling preferences?
-
so what tools team uses now? than the answer can be more concrete
I'm in a similar spot and very curious about the transition path, not just the end state.
We have several projects and different teams. In one of the more “advanced” ones we already run on a fairly standard enterprise stack: Jira for work tracking, Confluence for docs, and a dedicated repo for SDD/technical specs. That’s also the place where I’m closest to getting something that feels like real autonomy: the agentic dev loop is running and integrated into the existing tools, but there are still plenty of manual guardrails and workarounds.
My question is less about wiring up specific tools and more about the change‑management / rollout side. In practice this is a digital transformation: it’s not enough to define the target “agent‑first SDLC”, you also need a sane path to get there from a messy reality with ingrained habits and existing tooling.
Have you seen any concrete adoption patterns or approaches that worked well for teams already mid‑project?
Any actual evidence of it being better? Because publicly available evidence points to the contrary, where it repeatedly fails to complete the most basic of tasks.
