菜单
Use when the user manually requests a deep-work phase document review. Parses --phase, --structural, and --adversarial compatibility arguments, then enters the canonical adaptive review protocol.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
This skill should be used at Phase 3 of deep-work to execute slice-based TDD (RED → GREEN → REFACTOR) for each approved plan slice. Dispatches in solo (inline) or team (implement-slice-worker subagent delegation by cluster_id) mode, runs computational sensors (lint/typecheck/coverage), performs 2-stage slice review (delegate reviewer + evaluator_model), and emits M3-envelope-wrapped receipts/SLICE-*.json via hooks/scripts/wrap-receipt-envelope.js. Triggered by 'implement phase', '구현 시작', '/deep-work continue', /deep-implement slash, cross-platform Skill({ skill: "deep-work:deep-implement", args: "..." }), or orchestrator dispatch after plan approval.
This skill should be used at Phase 2 of deep-work, after research.md approval, to design a detailed implementation plan with TDD slices. Decomposes work into SLICE-NNN units with `depends_on` DAG, acceptance contracts (`failing_test`, `acceptance_threshold`), and optional `cluster_id` hint for parallel-safe grouping. Emits plan.md with the inline slice DAG (Implement Phase's deep-implement skill parses it for worker fan-out — no external slices.md/slice-graph.json is emitted). Triggered by 'create implementation plan', '계획 수립', /deep-plan slash, cross-platform Skill({ skill: "deep-work:deep-plan", args: "..." }), or orchestrator dispatch after research approval.
Author the executable spec contract for deep-work research sessions. Invoked through /deep-spec, $deep-work:deep-spec, or orchestrator dispatch.
This skill should be used when the user invokes /deep-work "task", uses cross-platform Skill({ skill: "deep-work:deep-work-orchestrator", args: "task" }), asks to start a new deep-work session, or requests evidence-driven workflow auto-flow across Brainstorm → Research → Plan → Implement → Test phases. Handles session initialization (profile v3 load, capability detection, session-recommender sub-agent, AskUserQuestion 4-key ask, flag parsing) and dispatches the 5-phase pipeline with Exit Gates between each phase.
Use when the user finishes a deep-work session — merging, opening a PR, keeping the branch as-is, or discarding. Triggers on `/deep-finish`, "finish session", "wrap up session", "세션 마무리", "세션 종료", "PR 만들어줘", or orchestrator auto-call after Phase 5 (Integrate) completes. Emits an M3-envelope-wrapped `session-receipt.json` (and optionally a cross-plugin `handoff.json`). Supports `--skip-integrate` (Phase 5 bypass), `--handoff-to=<plugin>` / `--no-handoff` (post-finish handoff control).
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.
| name | deep-phase-review |
| description | Use when the user manually requests a deep-work phase document review. Parses --phase, --structural, and --adversarial compatibility arguments, then enters the canonical adaptive review protocol. |
| user-invocable | true |
v6.12: 실행 계약은 adaptive-review-protocol.md + review-policy-runtime.js가 정본
이 skill은 수동 document review의 진입점과 args parser만 소유한다. reviewer 선택, fallback, severity, degraded, finding verdict는 본문에 재정의하지 않는다.
| 인자 | 의미 |
|---|---|
| `--phase=brainstorm | research |
--structural | 호환 플래그: structural-only single override 요청 |
--adversarial | 호환 플래그: dual override 요청 |
두 mode 플래그가 함께 있으면 dual로 해석한다. 알 수 없는 값은 경고 후 무시한다.
work_dir, current phase,
methodology_policy_json, review_execution_json을 읽는다.$WORK_DIR/<phase>.md 존재를 확인한다. 없으면 경로와 생성
command를 표시하고 종료한다.../shared/references/adaptive-review-protocol.md)하고
artifactKind:'document', phase, state risk/policy/review override, 감지 채널을 입력으로
조립한다. --structural/--adversarial compatibility 요청은 승인된
reviewModeOverride로만 전달한다.compileReviewPlan → reviewers → evaluateReviewExecution → finding verdict → persistence 순서를 실행한다. structural role은
Read(../shared/references/review-gate.md)의 차원과 snapshot 계약을 사용한다.review_execution_json과 호환 phase_review/review_results에 기록하고
decision/verdict/open finding/degraded event를 표시한다.Critical human-gate 또는 pause/needs-human이면 여기서 멈추며 자동 phase advance를 하지 않는다.