sdd-run

Automated test-first implementation executes your specification by branching, writing code against acceptance criteria, and verifying results through declared mechanisms like unit or integration tests. It coordinates the entire workflow automatically to ensure verifiable definition of done.

Spec-driven development enforces a strict workflow where the definition of done relies on verifiable criteria rather than subjective feeling. It ensures every acceptance criterion is verified through declared automated mechanisms such as unit tests, integration tests, or automated probes.

Generating a pull request with regression testing evidence is accomplished by automatically implementing the specification, verifying all acceptance criteria via automated probes, and attaching the validation evidence directly to the PR for policy compliance.

Adversarial code validation is available through an optional Ultracode mode that employs multi-agent orchestration to actively attempt to refute verified criteria. This ensures the highest level of code integrity beyond standard automated verification.

Spec-driven development works directly with feature specifications located in your .sdd/specs/ directory. It requires strict adherence to defined contracts and applies automated regression testing to verify your code against those declared policies.

Deterministic TDD should be avoided when your development workflow lacks strict specifications or defined acceptance criteria. Without verifiable contracts or automated probes to validate against, the enforced spec-driven workflow cannot establish a reliable definition of done.