Run any Skill in Manus with one click

deep-work

Stars10

Forks1

UpdatedMay 18, 2026 at 13:11

Use when the user invokes /deep-work "task", uses cross-platform Skill({ skill: "deep-work:deep-work", args: "task" }) or $deep-work:deep-work "task", asks to start a new deep-work session, or requests the primary Evidence-Driven Development auto-flow entry point. This is a compatibility alias for deep-work-orchestrator and preserves the historical /deep-work entry name.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Sungmin-Cho

Sungmin-Cho/claude-deep-work

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

SKILL.md

readonly

name	deep-work
description	Use when the user invokes /deep-work "task", uses cross-platform Skill({ skill: "deep-work:deep-work", args: "task" }) or $deep-work:deep-work "task", asks to start a new deep-work session, or requests the primary Evidence-Driven Development auto-flow entry point. This is a compatibility alias for deep-work-orchestrator and preserves the historical /deep-work entry name.
user-invocable	true

Deep Work Entry Alias

This skill preserves the historical /deep-work <task> entrypoint name for Codex and other skill-based callers.

Forward the invocation to deep-work-orchestrator with the same $ARGUMENTS and follow that skill's instructions exactly:

Skill("deep-work-orchestrator", args="$ARGUMENTS")

More from this repository

same repository

deep-implement

Sungmin-Cho/claude-deep-work

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.

2026-07-2210

deep-plan

Sungmin-Cho/claude-deep-work

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.

2026-07-2210

deep-spec

Sungmin-Cho/claude-deep-work

Author the executable spec contract for deep-work research sessions. Invoked through /deep-spec, $deep-work:deep-spec, or orchestrator dispatch.

2026-07-2210

deep-work-orchestrator

Sungmin-Cho/claude-deep-work

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.

2026-07-2210

deep-finish

Sungmin-Cho/claude-deep-work

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).

2026-07-2110

deep-phase-review

Sungmin-Cho/claude-deep-work

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.

2026-07-2110

name	deep-work
description	Use when the user invokes /deep-work "task", uses cross-platform Skill({ skill: "deep-work:deep-work", args: "task" }) or $deep-work:deep-work "task", asks to start a new deep-work session, or requests the primary Evidence-Driven Development auto-flow entry point. This is a compatibility alias for deep-work-orchestrator and preserves the historical /deep-work entry name.
user-invocable	true

Deep Work Entry Alias

This skill preserves the historical /deep-work <task> entrypoint name for Codex and other skill-based callers.

Forward the invocation to deep-work-orchestrator with the same $ARGUMENTS and follow that skill's instructions exactly:

Skill("deep-work-orchestrator", args="$ARGUMENTS")