deepwork

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

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

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 at once without structured planning, delegation, or review checkpoints. Deepwork enforces a scheduler-style orchestration model with persistent state and gated reviews. ## 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 Review Gates: Splits work into coherent delivery phases, delegates to specialist agents (oracle, librarian, explorer, designer, fixer), and requires an Oracle review gate after each phase with a bounded re-review budget. - Scheduler Discipline: Tracks task/session IDs, waits for background job completion before advancing, and commits at independently valid delivery boundaries. - Use Case: Migrating a codebase to a new module architecture where each phase changes dependency direction—deepwork coordinates research, phased implementation, structure scans, and gated reviews before each commit. ## Quick Start Ask the AI to use the deepwork workflow to plan and execute this large multi-phase refactor with Oracle 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 project with an AI agent?▼

Use an orchestrator workflow that splits work into coherent delivery phases, delegates implementation to specialist agents, and enforces a review gate after each phase. Deepwork maintains a persistent markdown progress file recording goals, plans, validation results, and blockers across the session.

When should I use the deepwork workflow?▼

Use deepwork 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 do AI code review gates work between implementation phases?▼

After each phase, the orchestrator runs validation, updates the progress file with changed paths and evidence, then requests an Oracle review before continuing. Each gate allows one initial review plus at most two re-reviews for material changes.

What are the limitations of orchestrator-based coding workflows?▼

Orchestration adds planning and review overhead, making it wasteful for routine multi-file changes or simple fixes. It also depends on specialist agents being available and requires disciplined state tracking to avoid advancing while background jobs are unreconciled.

How does deepwork handle design changes during implementation?▼

Designer output is treated as accepted design intent for later phases. Follow-up visual, motion, or component-feel changes route back to the designer, while bounded mechanical fixes like wiring or type corrections go to a fixer agent without altering the design.