OpenSpec, Superpowers, and Spec Kit: SDD Patterns
Compare OpenSpec, Superpowers, and GitHub Spec Kit through the practical SDD patterns they share: specs, plans, tasks, tests, review gates, and evidence.
A focused archive of Foundations articles for spec-first teams.
Compare OpenSpec, Superpowers, and GitHub Spec Kit through the practical SDD patterns they share: specs, plans, tasks, tests, review gates, and evidence.
Same order refund feature built two ways — vibe coding ships fast but drowns in edge-case bugs,…
20 real-world acceptance criteria examples in Given/When/Then format covering authentication, e-commerce, APIs, data processing, payments, and notifications.
How to write a technical specification: a complete template, real-world walkthrough, section-by-section guidance, and a free online generator to draft your own.
A practical guide to building test harness infrastructure for backend API services — from fixtures and mocks to contract tests and CI integration,…
Superpowers is an open-source framework that enforces spec-first discipline on AI coding agents.
Define backward compatibility rules for API specs, including deprecation timelines, migration paths, Sunset headers, and breaking-change review.
Define database schemas before writing migrations, including columns, constraints, indexes, API alignment, and rollout order.
AI coding tools drift without constraints — adding fields, renaming functions, expanding scope.
Govern AI-assisted coding with spec-driven prompts: define scope, boundaries, evidence, and audit trails before generated code reaches review.
Design API specs for LLM-powered agentic clients with discoverable fields, idempotency, dry-runs, semantic descriptions, and safe destructive actions.
See how Spec Skills fits spec-first delivery through constrained prompts, spec injection, boundary enforcement, and reviewable AI output.
Quality gates for AI-assisted code: pre-prompt spec checks, diff review, test evidence, and human sign-off before generated code ships.
Write non-goals that stop scope creep, name deferred work, and give reviewers a clear boundary before implementation starts.
A 30-day adoption plan for Spec-First: choose the first workflow, set a review threshold, and measure whether rework drops.
Turn software requirements into testable specs with observable outputs, failure paths, evidence types, and QA-ready acceptance criteria.
PRD vs Technical Spec: What's the Difference becomes clearer when the team makes the hidden decisions visible before coding starts.
What is spec-first development? A complete guide to surfacing hidden decisions about scope, contracts, edge cases, and acceptance criteria before coding starts.