What problem does it solve?
Repositories where knowledge lives in chat history and people's heads force every new human or agent contributor to ask instead of read. Drydock lays the keel of a shared shipyard harness so every contributor inherits the same context, rules, tools, and standards from files in the repo.
Core Features & Use Cases
- Four-pillar scaffolding: Creates and seeds CLAUDE.md, CONTEXT.md, docs/adr/, docs/standards/, docs/business/, design-system/, .omc/skills/, .mcp.json, and scripts/ without clobbering existing files.
- Document language resolution: Detects or asks for a BCP-47 document language (including zh-Hans/zh-Hant script disambiguation) and persists it as the documentLanguage frontmatter key in CONTEXT.md.
- Drift auditing with --check: Read-only mode that reports missing surfaces, invalid language tags, dead CLAUDE.md links, and unused glossary terms.
- Use Case: When starting a repo that both humans and AI agents will build on, run drydock once to scaffold the harness, then let launch, retro, and code-review flows sediment decisions and standards into it over time.
Quick Start
Ask the agent to run the drydock skill in this repository to scaffold the shared shipyard harness and report what was created.