Vibe Coding and Spec Driven Design Ignore **Agile**

• AGILE represents 25 years of software best practices.
• Current alternatives threw away process.
• Without process you can't reproduce your builds.
• Working software you can't reproduce isn't working software.

A Best Practice Process Exists.

Drydock is Agile applied to AI SDD delivery. You are the Commander - the Product owner - and the LLM is your Agile Best Practices Team .

SAIL - Governed, Blueprint-driven Delivery.

SAIL is an agile process for software delivery

• **Setup** your system and import your notes or LLM-created specifications.
• **Agile/Analyze** decomposes into stories/spikes and defines dependencies.
• **Implement** builds working software - context optimized.
• **Loop** and Refit with change tickets or specification edits.

SAIL creates documentation and measures build quality and drift.

Rigging builds using your common stack rules and branding.

You are the Commander.

The Commander decides — the Commander is the Agile Product Owner. The LLM is your Agile Best Practices Team, and the QuarterDeck enables clear, accurate communication between the two. Drydock is a process representing system behavior — not sub-agents or prompt tricks.

Laying the keel

Drydock requires a subscription to an LLM service. We recommend sonnet or 5.4.

Charting the course

• Import markdown, source code, Spec Kit, or loose notes.
• Decompose into stories, acceptance, blockers, questions.
• If the LLM finds blockers → it stops and asks. Answer in the QuarterDeck/rerun.
• Output is Features, Stories, and AC for Review.

The QuarterDeck is your Agile Web interface to the process.

An optimized communication path between the Commander and the LLM Process.

• Analyze creates the story hierarchy, identifies blockers, and surfaces questionnaires for review.
• Answer and redirect or proceed. Your feedback is persisted.
• The Commander controls — The GOAL is Working Software you can Iterate.
• drydock rigging compact reduces context (Builder/User)

The Manifest is a Build Plan Dependency Graph.

• drydock plan turns analysis into typed Blueprints + Manifest.
• The LLM estimates Story Points (token cost) using the dependency graph.
• Drydock stacks the correct minimal context into build prompts.
• Context is engineered, not hoped for. Builds become reproducible.

IMPLEMENT - Sailing the frontier

• drydock build walks the graph and builds the runnable frontier. The build is done by one context optimized step at a time.
• Every step is verified against Test Driven Development acceptance criteria.
• drydock build score measures delivery health across seven dimensions — spec completeness, test coverage, drift, and more.

Rigging: your standards,
baked into every build.

Your branding, stack rules, and conventions — injected automatically.

Compaction keeps context lean across a large codebase.

The Refit

Software is never done. drydock refit changes the application while keeping the Blueprint and the code aligned.

• Option 1: Edit specification files. Drydock tracks git commits for every built file and does a minimal rebuild of only what changed.
• Option 2: Change tickets. Refit ties them to Blueprints so they can be built using minimized context.
• Option 3: Skill Driven Brainstorming and Automatic Change Ticket Creation.
• Summary: The specification is the source of truth. Minimal drift.

The differentiator is PROCESS
The process is Agile.

The goal: working software you can reliably iterate with an easy path to rebuild anytime.