r/SpecDrivenDevelopment • u/No_Article_5669 • 40m ago
TeDDy: a coding harness for iterative, incremental development
r/SpecDrivenDevelopment • u/No_Article_5669 • 40m ago
r/SpecDrivenDevelopment • u/ditomax • 5h ago
Getting a first version running with Claude Code is quick. The trouble starts months later, when something has to change and nobody, the agent included, knows what the code was meant to do.
build is one answer to that: a free, open-source skillset (MIT). Concept documents are the specification and the code is derived from them. My test is whether a second agent could rebuild the product from the documents alone.
You type "start", then "next", "redo" or "stop". A director skill runs four stage skills:
A human decides at three gates: requirements, consistency findings, and a gap analysis before release.
Also built in: STPA-light (losses, hazards, constraints, each traced to a requirement and a test) and secret protection before the first line of code (hook, gitleaks pre-commit).
Plain markdown, nothing to install. Open the folder in Claude Code, Codex or Cowork and type "start", or symlink skills/build* into ~/.claude/skills/. Customer-specific rules go into a profile/ folder instead of a fork.
Repo: https://github.com/ditomax/build
Actually tested on two projects, medical app and a skill for fault detection in electrical installations in factories.
For those maintaining agent-written code longer than a few weeks: where does drift show up first for you? Does spec-first hold up, or does it just move the problem into the docs?