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.
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.
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.
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.
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.
SDD loads four layers of context automatically: principles, living specs, feature deltas, and ADRs, so your specs stop dying the moment a PR merges.
How I made SDD adoptable on a real, existing codebase: specs that live next to your code, and /sdd:init that drafts them from the code you already have.
I'm folding my SDD tool into spec-kit and rebuilding it in public as the SpecKit Companion. Here's the plan, the 8-step backlog, and how to follow along.
What SDD is, why I built it, and how it differs from spec-kit. The origin story behind folding it back into spec-kit as the SpecKit Companion.