Menú
Update progress and next-step docs so the next agent or session can resume with minimal context loss.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Run one bounded episteme Event end-to-end — branch, implement, verify, PR, merge, sync, doctor — with the repo's release and hook machinery handled correctly. Use when starting or closing a unit of work in the episteme repo (or any repo adopting its flow). Triggers on "new event", "이벤트 시작", "PR까지", "merge하고 sync", "release", "릴리즈", "브랜치 파서 작업".
Author the episteme gate artifact (.episteme/reasoning-surface.json) correctly on FIRST contact — schema, lens order, honest values, strict-vs-advisory, and when to escalate to epistemic-interrogation instead. Use the moment a PreToolUse hook reports a missing or stale Reasoning Surface, or BEFORE starting a session's first high-impact operation. Triggers on "reasoning surface", "Episteme Strict Mode", "surface stale", "blocked by episteme", "게이트 막힘", "서피스 갱신".
Devil's Advocate stress-testing for code, architecture, PRs, and decisions. Surfaces hidden flaws through structured adversarial analysis with metacognitive depth. Use for high-stakes review, stress-testing choices, or when the user wants problems found deliberately. NOT for routine code review (use /code-review). Triggers on "스트레스 테스트", "stress test", "devil's advocate", "반론", "이거 괜찮아", "문제 없을까", "깊은 리뷰", "critical review", "adversarial".
Senior-researcher interrogation of a load-bearing decision or conclusion — decompose into claims, verify the load-bearing ones in a fresh context with external evidence, argue the opposition, name the weakest link, pre-commit disconfirmation, record the verdict artifact the episteme gate reads.
Design and run unattended or long-horizon loops (overnight hardening, drain queues, iterative sweeps) with a written invariant the harness re-reads every iteration — no manual re-pasting, trustworthy metrics, explicit stop conditions, and correct model routing. Replaces bounded-loop-runner. Use for "overnight", "unattended", "keep iterating until", "밤새 돌려", "루프 돌려", ralph-loop or /loop driven work.
Prevents premature execution on ambiguous requests. Analyzes request clarity using 5W1H decomposition, surfaces hidden assumptions, and generates structured clarifying questions before work begins. Use at the start of any non-trivial task, or when a request could be interpreted multiple ways. Triggers on "뭘 원하는건지", "요구사항 정리", "clarify", "what exactly", "scope", "requirements", "정확히 뭘", "before we start".
| name | progress-handoff |
| description | Update progress and next-step docs so the next agent or session can resume with minimal context loss. |
Use this skill near the end of a work session or after substantial progress.
Convention check first: if the project's AGENTS.md (or operating contract)
declares its own handoff convention — different file names, a different form —
follow the project's declaration. Repo files own repo mechanics; the two
moves below are the episteme default for projects that declare none.
Handoff is two moves, and only two:
REPLACE docs/NEXT_STEPS.md. Overwrite it with the current state — do not
append. Include:
Append exactly ONE line to docs/EVENTS.md — one row in the history
index (| E<N> | date | one-line what happened | refs |). Nothing more; no
narrative body. Verbatim detail, if it must be kept, goes in archive/.
docs/PROGRESS.md is retired in this pattern. Do not create it and do not
write to it — its append-log shape was the disease compaction cured. The
one-line-per-event index (EVENTS.md) plus the REPLACE-form NEXT_STEPS.md
carry everything it used to.
Favor concise operational handoffs over narrative summaries.
