Home

spec-podcast-site

Welcome to the spec-podcast-site wiki.

This repository is a hands-on lab for Spec-Driven Development (SDD) using GitHub's Spec Kit. The deliverable is a sleek static podcast website for a fictional show called Signal & Static, built as a Next.js static export with embedded mock episode data.

The point of the project is not the podcast site itself. The point is the workflow: starting from intent, turning that intent into a constitution and a specification, and only then planning, decomposing, and implementing. Design decisions are made explicit and committed to source control before the app code is written.

What you will find here

Page	What it covers
Getting Started	Install Spec Kit, initialize the project, run the site locally
Spec-Driven Development	The SDD loop as practiced in this repo, command by command
Why Spec-Driven Development	The motivation and the problems SDD is designed to solve
Methodology Comparison	Classic DevOps (ADO Epics to Stories) vs SDD vs the HVE-core RPI flow
Architecture	The Next.js static export, content model, and project layout
Project Constitution	The non-negotiable rules that govern every change
Testing and Validation	Type-check, lint, build, accessibility, and end-to-end checks

The fictional product in one line

Signal & Static is a podcast about modern technology, culture, and creative work. The site has a landing page with one featured episode, an episodes page with exactly 20 mocked episodes, an about page, and an FAQ page.

How this site was actually built

Every artifact in specs/001-modern-podcast-site/ was produced through the SDD loop, and the application was implemented from the generated tasks.md. The validation suite (TypeScript, ESLint, static build, Playwright responsive checks, and axe accessibility checks) is part of the workflow, not an afterthought.

See Spec-Driven Development to follow the same path, or jump straight to the Methodology Comparison to see how SDD relates to classic Azure DevOps planning and the HVE-core RPI flow.