I decided to give project Squad (https://lnkd.in/e2EwMEVi) by Brady Gaster a try, together with the GitHub Copilot CLI and GitHub Boards, and the results were impressive. Using this setup, Squad created and actively managed a GitHub Project board, updating it, as worked progressed through project issues. Here's what that looked like in practice 👇 ✅ Squad initialized a team of specialized agents based on my project requirements ✅ Squad created and managed a GitHub project board ✅ Work was broken down into GitHub issues, routed to specific "team members" based on skillset ✅ Each agent picked up issues, opened PRs, ran tests, fixed failures, and moved work forward ✅ Everything flowed exactly like a modern, disciplined dev team would All of this happened inside this repo: 🔗 https://lnkd.in/eNKf7jeh A .NET Aspire application built incrementally through issues, PRs, and CI driven by Squad and executed via the GitHub Copilot CLI. What would normally take days of focused engineering work was completed under 2 hours, with structure, traceability and quality gates. It feels like an early glimpse of how software teams will scale in the near future, not by replacing developers, but by amplifying how development work flows through a team. #Squad #CopilotCLI #GitHubCopilot #DotNet #Aspire #AutonomousAgents
I've used this wonderful little feature a bunch. It makes things a LOT cleaner to be able to watch the Squad get things done for you. Note - you need to login using the -s project switch for this to work!
This is fascinating Jorge. Can't wait to demo this to some of my customers... appreciate you sharing!
Thanks for sharing Jorge Balderas! It popped up timely in my feed - I was about to refactor my homegrown multi-role “simulated scrum team” workflow in Claude Code! Will give this a shot!
Thanks for posting. How close to prod-ready was the end result?