Drydock is a repeatable method to turn messy specifications into tested working software.
Drydock imports your source material, defines stories using agile best practices, and decomposes your sources into typed blueprints (stories) related using a graph database. Drydock builds with a context aware compression based algorithm and tests stories with deterministic test driven acceptance criteria.
- Builds working software using small, cheap models
- Agile Methodology to decompose buildable stories and for product owner / llm review
- Test driven development with acceptance criteria embedded in each Story/Blueprint
- Dependency graph relates stories and orders builds
- QuarterDeck web console to answer questions and review the process
- Runs on existing subscriptions
- Ingests your existing specs and notes in any format
- Change management — edit the spec, rebuild only what's affected
- Context compression and Grouping for context aware builds
- Enterprise guardrails with embedded branding, best practices, and build gates
- Generates consistent apps and documentation
No API keys — Drydock runs on your existing Claude or Codex subscription.
I am Ed Barlow. 30 years in data engineering and architecture, the last two building software with coding agents. Drydock is the process I needed and could not find.
0.2.0, beta. Install is: uv tool install drydock-sdd
The complete command surface is one table in the README.
www.webcloudstudio.com
What I want feedback on: I need to test on other design paterns - love feedback and will tune for your use case.
4 WORKING applications built as uat - full build evidence
ReadingList - simple web app - https://webcloudstudio.github.io/drydock-example-readinglist...
CommonMark - markdown formatter - https://webcloudstudio.github.io/drydock-example-commonmark/
TOML - markup language - https://webcloudstudio.github.io/drydock-example-toml/
jq - flagship - full build of the jq language - https://webcloudstudio.github.io/drydock-example-jq/
All four built with gpt-5.6-luna on a Codex subscription. No API keys. Feel free to also use haiku.
Drydock is a repeatable method to turn messy specifications into tested working software.
Drydock imports your source material, defines stories using agile best practices, and decomposes your sources into typed blueprints (stories) related using a graph database. Drydock builds with a context aware compression based algorithm and tests stories with deterministic test driven acceptance criteria.
- Builds working software using small, cheap models
- Agile Methodology to decompose buildable stories and for product owner / llm review
- Test driven development with acceptance criteria embedded in each Story/Blueprint
- Dependency graph relates stories and orders builds
- QuarterDeck web console to answer questions and review the process
- Runs on existing subscriptions
- Ingests your existing specs and notes in any format
- Change management — edit the spec, rebuild only what's affected
- Context compression and Grouping for context aware builds
- Enterprise guardrails with embedded branding, best practices, and build gates
- Generates consistent apps and documentation
No API keys — Drydock runs on your existing Claude or Codex subscription.
I am Ed Barlow. 30 years in data engineering and architecture, the last two building software with coding agents. Drydock is the process I needed and could not find.
0.2.0, beta. Install is: uv tool install drydock-sdd
The complete command surface is one table in the README.
www.webcloudstudio.com
What I want feedback on: I need to test on other design paterns - love feedback and will tune for your use case.