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.
Spec Coding Blog
Paginated browsing for the full Spec Coding article archive. These pages keep long lists readable while preserving direct links.
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.
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.
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.
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.
Payment Workflow Spec: Failure and Retry Matrix
Write payment workflow specs with retryable errors, declined-card handling, timeout behavior, 3DS branches, and dunning states.
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.
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.
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.
Static pagination page · 2/3