Menü
Use when starting a new session that continues previous work, or when a handoff document is provided
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Use when reviewing a spec or task graph for completeness before implementation
Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, logging in, or automating browser actions
Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, logging in, or automating browser actions
Use when decomposing a spec, design, or feature description into a task dependency graph with self-evaluating acceptance criteria
Use when doing creative product, feature, component, functionality, or behavior design work
Use when infrastructure or features are built but before declaring done -- verifies work is wired into the system and actively used
| name | resume-handoff |
| description | Use when starting a new session that continues previous work, or when a handoff document is provided |
Resume work from a handoff document by reading it fully, verifying current state, and proposing a course of action.
tasks.completed, tasks.in_progress, tasks.remaining, and tasks.epic before continuing, along with decisions, learnings, and next stepsHandoffs without a tasks: section are incomplete state; reconstruct tracked task state before continuing.
Check for each of the 4 scenarios:
| Scenario | Signal | Action |
|---|---|---|
| Clean continuation | All changes present, no conflicts | Proceed with next: items |
| Diverged codebase | Changes missing or modified since handoff | Reconcile differences, adapt plan |
| Incomplete work | Tasks marked in_progress | Complete unfinished work first |
| Stale handoff | Significant time passed, major refactoring occurred | Re-evaluate strategy entirely |
Verify tracked task state before continuing:
tasks.completed entries are actually present in the current codebase or task trackertasks.in_progress entries before starting tasks.remainingtasks.remaining as the next work queue only after unfinished in-progress work is resolvedtasks.epic as the parent context when creating or resuming tracked tasksI've analyzed the handoff from [date]. Current situation:
**Completed work:** [verified present/missing/modified]
**Key decisions:** [still valid/changed]
**Recommended next actions:**
1. [Most logical next step]
2. [Second priority]
Shall I proceed, or adjust the approach?
next: items from handoff into tasksoro task ready for any tracked worktasks.completed, tasks.in_progress, tasks.remaining, and tasks.epic state with tracked tasks before selecting the next taskworked: and avoid failed: approachesfailed: approaches (repeating mistakes)