Feature
I Wrote 238 Specs and Never Read One Again
I ran spec-driven development for real and ended up with 238 spec files I never reopened. Neither did my AI. Here is what fixed it.
ReadBlog · Active topic
Spec-driven-development
13 field notes filtered by Spec-driven-development.
Latest edition
sdd
Build Log 4: Your Pipeline, as Nodes
SpecKit Companion's pipeline is now a list of nodes, not hardcoded steps. Three confusing toggles collapse into one picker, and the workflow finishes itself.
Read
sdd
Build Log 3: Turbo Mode and the Fast Path
Giving spec-kit a leaner, faster shape without forking it: turbo mode, a fast-path that skips plan/tasks on small changes, and why it all shipped opt-in.
Read
sdd
Build Log 2: Capturing the Whole Lifecycle, and Shipping v1
Build Log 2: full lifecycle capture, a derive-from-files fallback, and an eval that caught my state engine lying. Where the SpecKit Companion ships v1.
Read
sdd
Build Log 1: Proving the Riskiest Assumption
Proving the riskiest assumption in my SDD rebuild: a spec-kit hook auto-fires, writes the state file, and the Companion GUI lights up. Plus the install gotcha.
ReadArchive
8 entriesLayered Context FoundationsddSpecs That Move In Next to Your CodesddBuild Log 0: Kickoff, Rebuilding SDD in PublicsddWhat is SDD (and Why I Built It)sddBuild Your Own SDD Workflowspec-driven-developmentCustom Workflows in SpecKit Companionspeckit-companionSpecKit Companionspeckit-companionSpec-Driven Development: Stop Vibe Codingspec-driven-development