sdd-kit

The problem

AI agents write code fast, but without a process: they forget the project at every session, open huge pull requests, decide things that belonged to the owner and, when CI goes red, sometimes fix it by switching the test off.

The community's SDD tools handle the specification well. What is left to the person is the delivery: turning the spec into reviewable tickets, keeping CI green and closing the version.

The solution

The kit brings a professional team's way of delivering to any repository:

• A skill that teaches the agent the whole process: evidence-based analysis, specs with acceptance criteria, an epic per phase, one ticket per branch and per pull request, review, CHANGELOG and tag.
• An adoption script, in sh and PowerShell, that copies the template without overwriting anything: CLAUDE.md, issue and PR templates, specs and ready-made CI for Go, Node/TypeScript, Java, Python, Rust and C#/.NET, with minimum test coverage.
• An event engine on GitHub Actions that does the mechanical steps without AI: it updates the checkpoint on every merge, summarizes red CI, brings main into the PRs, opens the closing PR and triggers the release.
• Resume checkpoints: a session can end at any moment, and the next one picks up where the last one stopped.
• axyn, a Go CLI that brings the same process to free or local models, moving on only when the quality gates pass.

How quality is enforced

The kit is developed with its own process, and every pull request goes through 12 checks:

• Markdown and shell lint, tests of the scripts, and workflow verification (actionlint).
• Adoption tested on Linux, macOS and Windows.
• Every language template adopted into a minimal project, with the generated make ci actually running.
• Traceability: every acceptance criterion is cited in a test; a rule fails CI if one is left out.
• Each release's version is computed from the commits, with Go Release Manager.

Technical decisions

• Explicit stopping points: decisions, review, merge and tag belong to the owner, unless delegated.
• Tests are sovereign: red CI is fixed at the root cause, never by loosening or skipping a test.
• Scripts in POSIX sh and PowerShell, so they run the same on Linux, macOS and Windows.
• Adoption never overwrites the project's files, and a weekly sync keeps adopted repositories up to date.

Outcome

The kit grew out of cv-craft, which went from prototype to v1.x with this process: 10 specs and 71 acceptance criteria, all with an automated test. Today it drives Go Release Manager and sdd-kit-demo, a project built from scratch with an epic, tickets, pull requests and a release, as well as the kit itself. The same method, with specs and sovereign tests, guides this site.

Limits

The kit depends on GitHub and on an agent (Claude Code, or opencode through axyn). So far it is used on my own projects; validation by other teams is missing. The process does not replace the person: decisions and review still belong to the owner.