<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
  xmlns:atom="http://www.w3.org/2005/Atom"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Spec Coding Blog</title>
    <link>https://spec-coding.dev/blog/</link>
    <description>Practical guides, templates, and checklists for spec-first software delivery. Written by Daniel Marsh.</description>
    <language>en</language>
    <lastBuildDate>Fri, 29 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://spec-coding.dev/feed.xml" rel="self" type="application/rss+xml" />
    <image>
      <url>https://spec-coding.dev/og.png</url>
      <title>Spec Coding Blog</title>
      <link>https://spec-coding.dev/blog/</link>
    </image>

    <item>
      <title>OpenSpec vs Superpowers vs Spec Kit: SDD Patterns</title>
      <link>https://spec-coding.dev/blog/spec-driven-development-tools-openspec-spec-kit-superpowers</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/spec-driven-development-tools-openspec-spec-kit-superpowers</guid>
      <pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-29</dc:date>
      <category>Foundations</category><category>Ai</category><category>Process</category><category>Resource</category>
      <description>Compare OpenSpec vs Superpowers vs GitHub Spec Kit through practical SDD patterns: specs, plans, tasks, tests, review gates, and evidence.</description>
    </item>

    <item>
      <title>Harness Engineering vs Spec-Driven Development</title>
      <link>https://spec-coding.dev/blog/building-a-test-harness-for-api-services</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/building-a-test-harness-for-api-services</guid>
      <pubDate>Thu, 02 Apr 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-29</dc:date>
      <category>Process</category><category>Foundations</category><category>Api</category>
      <description>Compare harness engineering vs spec-driven development, then build an API test harness with fixtures, mocks, contract tests, and CI evidence.</description>
    </item>

    <item>
      <title>Acceptance Criteria Examples You Can Copy</title>
      <link>https://spec-coding.dev/blog/acceptance-criteria-examples-guide</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/acceptance-criteria-examples-guide</guid>
      <pubDate>Wed, 08 Apr 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-11</dc:date>
      <category>Foundations</category>
      <description>20 real-world acceptance criteria examples in Given/When/Then format covering authentication, e-commerce, APIs, data processing, payments, and notifications.</description>
    </item>

    <item>
      <title>Technical Spec Template, Examples, and Generator</title>
      <link>https://spec-coding.dev/blog/how-to-write-technical-spec-template-guide</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/how-to-write-technical-spec-template-guide</guid>
      <pubDate>Wed, 08 Apr 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-11</dc:date>
      <category>Foundations</category>
      <description>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.</description>
    </item>

    <item>
      <title>Backward Compatibility Specs and Deprecation Paths</title>
      <link>https://spec-coding.dev/blog/backward-compatibility-specs-deprecation-paths</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/backward-compatibility-specs-deprecation-paths</guid>
      <pubDate>Fri, 27 Mar 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-11</dc:date>
      <category>Foundations</category>
      <description>Define backward compatibility rules for API specs, including deprecation timelines, migration paths, Sunset headers, and breaking-change review.</description>
    </item>

    <item>
      <title>Database Schema Specs Before Migrations</title>
      <link>https://spec-coding.dev/blog/spec-database-schemas-before-writing-migrations</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/spec-database-schemas-before-writing-migrations</guid>
      <pubDate>Sun, 22 Mar 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-11</dc:date>
      <category>Foundations</category>
      <description>Define database schemas before writing migrations, including columns, constraints, indexes, API alignment, and rollout order.</description>
    </item>

    <item>
      <title>AI Coding Prompts That Follow Specs</title>
      <link>https://spec-coding.dev/blog/ai-prompts-that-follow-your-spec</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/ai-prompts-that-follow-your-spec</guid>
      <pubDate>Tue, 17 Mar 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-11</dc:date>
      <category>Foundations</category>
      <description>AI coding tools drift without constraints, adding fields, renaming functions, expanding scope, and inventing tests. Spec-first prompts keep changes reviewable.</description>
    </item>

    <item>
      <title>AI Coding Risk Register Before Merge</title>
      <link>https://spec-coding.dev/blog/ai-coding-risk-register-before-merge</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/ai-coding-risk-register-before-merge</guid>
      <pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-11</dc:date>
      <category>Process</category><category>Resource</category>
      <description>Use a pre-merge risk register for AI-generated code: flag auth, data, contract, migration, rollback, and observability risks.</description>
    </item>

    <item>
      <title>API Change Management for AI-Generated Clients</title>
      <link>https://spec-coding.dev/blog/api-change-management-for-ai-generated-clients</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/api-change-management-for-ai-generated-clients</guid>
      <pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-11</dc:date>
      <category>Api</category><category>Process</category>
      <description>Manage API changes for AI-generated clients with structured changelogs, announcement channels, compatibility rules, and CI gates.</description>
    </item>

    <item>
      <title>API Error Taxonomy for AI-Assisted Integrations</title>
      <link>https://spec-coding.dev/blog/api-error-taxonomy-for-ai-assisted-integrations</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/api-error-taxonomy-for-ai-assisted-integrations</guid>
      <pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-11</dc:date>
      <category>Api</category><category>Writing</category>
      <description>Design API error taxonomies AI-generated clients can use, with stable codes, retry categories, and machine-readable details.</description>
    </item>

    <item>
      <title>Designing API Specs for Agentic Clients</title>
      <link>https://spec-coding.dev/blog/designing-api-specs-for-agentic-clients</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/designing-api-specs-for-agentic-clients</guid>
      <pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-11</dc:date>
      <category>Api</category><category>Foundations</category>
      <description>Design API specs for LLM-powered agentic clients with discoverable fields, idempotency, dry-runs, semantic descriptions, and safe destructive actions.</description>
    </item>

    <item>
      <title>Spec Skills Case Study: From Ticket to Spec</title>
      <link>https://spec-coding.dev/blog/spec-skills-case-study-ticket-to-spec</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/spec-skills-case-study-ticket-to-spec</guid>
      <pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-11</dc:date>
      <category>Case Study</category><category>Writing</category>
      <description>Follow a vague support ticket as it becomes a shippable technical spec using Spec Skills, guided questions, and review-ready output.</description>
    </item>

    <item>
      <title>Spec Skills and Spec-First Delivery</title>
      <link>https://spec-coding.dev/blog/spec-skills-first-overview</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/spec-skills-first-overview</guid>
      <pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-11</dc:date>
      <category>Foundations</category><category>Process</category>
      <description>See how Spec Skills fits spec-first delivery through constrained prompts, spec injection, boundary enforcement, and reviewable AI output.</description>
    </item>

    <item>
      <title>Real-Time Collaboration Spec: Conflict Resolution</title>
      <link>https://spec-coding.dev/blog/real-time-collaboration-spec-conflict-resolution</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/real-time-collaboration-spec-conflict-resolution</guid>
      <pubDate>Mon, 09 Mar 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-11</dc:date>
      <category>Case Study</category><category>Api</category>
      <description>How to spec real-time collaboration: OT vs CRDT, presence protocol, offline edits, conflict resolution, and the operational transform vs three-way-merge decision.</description>
    </item>

    <item>
      <title>Contract Testing Plan: From OpenAPI to CI</title>
      <link>https://spec-coding.dev/blog/contract-testing-plan-from-openapi-to-ci</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/contract-testing-plan-from-openapi-to-ci</guid>
      <pubDate>Sun, 01 Mar 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-11</dc:date>
      <category>Api</category><category>Process</category>
      <description>Add contract testing from OpenAPI to CI with generated tests, provider checks, consumer expectations, and reliable fixtures.</description>
    </item>

    <item>
      <title>Data Sync Between Services: Spec Guide</title>
      <link>https://spec-coding.dev/blog/data-sync-spec-between-services</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/data-sync-spec-between-services</guid>
      <pubDate>Sun, 01 Mar 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-11</dc:date>
      <category>Api</category><category>Case Study</category>
      <description>Specify cross-service data sync with ordering guarantees, conflict handling, backfill plans, and event-driven or pull-based tradeoffs.</description>
    </item>

    <item>
      <title>Designing Idempotent Workflows with Specs</title>
      <link>https://spec-coding.dev/blog/designing-idempotent-workflows-with-specs</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/designing-idempotent-workflows-with-specs</guid>
      <pubDate>Sun, 01 Mar 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-11</dc:date>
      <category>Api</category><category>Writing</category>
      <description>How to specify idempotency keys, deduplication windows, and state-machine transitions so retries and partial failures don't double-charge or corrupt data.</description>
    </item>

    <item>
      <title>Event-Driven Systems: Specification Patterns</title>
      <link>https://spec-coding.dev/blog/event-driven-systems-specification-patterns</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/event-driven-systems-specification-patterns</guid>
      <pubDate>Sun, 01 Mar 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-11</dc:date>
      <category>Api</category><category>Process</category>
      <description>Specification patterns for event-driven systems: schema versioning, command vs fact events, orchestration choices, idempotent handlers, and replay safety.</description>
    </item>

    <item>
      <title>Mobile API Spec Considerations for Offline Mode</title>
      <link>https://spec-coding.dev/blog/mobile-api-spec-for-offline-mode</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/mobile-api-spec-for-offline-mode</guid>
      <pubDate>Sun, 01 Mar 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-11</dc:date>
      <category>Api</category><category>Case Study</category>
      <description>Spec a mobile API for offline mode with local-first writes, sync windows, conflict handling, outbox behavior, and rejection recovery.</description>
    </item>

    <item>
      <title>Payment Workflow Spec: Failure and Retry Matrix</title>
      <link>https://spec-coding.dev/blog/payment-workflow-spec-failure-and-retry-matrix</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/payment-workflow-spec-failure-and-retry-matrix</guid>
      <pubDate>Sun, 01 Mar 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-11</dc:date>
      <category>Case Study</category><category>Api</category>
      <description>Write payment workflow specs with retryable errors, declined-card handling, timeout behavior, 3DS branches, and dunning states.</description>
    </item>

    <item>
      <title>Rollout and Rollback Design for High-Risk Releases</title>
      <link>https://spec-coding.dev/blog/rollout-and-rollback-design-for-high-risk-releases</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/rollout-and-rollback-design-for-high-risk-releases</guid>
      <pubDate>Sun, 01 Mar 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-11</dc:date>
      <category>Process</category><category>Writing</category>
      <description>Design high-risk releases with stop-loss metrics, rollout windows, rollback types, ownership, monitoring, and evidence that teams can use under pressure.</description>
    </item>

    <item>
      <title>Writing Edge Cases That QA Can Actually Test</title>
      <link>https://spec-coding.dev/blog/writing-edge-cases-that-qa-can-test</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/writing-edge-cases-that-qa-can-test</guid>
      <pubDate>Sun, 01 Mar 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-11</dc:date>
      <category>Writing</category><category>Process</category>
      <description>Write edge cases QA can execute with concrete inputs, starting states, expected outputs, failure paths, and examples that turn vague risks into tests.</description>
    </item>

    <item>
      <title>10 Common Mistakes in Software Specifications</title>
      <link>https://spec-coding.dev/blog/common-mistakes-in-software-specifications</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/common-mistakes-in-software-specifications</guid>
      <pubDate>Wed, 25 Feb 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-11</dc:date>
      <category>Writing</category><category>Process</category>
      <description>Avoid ten specification mistakes that hide decisions, blur acceptance criteria, skip failure paths, and push scope arguments into implementation.</description>
    </item>

    <item>
      <title>Spec Review Checklist Before Coding</title>
      <link>https://spec-coding.dev/blog/spec-review-checklist-before-coding</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/spec-review-checklist-before-coding</guid>
      <pubDate>Wed, 25 Feb 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-11</dc:date>
      <category>Process</category><category>Writing</category>
      <description>Use this pre-coding review checklist to separate blockers from preferences, record accepted risks, and attach test evidence before implementation begins.</description>
    </item>

    <item>
      <title>What Is Spec-First Development? (Complete Guide)</title>
      <link>https://spec-coding.dev/blog/what-is-spec-first-development-complete-guide</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/what-is-spec-first-development-complete-guide</guid>
      <pubDate>Wed, 25 Feb 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-11</dc:date>
      <category>Foundations</category><category>Process</category>
      <description>What is spec-first development? A complete guide to surfacing hidden decisions about scope, contracts, edge cases, and acceptance criteria before coding starts.</description>
    </item>

    <item>
      <title>AI Coding Spec Packet Before Code Generation</title>
      <link>https://spec-coding.dev/blog/ai-coding-spec-packet-before-code-generation</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/ai-coding-spec-packet-before-code-generation</guid>
      <pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-06</dc:date>
      <category>Ai</category><category>Writing</category><category>Process</category><category>Resource</category>
      <description>A copy-ready packet for giving AI coding tools a bounded task, acceptance criteria, file ownership, tests, and review evidence before code generation starts.</description>
    </item>

    <item>
      <title>Refund Example: Vibe vs Spec Coding</title>
      <link>https://spec-coding.dev/blog/same-refund-feature-vibe-coding-vs-spec-coding</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/same-refund-feature-vibe-coding-vs-spec-coding</guid>
      <pubDate>Sat, 11 Apr 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-06</dc:date>
      <category>Foundations</category>
      <description>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.</description>
    </item>

    <item>
      <title>Superpowers for Spec-First AI Coding</title>
      <link>https://spec-coding.dev/blog/superpowers-spec-first-ai-agent-skills</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/superpowers-spec-first-ai-agent-skills</guid>
      <pubDate>Thu, 02 Apr 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-06</dc:date>
      <category>Foundations</category>
      <description>Superpowers enforces spec-first discipline for AI coding agents through brainstorming, specs, plans, TDD, verification, and repeatable review evidence.</description>
    </item>

    <item>
      <title>AI Coding Governance with Spec-Driven Prompts</title>
      <link>https://spec-coding.dev/blog/ai-coding-governance-with-spec-driven-prompts</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/ai-coding-governance-with-spec-driven-prompts</guid>
      <pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-06</dc:date>
      <category>Process</category><category>Foundations</category>
      <description>Govern AI-assisted coding with spec-driven prompts: define scope, boundaries, evidence, and audit trails before generated code reaches review.</description>
    </item>

    <item>
      <title>AI Coding PR Review with Acceptance Criteria</title>
      <link>https://spec-coding.dev/blog/ai-coding-pr-review-with-acceptance-criteria</link>
      <guid isPermaLink="true">https://spec-coding.dev/blog/ai-coding-pr-review-with-acceptance-criteria</guid>
      <pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate>
      <dc:creator>Daniel Marsh</dc:creator>
      <dc:date>2026-05-06</dc:date>
      <category>Writing</category><category>Process</category>
      <description>Review AI-generated pull requests against acceptance criteria: inspect the diff, run evidence checks, and catch failures a quick skim misses.</description>
    </item>
  </channel>
</rss>
