Download and Read
Three resources for readers who want to go deeper than the mini-site summary: the two briefs and the learning bundle.
SDD Practitioner Brief
For engineering leadership. Opens with the AI Productivity Paradox, then walks the architecture: two spec types (Feature Specs describe what to change; Anchor Specs describe how the system is), the pipeline and its gates, opposed review by design, and the proof discipline underneath every approval. Closes with the evidence from use. Edition 2, describing methodology v4.0.5.
Get the Practitioner BriefSDD Partner Brief
For CEOs and PE partners.
The capital-side read on Spec-Driven Development: why AI spend is not showing up in release cadence, and how that gap reads to a sponsor looking at a portfolio company’s engineering organisation.
Get the Partner BriefSDD Learning Bundle
The kit itself, at v0.1.9: the five SDD pipeline agent prompts and the full agent roster, the governance documents (Solo Operator Model, escalation rules, tier-selection guidelines, the two-architect gate, proof discipline), the gate checklists, the spec, anchor, escape and learning-event templates, and the hooks, skills and commands layers. For engineering leaders who want to run SDD on their own team.
Request the Learning BundleRequest the Learning Bundle
The two briefs above download directly. The bundle is the kit itself, and we ask who is taking it — the methodology is open source under AGPL-3.0, so this is not a restriction on use. We want to know which teams are running it.
Apply This to a Portfolio Company.
The brief and the bundle are how engineering leaders evaluate SDD before adopting it. In a portfolio engagement, Geekbyte sits with the CTO through the adoption window — past evaluation, into the team. If you’re considering SDD for a portfolio company, the conversation is the place to start.
Discuss a Growth Advisory Engagement