Browsed by
Tag: GitHub SpecKit

GitHub SpecKit is an open source toolkit for spec-driven development with AI coding agents. Learn the specify, plan and implement workflow and how to apply it to real projects.

Spec-Driven Azure Infrastructure Before You Start Coding
Spec-Driven Azure Infrastructure Before You Start Coding

Spec-Driven Azure Infrastructure Before You Start Coding

Comments 0 Comment

What if you could describe your Azure environment in plain words and get it deployed – secure, cost-controlled, and repeatable? That is spec-driven Azure infrastructure. And you don’t need to be a cloud architect to try it. I restarted my Expenses Manager in June with one ambition: rebuild it without click ops. No portal wizards, no manual setup. That is why I use spec-driven development and rely on GitHub Copilot to assist me. In one of my previous posts, I…

Read More Read More

Never Pay for the Same Dataverse Mistake Twice
Never Pay for the Same Dataverse Mistake Twice

Never Pay for the Same Dataverse Mistake Twice

GitHub Copilot showed me something new: GPT-5.6 Sol, plus a 30% discount. Yes, and I couldn’t resist trying it on a Dataverse task. Why not see the new model in action, right? As a result, that decision burned nearly a month’s budget before the task was even done. But here’s the thing: the expensive part isn’t the story worth telling. What came out of it was a GitHub Copilot custom skill – a reusable file that captures everything the agent…

Read More Read More

One Task Table to Rule Them All
One Task Table to Rule Them All

One Task Table to Rule Them All

The backlog from my last post had one line I couldn’t ignore: status transitions weren’t implemented yet. Tables, views, the model-driven app – all done. The missing piece was the Dataverse Agent Task contract itself. In other words, the part that lets Power Platform and Azure talk to each other. That wasn’t a bug. It was a missing seam. Without an explicit contract, two teams can’t build independently. They can’t test independently either. Remember my post about project decomposition? I…

Read More Read More

My Son Built an App with No IT Background
My Son Built an App with No IT Background

My Son Built an App with No IT Background

“Dad, can we build an app with AI?” That question started a spec-driven development experiment I’ll never forget. He was seventeen. No coding background, no CS classes. Just frustration with the school carpool situation: thirty parents in a WhatsApp thread, nobody knowing who was driving, every morning a small disaster. I said yes. But on one condition: we use GitHub 🌱 SpecKit. He looked puzzled. Fair enough. So I explained: it’s a framework for Spec-Driven Development. Describe the problem the…

Read More Read More

GitHub Copilot Dataverse: MCP Limits, YAML, and PAC CLI

GitHub Copilot Dataverse: MCP Limits, YAML, and PAC CLI

My spec was done. The plan too. Time to build the Dataverse foundation: the piece everything in my Expense Management system would run on. I connected the Dataverse MCP server in VS Code, opened my prepared spec, and ran /speckit.implement in GitHub Copilot. The GitHub 🌱 SpecKit workflow with Copilot to implement my Dataverse solution felt ready. I expected it to just work. It didn’t. The MCP hit its limits fast. Cryptic errors, wrong solution placement, no model-driven app support….

Read More Read More

Spec-Driven Development: Project Decomposition
Spec-Driven Development: Project Decomposition

Spec-Driven Development: Project Decomposition

The Dataverse-first restart was done. However, my spec looked sharper. The data model had a center of gravity, and that part actually worked. Solving one problem, however, revealed another. One spec was still covering six very different concerns: different timelines, different risk profiles, and different people who would eventually build and own each piece. Nothing defined where one concern ended and another began. That’s not a spec problem. Instead, it’s a structure problem. In my previous post, I said the…

Read More Read More