Browsed by
Tag: SpecKit

An open-source GitHub tool (github/spec-kit) that implements spec-driven development through a set of AI slash commands: /speckit.constitution, /speckit.specify, /speckit.clarify, /speckit.plan, /speckit.tasks, /speckit.analyze, and /speckit.implement. Works with any AI coding agent to produce stable, reviewable output.

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

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

Comments 0 Comment

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: When the Spec Is Too Big
Spec-Driven Development: When the Spec Is Too Big

Spec-Driven Development: When the Spec Is Too Big

I had a spec, I had GitHub Copilot Pro+! A new billing period with fresh credits has begun. So I started to refurbish my Expense Management system. In detail, I was building with a fresh spec that should rebuild the whole system in one run. And yes, that was the problem. Everything looked good. Copilot credits were melting away during implementation. Some hours later I had my first results. The Azure portal showed me what was there. Content Understanding analyzers:…

Read More Read More

Spec-Driven Development: The Methodology Behind the Magic
Spec-Driven Development: The Methodology Behind the Magic

Spec-Driven Development: The Methodology Behind the Magic

Most developers I know have been here. They type a detailed prompt into their AI agent. The output looks right. They run it, tweak a detail, run it again – and somewhere around the third attempt, the whole thing has quietly shifted into something else. The problem is not the AI. The problem is the approach. Spec-driven development changes that. Before a single file gets created, you define intent. You build a shared understanding for your business stakeholders, your architect,…

Read More Read More

Stop Coding. Start Building from Specs.
Stop Coding. Start Building from Specs.

Stop Coding. Start Building from Specs.

I haven’t written a line of code since January. Not because I couldn’t. I stopped because spec-driven development showed me I was spending time on the wrong part of the job. Today, it is easy to type “build me XYZ” and get code in seconds. I did that too. Sometimes the result looked great. Then I ran the same prompt again and got something different. Logic shifted. Edge cases disappeared. The output stopped being predictable. The turning point came when…

Read More Read More