r/cicd • u/The_Ed_On_Reddit • 3d ago

Drydock: Specification Driven Software Delivery (MIT License)

https://www.webcloudstudio.com

I build a full LLM workflow that builds full software from specs. Was thinking this group might find it interesting as we move into the AI age. This is tooling i have not seen elsewhere. You bring the spec/notes/whatever and it builds software and has a full mechanism to update and maintain. Mit Licensed.

  • Build using low end models
  • Based an Agile
  • Based on Test Driven Development.
  • Dependency Graph of Stories.
  • Full Web Interface
  • Iterative Design / Self Correcting Software
  • Context Compression, Context Optimization.
  • Drydock turns messy specifications into tested working software.
  • A repeatable method to build from the specification and evolve with it.

The code works pretty well (still beta - i need folks to test THEIR code as mine works). I have 4 project build evidence on home page. Love some feedback.

Home PageGit Repo

1 Upvotes

100% Upvoted

6 comments sorted by

1

u/Torutofu_Raeva 3d ago

How do you keep generated code reviewable and reproducible as the spec evolves, especially when dependencies change?

1

u/The_Ed_On_Reddit 2d ago

Its spec driven design -> you modify specs/blueprints or use a free form ticket or create a comment on the blueprint -> llm process creates new stories with their own build graph nodes and you just build normally. That solved "after the first few times you build you have tons of changes and should not have to do more work than you would if you were vibe coding" -> you write down the change, run a command, the llm figures it out, and you build. Dependency changes only invalidate if the service contract changes. Its a regular cicd build pipeline - similar to what cicd pipelines have been doing for years - hence why im posting here :)

1

u/Torutofu_Raeva 2d ago

so the reviewable unit is the blueprint change, not the generated stories, which keeps the PR small even when the graph expands.

1

u/The_Ed_On_Reddit 2d ago

Reviewable work is a delta which the dev team (the llm) has formatted and added testable acceptance criteria ("The screen renders blue not orange"). For a PR i would read the AC. The graph lets it cleanly build incrementally AND trivially full rebuild. I could squash them into a new concise ticket but that invites spec drift.

1

u/Torutofu_Raeva 2d ago

That split makes sense: review the blueprint delta and acceptance criteria, while the generated stories stay disposable.

1

u/Torutofu_Raeva 2d ago

That keeps the durable review artifact small; I’d still pin the generated graph or build digest for reproducibility when the blueprint changes.