القائمة
Use this skill when ending a session and you want the next session to pick up where you left off. The goal is to capture enough context for seamless session continuity.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use this skill when the user has a rough idea, wants to explore a feature, or says "let's brainstorm" or "help me design." The goal is to refine an idea into a validated design doc before any code is written.
Use this skill when starting feature work that needs isolation from the current workspace, or when you need to work on multiple branches simultaneously. The goal is to create an isolated worktree with a verified clean baseline.
Use this skill when fixing a bug caused by invalid data reaching deep into execution. The goal is to add validation at every layer the data passes through, making the bug structurally impossible to reproduce.
Use this skill when documentation has drifted from the codebase, needs an inventory, or should be archived.
Autonomous implementation pipeline. Reads a plan file, reviews it adversarially,
>-
| name | onex-handoff |
| description | Use this skill when ending a session and you want the next session to pick up where you left off. The goal is to capture enough context for seamless session continuity. |
| disable-model-invocation | true |
Use this skill when ending a session and you want the next session to pick up where you left off. The goal is to capture enough context for seamless session continuity.
Sessions end for many reasons — context limits, breaks, or task switches. Without an explicit handoff, the next session starts cold and wastes time rediscovering state. This skill captures the current working context into a structured manifest so the next session can resume efficiently.
Capture current state. Record the essential context:
Summarize progress. Write a brief summary of what was accomplished in this session. Focus on decisions made, approaches chosen, and any non-obvious context that would be lost.
Document remaining work. List what still needs to be done, in order. Be specific — "implement the validation layer in auth.py" is useful; "finish the feature" is not.
Note blockers and warnings. Record anything the next session should know: failing tests with known causes, environment issues, dependencies on external work, or decisions that need user input.
Write the handoff manifest.
Save to a session-specific path such as docs/archive/dev/handoffs/YYYY-MM-DD-<short-slug>.md or docs/plans/YYYY-MM-DD-session-handoff.md. Prefer not overwriting archived continuity docs unless the user explicitly asks for a specific file by name. The manifest should be self-contained — a reader with access to the repo but no prior context should understand what to do next.
A handoff document containing:
