GitHub just unlocked a new level of developer workflow. Den Delimarsky walks through how GitHub Spec Kit now integrates with the brand-new Copilot CLI. Here is what stands out: ➡️ Switch between multimodal models like Cloud Sonnet 4 and GPD5 for different behaviors. ➡️ Run custom slash commands directly in the CLI to guide Copilot. ➡️ Follow a repeatable workflow: constitution, specify, clarify, plan, tasks, analyze, and implement. This walkthrough is more than a tutorial. It is a glimpse into how developers will collaborate with AI agents to rapidly build, test, and ship projects. 👉 Watch Den's full breakdown and see the live demo here: https://lnkd.in/gAgvBb9v #GitHub #Copilot #DeveloperTools #AI #Workflows
Great introduction to copilot CLI and Speckit for those that are not familiar with both yet. As a software architect, I love the direction we are moving with LLMs in software development (design-first approach)😍
Yeah, I'm on the fence on the Speckit. For me it's moving then problem of code generation to document generation. Not sure if it's easier to generate good documentation vs good code. That said I'm looking into the GitHub CLI soon!
Technical Solutions Architect specializing in AI/ML, cloud-native innovations, and automation, with a proven track record of delivering scalable solutions, optimizing operations, and driving technological advancements
4wPowerful shift here. What excites me isn’t just the CLI integration,it’s the move toward agentic workflows where developers orchestrate AI models like teammates. Switching between models for different behaviors, guiding them with slash commands, and following a constitution-driven workflow feels like the early blueprint for how software engineering will evolve in the next 3–5 years. Curious to see how this compares against emerging AI-native IDEs—GitHub may have just staked a big claim in the agentic developer future.