Spec‑Driven Development: From Contracts to Code with GitHub Spec Kit (on‑demand)

Modern engineering teams are moving from “code‑first” to spec‑driven workflows to ship services faster with fewer breaking changes. In this session, we walk through how to use GitHub Spec Kit and OpenAPI‑based contracts to design APIs up front, generate SDKs and tests, and wire everything into CI/CD so releases are predictable and compliant. You’ll see practical patterns for enforcing contract changes in pull requests, auto‑generating client libraries, and validating behaviour in pipelines—so your teams can spend less time fixing regressions and more time delivering value.

What you will learn

• How to design clear API contracts (e.g., OpenAPI) and make them the source of truth for services and clients.     
• Using GitHub Spec Kit to scaffold SDKs, stubs, and tests from a single spec, with repeatable CI/CD automation.
• Pull request and governance patterns that gate changes, surface diffs, and prevent accidental breaking changes before they ship.
• End‑to‑end verification with contract tests in CI, plus smoke and compatibility checks across versions.
• Release hygiene at scale: versioning, changelogs, and how spec‑driven workflows improve developer experience and reliability.
  
  

Who this is for

This session is designed for developers, tech leads, and platform/API owners who:

• Build or maintain REST/graph‑style APIs and client SDKs.
• Use GitHub, Azure DevOps, or both, and want cleaner, safer releases.
• Need a practical path to governance, observability, and quality without slowing teams down.