Browsed by
Tag: GitHub SpecKit

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

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