Harness Engineering vs Spec-Driven Development
What harness engineering means for AI coding agents, how it differs from spec-driven development, and how to run both.
Topic: Foundations
A focused archive of Foundations articles for spec-first teams.
AGENTS.md for Spec-First Teams: What Belongs In It
AGENTS.md is a README for coding agents. The hard part is the boundary: which rules are true for every change, and which belong in a spec for one change.
Cursor Rules: The Four Types and When Each Fires
A Cursor rule that never fires is worse than no rule. Three frontmatter fields decide which of the four types you wrote, and most teams write the dead one.
Spec-First Workflow for AI Agent Teams
A five-stage spec-first workflow for teams running AI coding agents: spec packets, bounded tasks, write scopes, evidence gates, and PR review that scales.
OpenSpec vs Superpowers vs Spec Kit: Compare and Combine
OpenSpec vs Superpowers vs Spec Kit, checked Sep 2026: what each one owns, how to combine them, and which to start with.
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.
Refund Example: Vibe vs Spec Coding
Same refund feature built two ways: vibe coding ships fast but misses edge cases, while spec coding defines scope, acceptance criteria, tests, and rollout proof.
Acceptance Criteria Examples You Can Copy
20 real-world acceptance criteria examples in Given/When/Then format covering authentication, e-commerce, APIs, data processing, payments, and notifications.
Technical Spec Template, Examples, and Generator
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.
Superpowers for Spec-First AI Coding
Superpowers enforces spec-first discipline for AI coding agents through brainstorming, specs, plans, TDD, verification, and repeatable review evidence.
Database Schema Specs Before Migrations
Define database schemas before writing migrations, including columns, constraints, indexes, API alignment, and rollout order.
AI Coding Prompts That Follow Specs
AI coding tools drift without constraints, adding fields, renaming functions, expanding scope, and inventing tests. Spec-first prompts keep changes reviewable.
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.
Designing API Specs for Agentic Clients
Design API specs for LLM-powered agentic clients with discoverable fields, idempotency, dry-runs, semantic descriptions, and safe destructive actions.
How to Scope Non-Goals in Technical Specs
Write non-goals that stop scope creep, name deferred work, and give reviewers a clear boundary before implementation starts.
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.
How to Write Testable Software Specifications
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?
PRD vs Technical Spec: What's the Difference becomes clearer when the team makes the hidden decisions visible before coding starts.
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.
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.