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.
Topic: Process
A focused archive of Process articles for spec-first teams.
AI Coding Spec Packet Before Code Generation
A copy-ready packet for giving AI coding tools a bounded task, acceptance criteria, file ownership, tests, and review evidence before code generation starts.
AI Coding Governance with Spec-Driven Prompts
Govern AI-assisted coding with spec-driven prompts: define scope, boundaries, evidence, and audit trails before generated code reaches review.
AI Coding PR Review with Acceptance Criteria
Review AI-generated pull requests against acceptance criteria: inspect the diff, run evidence checks, and catch failures a quick skim misses.
AI Coding Risk Register Before Merge
Use a pre-merge risk register for AI-generated code: flag auth, data, contract, migration, rollback, and observability risks.
AI Coding with Test-Evidence Gates
Use test-evidence gates for AI-generated code: require meaningful tests before merge and catch hallucinated implementations before release.
API Change Management for AI-Generated Clients
Manage API changes for AI-generated clients with structured changelogs, announcement channels, compatibility rules, and CI gates.
API Schema Diff Review Before Release
How to run an API schema diff review before every release: what diff tools catch, what they miss, and the human checks that still matter for OpenAPI and GraphQL.
Spec Skills and Spec-First Delivery
See how Spec Skills fits spec-first delivery through constrained prompts, spec injection, boundary enforcement, and reviewable AI output.
Quality Gates for AI-Assisted Development Specs
Quality gates for AI-assisted code: pre-prompt spec checks, diff review, test evidence, and human sign-off before generated code ships.
Contract Testing Plan: From OpenAPI to CI
Add contract testing from OpenAPI to CI with generated tests, provider checks, consumer expectations, and reliable fixtures.
Event-Driven Systems: Specification Patterns
Specification patterns for event-driven systems: schema versioning, command vs fact events, orchestration choices, idempotent handlers, and replay safety.
Rollout and Rollback Design for High-Risk Releases
Design high-risk releases with stop-loss metrics, rollout windows, rollback types, and owners who can pause expansion.
Writing Edge Cases That QA Can Actually Test
Write edge cases QA can execute with concrete inputs, starting states, expected outputs, and release-blocking priority.
10 Common Mistakes in Software Specifications
Avoid ten specification mistakes that hide decisions, blur acceptance criteria, skip failure paths, and push scope arguments into implementation.
How to Adopt Spec-First in a Team (30-Day Plan)
A 30-day adoption plan for Spec-First: choose the first workflow, set a review threshold, and measure whether rework drops.
PRD vs Technical Spec: What's the Difference?
PRD vs Technical Spec: What's the Difference becomes clearer when the team makes the hidden decisions visible before coding starts.
Spec Review Checklist Before Coding
Use this pre-coding review checklist to separate blockers from preferences, record accepted risks, and attach test evidence before implementation begins.
What Is Spec-First Development? (Complete Guide)
What is spec-first development? A complete guide to surfacing hidden decisions about scope, contracts, edge cases, and acceptance criteria before coding starts.