NOT BUILT YETsoon
A course, once there is one worth sitting through
The plan is a course on applying spec-driven development with Spec Kit: taking real work from a vague idea to a spec, a plan, tasks and shipped code. It has not been made, so the honest answer to when is that we do not know.
Nothing is recorded and there is no date. What follows is the outline it would run, so you know what you would be joining a list for.
WAITLIST
Get told when it lands
An address here gets exactly one message, on the day the course opens. There is no newsletter behind it.
THE OUTLINE
Four parts, from an empty workspace to a spec that outlives the ticket
This is the shape, not a schedule. Every lesson below covers something the product does today. The last one, the Workflow Builder, is in beta.
Set up
- Install both halvesWhat the VS Code extension gives you, and what the Spec Kit extension adds on top.
- Pick your AI providerTwelve of them, and what changes when yours cannot submit the prompt for you.
- Read the sidebarYour specs, the status of each one, and the steering docs underneath.
Your first spec
- Create a specChoosing a workflow, and giving it the images and context it needs.
- The spec viewerThe documents, the step rail, and where you are in the run.
- Run a step, then review itComment on the line you disagree with, and send the notes back with Refine.
- Read the OverviewIntent, decisions, coverage, and the run log folded underneath.
Make it yours
- Add your own actionsCustom commands, and where they show up in the viewer footer.
- Attach work around a stepA companion.yml hook: a shell command, an instruction, or a node file of your own.
- Write your own workflowYour phases, your commands, your output files, offered by Create Spec.
Going further
- Living specsTurning them on, adopting a capability, and keeping it central or beside the code.
- Drift and coverageWhat each report tells you, and why neither one can ever block a build.
- The Workflow BuilderIn beta. Change what a step does on a board, then build.
THE WRITTEN VERSION
Five guides cover the same ground today
Read in this order they walk from an empty workspace to a finished run you can hand to someone else.
- Getting startedInstall both halves, create your first spec, run it, and read the record it leaves behind.
- Pick a pipelineChoose stock SpecKit or SpecKit Companion, then bend either one into a workflow of your own.
- Review and refineComment on a spec line by line, keep the comments in the repo, and hand the pending ones to your AI.
- Anatomy of the OverviewHow to read the record a finished run leaves behind, and what it will not tell you.
- Living specsOne durable spec per capability, kept next to the code, updated by the runs that change it.