deepwork

Orchestrates phased multi-specialist coding workflows with Oracle review gates and persistent progress files.

1|Updated Mar 15, 2025
One-click install
npx skills add https://github.com/adikpb/dotfiles --skill deepwork-adikpb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deepwork
Source: https://github.com/adikpb/dotfiles/tree/main/.config/opencode/skills/deepwork
Command: npx skills add https://github.com/adikpb/dotfiles --skill deepwork-adikpb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large, high-risk coding efforts with multiple dependent phases often fail due to lost context, unreviewed intermediate work, and poor coordination between specialist agents. This Skill structures such work into planned phases with review gates and a persistent progress file. ## Core Features & Use Cases - Phased Orchestration: Splits large work into coherent implementation phases based on dependencies and delivery boundaries, delegating to specialist agents like @designer, @fixer, and @librarian. - Oracle Review Gates: Runs an @oracle review after each planned phase, with batched remediation passes and follow-up reviews only when decisions or risks change. - Persistent Session State: Maintains a markdown progress file under .slim/deepwork/ capturing research findings, plans, review notes, and validation results, kept git-local via .gitignore and .ignore rules. - Use Case: When migrating a codebase architecture across several modules, use this Skill to plan phases, delegate each phase to specialists, gate progress on Oracle reviews, and track all decisions in one progress file. ## Quick Start Use the deepwork skill to plan and orchestrate this large multi-phase refactoring with specialist delegation and Oracle review gates.

Frequently Asked Questions about deepwork

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

FAQPage Schema
How do I orchestrate a large multi-phase coding task with AI agents?▼

Activate deepwork to plan coherent implementation phases from the work's dependencies, delegate each phase to specialist agents, and gate progress on Oracle reviews. A persistent markdown file under .slim/deepwork/ tracks plans, research, and validation results.

When should I use deepwork instead of handling a task directly?▼

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

How do Oracle review gates work between implementation phases?▼

After each planned phase, the orchestrator validates results, updates the deepwork file, and asks @oracle to review before continuing. Actionable findings are batched into one bounded remediation pass, with follow-up reviews only if decisions or risks change.

Why does deepwork create a .slim/deepwork progress file?▼

The file serves as persistent session state capturing goals, confirmed research, phase status, review notes, and blockers. It is kept git-local via .gitignore and .ignore entries so OpenCode can read it without committing it.

How does deepwork preserve designer intent across later phases?▼

Designer output is treated as accepted design intent and recorded in the deepwork file. Later phases preserve layout, motion, spacing, and component feel, routing visual changes back to @designer and using @fixer only for mechanical non-visual follow-up.