English | 한국어

Deep Work Plugin

<!-- Badges (populated after sessions) --> <!--  --> <!--  -->

A Claude Code plugin that implements an Evidence-Driven Development Protocol — a single-command auto-flow orchestration (Brainstorm → Research → Plan → Implement → Test) with TDD enforcement, receipt-based evidence collection, and strict separation of planning and coding.

Role in Harness Engineering

deep-work is the core harness engine in the Deep Suite ecosystem, implementing the Harness Engineering framework (Böckeler/Fowler, 2026).

In the 2×2 matrix (Guide/Sensor × Computational/Inferential), deep-work covers:

• Computational Guides: Phase Guard hook (physically blocks edits), Worktree Guard (P0, hard-blocks writes outside worktree), TDD state machine (RED→GREEN), topology templates (phase-specific guides)
• Computational Sensors: Linter/typecheck pipeline, coverage, mutation testing, 4 drift sensors, fitness rules, review-check sensor, Phase Transition Injector (P1, condition context injection)
• Inferential Guides: Research/plan/brainstorm documents, Sprint Contract
• Self-Correction Loop: SENSOR_RUN → SENSOR_FIX → SENSOR_CLEAN with per-sensor 3-round independent limit

deep-work also produces receipts and health reports consumed by deep-review and deep-dashboard.

The Problem

Common pitfalls when AI coding tools tackle complex tasks:

• Introducing new patterns while ignoring the existing architecture
• Reimplementing utilities that already exist
• Jumping into implementation before understanding the codebase
• Adding unrequested "improvements" that cause bugs
• Marking work as done without verification

The Solution

The Brainstorm → Research → Plan → Implement → Test workflow enforces evidence-driven development:

• Phase 0 (Brainstorm): Optional design exploration — "why before how" (skip with --skip-brainstorm)
• Phase 1 (Research): Deep analysis and documentation of the codebase
• Phase 2 (Plan): Slice-based implementation plan with per-slice TDD fields, requiring user approval
• Phase 3 (Implement): TDD-enforced slice execution — failing test → production code → receipt collection
• Phase 4 (Test): Receipt completeness, spec compliance review, code quality review, verification evidence

Code file modifications are physically blocked during Phases 0, 1, 2, and 4 (via PreToolUse hook). Bash file-writing commands (echo >, sed -i, cp) are also intercepted. File changes and receipt data are automatically collected during Phase 3 (via PostToolUse hook).

Usage (Auto-Flow)

# Just one command — the entire workflow runs automatically
/deep-work "Implement JWT-based user authentication"

# The auto-flow orchestrates: Brainstorm → Research → Plan → [user approves] → Implement → Test → Report
# Plan approval is the ONLY required interaction

# Check unified status (replaces /deep-report, /deep-receipt, /deep-history, /deep-assumptions)
/deep-status              # current progress
/deep-status --report     # session report
/deep-status --receipts   # receipt dashboard
/deep-status --history    # cross-session trends
/deep-status --assumptions # assumption health
/deep-status --all        # everything at once

# Compare two sessions
/deep-status --compare

Commands

Primary Commands (7)

Command	Description
/deep-work <task>	Auto-flow orchestration — runs the entire Brainstorm → Research → Plan → Implement → Test pipeline automatically. Plan approval is the only required interaction.
/deep-research	Manual override for Phase 1 (Research) — deep codebase analysis
/deep-plan	Manual override for Phase 2 (Plan) — slice-based implementation planning
/deep-implement	Manual override for Phase 3 (Implement) — TDD-enforced slice execution
/deep-test	Phase 4: Receipt check → spec compliance → code quality → quality gates. Now auto-runs drift-check, SOLID review, and insight analysis.
/deep-status	Unified view — current progress, report, receipts, history, assumptions. Flags: --report, --receipts, --history, --assumptions, --all, --compare
/deep-debug	Systematic debugging: investigate → analyze → hypothesize → fix (auto-triggers on failures)

Deprecated Commands (13)

These commands still work but are now absorbed into the auto-flow. You no longer need to call them manually.