deepwork

Orchestrates multi-phase coding workflows with delegated specialists and mandatory review gates.

Updated Sep 13, 2023
One-click install
npx skills add https://github.com/dlwlrmax/.dotfiles --skill deepwork-dlwlrmax
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deepwork
Source: https://github.com/dlwlrmax/.dotfiles/tree/main/opencode/.config/opencode/skills/deepwork
Command: npx skills add https://github.com/dlwlrmax/.dotfiles --skill deepwork-dlwlrmax

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large, high-risk coding efforts—cross-cutting refactors, unsafe-to-partially-ship migrations, multi-phase architectural changes—often fail because a single agent tries to implement everything without structure, review, or persistent state. Deepwork turns the AI into a scheduler that plans phases, delegates to specialists, and enforces review gates before work proceeds. ## Core Features & Use Cases - Persistent Session State: Maintains a task-specific markdown progress file under .slim/deepwork/ capturing goals, research, plans, validation results, and blockers across the session. - Phased Delegation with Oracle Gates: Splits work into coherent delivery phases, delegates to specialist agents (oracle, librarian, explorer, designer, fixer), and requires an Oracle review after each phase with a bounded re-review budget. - Scheduler Discipline: Tracks task/session IDs, waits for background job completion before consuming results, and blocks phase advancement until terminal results are reconciled. - Use Case: Migrating a monolith's authentication layer across multiple services—plan the phases, delegate each to specialists, gate each with an Oracle review, and commit only at validated delivery boundaries. ## Quick Start Ask the AI to use the deepwork workflow to plan and execute a large multi-phase refactor with specialist delegation and review gates after each phase.

Frequently Asked Questions about deepwork

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage a large multi-phase coding task with an AI agent?▼

Use an orchestrator workflow that splits the work into coherent delivery phases, delegates each phase to specialist agents, and requires a review gate before advancing. Deepwork implements this with a persistent progress file and mandatory Oracle reviews per phase.

When should I use the deepwork workflow?▼

Use it only for large or high-risk work: multiple dependent phases, cross-cutting architectural change, or migrations unsafe to ship partially. Do not use it for trivial edits, quick docs changes, simple bug fixes, or routine bounded features.

How many Oracle re-reviews are allowed per phase gate?▼

Each planned Oracle gate gets one initial review plus at most two re-reviews. Request a re-review only when remediation materially changes the reviewed decision or risk; after exhaustion, record remaining risk and ask the user how to proceed.

Where does deepwork store its progress state?▼

Progress files live in a task-specific markdown file under .slim/deepwork/, kept git-local via .gitignore entries while remaining readable by OpenCode through .ignore rules. Code and documentation deliverables go to normal project paths like src/ or docs/.

What are the limitations of the deepwork orchestration approach?▼

It adds planning, delegation, and review overhead, so it is wasteful for routine multi-file changes or small features. It also depends on specialist agents like oracle, librarian, explorer, designer, and fixer being available in the environment.