Skip to content
#

spec-driven-development-requirements

Here are 4 public repositories matching this topic...

Turn vague ideas into developer-ready specs and vertical-slice build plans — one question at a time. A gated, resumable interview that adapts its depth to project complexity. It never invents requirements: unknowns become traceable Open Questions tied directly to affected build slices. Delivered as a Claude Code skill.

  • Updated May 28, 2026

Spec-driven governance for AI coding agents, organized in seven pillars (M.A.N.D.A.T.E.): Markdown as source of truth, Architecture by ADR, Named rules enforced by script, Decision Log, Agents with bounded mandates, Tested before asserted, Executable backlog.

  • Updated Oct 16, 2026
  • Shell

Spec-driven development for codebases written with AI coding agents: a real SRS (ISO 29148, EARS, MADR) in plain Markdown, immutable requirement IDs, a generated traceability matrix, and a stdlib-only checker that fails the build when code and spec disagree. Works with Claude Code, Cursor, Codex, Copilot — or by hand.

  • Updated Nov 7, 2026
  • Shell

Add this topic to your repo

To associate your repository with the spec-driven-development-requirements topic, visit your repo's landing page and select "manage topics."

Learn more