メニュー
Prepare a session handoff — summarize progress, annotate tasks with current status, and identify what's ready for the next session. Use at the end of a work session or when the user says they're done for now.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | handoff |
| description | Prepare a session handoff — summarize progress, annotate tasks with current status, and identify what's ready for the next session. Use at the end of a work session or when the user says they're done for now. |
Prepare context for the next session so work can continue seamlessly.
Review active tasks — call task_list with filter +ACTIVE to find tasks that were being worked on. Use the UUIDs from that response for the calls below; do not rely on UUIDs you remember from earlier in the session. For each task in the result:
task_annotate to record what was accomplished and what remainstask_stop to mark it as no longer activeReview pending tasks — call task_list with filter status:pending to see the full backlog. Note any tasks whose status has changed based on work done this session.
Log unplanned work — if work was done that wasn't tracked as a task, use task_log to record it retroactively with appropriate project and tags.
Update blocked tasks — if any blockers were resolved this session, use task_modify to remove dependencies or update descriptions.
Present the handoff summary:
Keep the summary concise — the goal is to give the next session (or agent) a clear starting point.
Pick up a task from the backlog and implement it. Reads the spec if one exists, starts the task, does the work, and marks it done. Use when the user wants to work on a specific task or the next available task.
Break down a goal into actionable tasks with dependencies, priorities, and optional specs. Use when the user wants to plan work, decompose a feature, or create a task breakdown.
Review and improve the backlog — identify vague tasks, missing priorities, broken dependencies, tasks needing specs, and stale items. Use when the user wants to groom, refine, clean up, or improve their task backlog.
Write a detailed spec document for a task before implementation begins. Use when the user wants to define requirements, acceptance criteria, or technical design for a task.
Daily standup summary — what was completed recently, what's in progress, and what's blocked. Use when the user asks for a standup, status update, or summary of recent work.
Show the current task backlog — pending, active, blocked, and overdue tasks. Use when the user asks about tasks, status, what needs to be done, or what's in progress.