GitHub Spec Kit tutorial with Copilot and .NET 10

Johan Smarius walks through GitHub Spec Kit using a single-player ping-pong game. He presents the open source toolkit as a way to document product requirements before asking a coding assistant to implement them. The version shown is 0.8, which he describes as a preview rather than a production release. Setup requires Python and the Specify CLI; he initializes the project on a Mac with GitHub Copilot.

The workflow starts with a constitution that records project principles, then moves through specification, planning, tasks and implementation. Smarius stresses that these stages repeat as requirements change. The generated Markdown includes user stories, acceptance criteria and documented assumptions. He recommends the optional clarify and analyze commands: clarification asks about gaps, while analysis catches a score-entry requirement that the demo's tasks did not fully cover.

For implementation, he requests .NET 10 Blazor with WebAssembly rendering, browser local storage and a clean architecture. He reports roughly 40 minutes for code generation and about an hour and a half for the overall process, but notes remaining game-logic problems. Much of the demonstration uses accelerated recordings.

He also shows how to derive specifications from an existing codebase and discusses customization through presets and extensions.