deep-work

Delegated implementation worker for deep-work's Implement phase. Receives a list of slice IDs to execute and runs the full TDD + Sensor + Slice Review protocol for each. Invoked by the deep-implement skill. <example> Context: solo implement — parent delegates all slices to one worker prompt: "cluster_ids=[SLICE-001,SLICE-002,SLICE-003]; sequential; tdd_mode=strict" </example> <example> Context: team implement with multiple subagents — each worker handles one cluster prompt: "cluster_ids=[SLICE-004]; tdd_mode=strict; evaluator_model=opus" </example>

Delegated research worker for deep-work's Research phase on existing codebases. Invoked by the deep-research skill (not by the user directly). Takes an area parameter and analyzes the corresponding codebase areas, writing findings to $WORK_DIR/research{-area}.md. <example> Context: parent skill runs Research in solo mode prompt (parent → agent): "area=full; work_dir=/.../deep-work; task=..." </example> <example> Context: parent skill runs Research in team mode, arch area prompt (parent → agent): "area=architecture; work_dir=...; task=..." </example>

Delegated research worker for deep-work's Research phase on NEW projects (project_type=zero-base). Takes an area parameter and researches technology choices, conventions, and data models — with explicit authority to search the web for up-to-date framework/library information. <example> Context: zero-base project, solo mode, full research prompt: "area=full; work_dir=/.../deep-work; task=Build a CLI for X" </example> <example> Context: zero-base, team mode parallel, tech-stack area prompt: "area=tech-stack; work_dir=...; task=..." </example>

Deep-work 세션 초기화 시 task description + workspace meta + capability를 분석하여 5개 ask 항목(team_mode, start_phase, tdd_mode, git, model_routing)에 대한 추천 값을 fenced JSON으로 반환합니다. <example> Context: 사용자가 "Refactor authentication module" task로 deep-work 호출 prompt: { "task_description": "Refactor authentication module", "workspace_meta": { "git_status": "clean", "recent_commits": [], "top_level_dirs": ["src", "tests"] }, "capability": { "git_worktree": true, "team_mode_available": true } } expected_output: ```json { "team_mode": { "value": "team", "reason": "리팩터 + 인증 = 다중 모듈 변경 예상" }, "start_phase": { "value": "research", "reason": "기존 코드 구조 파악 필요" }, "tdd_mode": { "value": "strict", "reason": "인증 모듈은 core 안정성 요구" }, "git": { "value": "worktree", "reason": "리팩터 범위 격리 필요" }, "model_routing": { "value": "default", "reason": "표준 흐름" } } ``` </example>

Use when the user wants to generate or view the comprehensive deep-work session report — session lifecycle, slice summary, evidence trail, TDD compliance, sensor pass-rate, model usage, evaluation outcomes. Triggers on `/deep-report`, `/deep-status --report`, "session report", "deep-work report", "세션 리포트", "세션 보고서", "리포트 생성". Writes to `$WORK_DIR/report.md` and prints inline summary. Sub-page of the deep-status hub.

This skill should be used during deep-work Phase 1 to research an existing codebase (architecture/patterns/risks) via research-codebase-worker, or to investigate a zero-base project's tech stack/conventions/data-model via research-zerobase-worker (using WebSearch + Context7 for up-to-date library docs). Consumes evolve-insights and harnessability M3 envelopes as context. Triggered by 'start research phase', 'analyze codebase', /deep-research slash, cross-platform Skill({ skill: "deep-work:deep-research", args: "..." }), or orchestrator dispatch after brainstorm approval. Solo/Team mode automatic based on project size.

Use when the user wants plan-alignment verification — comparing the approved plan against actual implementation to detect unimplemented items, out-of-scope changes, and design drift. Triggers on `/drift-check`, "plan drift", "drift detection", "plan alignment", "플랜 드리프트", "계획 정합성", "드리프트 검증", or auto-invocation by `/deep-test` as the Required Gate (blocks on drift). Read-only — does NOT modify code. Saves results to `$WORK_DIR/drift-report.md` when in workflow mode.

Use when the user wants SOLID design-principles code review — evaluating SRP / OCP / LSP / ISP / DIP compliance on a target file/directory/glob. Triggers on `/solid-review`, "SOLID review", "design review", "design principles", "SOLID 검증", "디자인 리뷰", "원칙 검증", or auto-invocation by `/deep-test` as the Advisory Quality Gate (does not block). Review-only — does NOT modify code. Saves results to `$WORK_DIR/solid-review.md` when in workflow mode.

Use when the user wants to inspect deep-work's assumption health report — Wilson Score-based per-assumption confidence, verdict (justified / loosen / drop), model-aware split, and decay history. Triggers on `/deep-assumptions`, `/deep-status --assumptions`, "assumption health", "rule justification", "loosen enforcement", "어썸션 헬스", "규칙 정당화", "가정 검증". Reads session evidence to decide whether deep-work's hook denylist + receipt validation rules are still justified. Sub-page of the deep-status hub.

7 hooks across 4 events