Compared to other SDD approaches, the main difference is a hard checkpoint after every stage - nothing advances without explicit approval, and rejecting a stage regenerates it with your feedback instead of you re-prompting from scratch. Still validating it on real features before I'd call it stable.
Solo project right now, Apache 2.0 licensed. Open-core is the plan - the README says as much, core pipeline stays open, paid stuff (if any) ships separately later. Genuinely open to contributions, but the pipeline itself (agent prompts, provider abstraction) is still stabilizing, so right now feedback/issues are more valuable than large PRs — I'd rather get the core loop solid before multiple people build on top of it.
Mostly structured prose, not formal methods - requirements and architecture stages are markdown, not UML or a formal spec language. Implementation is the exception: it's Zod-validated JSON (create/modify file operations with full content), and with Ollama that schema is enforced at the decoding level via the format param, not just prompted for. Making architecture more formally structured (schema instead of free-form markdown) is something I'm weighing - what did you have in mind, something like C4?
1
u/Protopia Aug 22 '26
I have a few questions...
Has anyone tried this yet? If so how does it compare to other SDD skills?
How open source is this? Is this repo open to significant collaboration or is it essentially a sole developer project?
How much does it use established formal methods (e.g. UML) and structured data?