Topic: Spec Writing

A focused archive of Spec Writing articles for spec-first teams.

No-JS fallback page ยท 10 articles

Browse by topic (no-JS fallback)

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.

Read article

Spec Skills Case Study: From Ticket to Spec

Follow a vague support ticket as it becomes a shippable technical spec using Spec Skills, guided questions, and review-ready output.

Read article

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.

Read article

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.

Read article

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.

Read article

Rollout and Rollback Design for High-Risk Releases

Design high-risk releases with stop-loss metrics, rollout windows, rollback types, ownership, monitoring, and evidence that teams can use under pressure.

Read article

Writing Edge Cases That QA Can Actually Test

Write edge cases QA can execute with concrete inputs, starting states, expected outputs, failure paths, and examples that turn vague risks into tests.

Read article

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.

Read article

How to Write Testable Software Specifications

Turn software requirements into testable specs with observable outputs, failure paths, evidence types, and QA-ready acceptance criteria.

Read article

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.

Read article