Menu
Karpathy-style recap of deepwork history — reads DEEPWORK_WIKI.md Overview and the last 3 log entries, outputs 30-50 plain-text words
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | deepwork-recap |
| description | Karpathy-style recap of deepwork history — reads DEEPWORK_WIKI.md Overview and the last 3 log entries, outputs 30-50 plain-text words |
| allowed-tools | ["Read(${CLAUDE_PROJECT_DIR:-$(pwd -P)}/.claude/deepwork/DEEPWORK_WIKI.md)"] |
Produce a brief plain-text recap of the project's deepwork history. Modeled on CC's own /recap — short, factual, no markdown.
Read ${CLAUDE_PROJECT_DIR:-$(pwd -P)}/.claude/deepwork/DEEPWORK_WIKI.md. If the file is absent or empty, respond: "No deepwork sessions recorded yet." and stop.
Extract:
## Overview section (everything between ## Overview and the next ## heading)# Log — each entry is a ## [YYYY-MM-DD] lineOutput 1-2 plain sentences. Target 30-50 words. Constraints:
.md artifacts with task_id frontmatter, append one line at the end:
"Gate-list: tasks completed across bar criteria (instance <8-hex>)."
Implementation: glob archived instance dir for *.md, extract task_id and bar_id
frontmatter via Read tool, count distinct task_ids and distinct bar_ids. Skip if no
frontmatter present (back-compat with pre-fix artifacts).Example shape:
Four deepwork sessions across the project; three approved, one cancelled at SYNTHESIZE. Latest (2026-04-21) approved a changelog pipeline with a dry-run flag. Open thread: the auth middleware rewrite paused on a legal-compliance question.
Lightweight single-gate amendment for execute mode — spawns MICRO-TEAM (CRITIC + 1 specialist) for re-verdict without full deepwork re-run
View execute-mode session status — phase, plan_hash, drift, change_log, test results, 3-dimension verdict table, rollback log, discoveries
Run a deepwork session: research/design convergence (default) or plan execution (--mode execute). Design mode spawns a 5-archetype oppositional team and delivers an approved plan. Execute mode drives faithful implementation of an approved plan via role-asymmetric agents.
View deepwork session status — phase, team, bar verdicts, proposals, guardrails
End an active deepwork session — graceful per-teammate shutdown, archives state, and restores settings. CLI auto-cleans team dirs at session end. Works for both mid-flight abort and post-HALT cleanup.
Add, remove, or list written-bar criteria for the active deepwork session