Results for “drydock”

Designs, reconciles, and reviews an end-to-end Drydock program for safely staging agent runtimes: immutable worktree provenance, disposable VM containment, typed effect brokerage, global body accounting, resurrection, subscription-capacity economics, context compaction, operator control, evidence, and promotion. Use when several Drydock contracts must compose into one architecture, implementation hypertree, diagram set, or release plan. NOT for launching Port Daddy, running an untrusted subject, replacing focused containment/resurrection/capacity audits, or treating a design packet as runtime authority.

The English summary is being prepared. Showing the original description.

Guide a development brief through specification, dependent tickets, implementation, review, and verification. Coordinate parallel work while keeping human approval at key decisions and recording agreed vocabulary, business rules, and the reasons behind technical choices.

• Turning a development brief into a specification and tickets
• Coordinating parallel implementation across dependent tickets
• Approving acceptance criteria and testing boundaries

Write or revise instructions, specifications, tickets, and skill files so an agent can act without prior chat history. Make rules checkable, explain their reasons, define completion criteria, and keep authoritative information in one place.

• Clarifying instructions in CLAUDE.md
• Making specifications and tickets actionable
• Adding completion criteria to skill procedures

Sets up shared project rules and a glossary so people and AI agents work from the same context. It preserves existing documents, introduces additional records when needed, and provides a check mode to audit inconsistencies.

• Setting up shared rules for a new development project
• Moving project knowledge out of chat history
• Preparing documentation for new contributors