Drydock established

Core approach

Process-first: reuse the Agile and Test-Driven Development practices teams have relied on for years to deliver reproducible results and maintain working software. Delivery is driven from a drydock CLI that plans a Manifest and Blueprints, validates each Blueprint's Typed Specification, and builds the target software alongside a built-in web console.

Workflow

1. drydock init — initialize a target workspace
2. drydock import — copy your specifications into the workspace
3. drydock analyze — decompose imported sources into stories, blockers, and acceptance milestones
4. drydock plan — create the Manifest and Blueprints
5. drydock validate — validate a Blueprint's Typed Specification
6. drydock build — build or inspect build state
7. drydock refit — update Blueprint and target software together
8. drydock score — evaluate acceptance and release readiness
9. drydock document / drydock publish — generate project documentation and render Markdown into publishable HTML

Supported tools

• Claude
• Codex

Notes

Drydock is a specification-driven software delivery methodology from Ed Barlow / Web Cloud Studio that combines Agile and Test-Driven Development. Work is organized around Blueprints with Typed Specifications and a Manifest, driven from a drydock CLI and accompanied by a web console for Commander-to-LLM interaction. The approach is documented in the preprint Improving Step Accuracy in Specification-Driven Development (Edward Barlow, 2026). It currently targets Claude and Codex and had its initial release in July 2026, so it is one to watch as adopters put its process claims to the test.

Added Jul 18, 2026 · Assessment last reviewed Jul 18, 2026 · How we track