handoff
Handoff
Use this skill to produce a compact handoff document for a fresh agent.
The handoff should preserve decisions, current state, blockers, and the next useful actions without restating large artifacts that already exist elsewhere.
Workflow
- Read the current conversation and identify:
- The user's goal
- Work already completed
- Open questions, blockers, and risks
- Concrete next steps
- Existing artifacts that already capture detail, such as PRDs, plans, ADRs, issues, commits, diffs, or generated files
- If the user supplied arguments, treat them as the expected focus of the next session.
- Tailor the handoff toward that next task.
- Emphasize the most relevant state and deprioritize unrelated context.
More from ouj/skills
rubber-duck
Collaborative design partner for coding problems, system design, bug fixes, and interface changes. Use when Codex should inspect the current project first, ask lettered multiple-choice questions one at a time, compare 2-3 clean solution approaches, draw before-and-after system interactions, and write a design doc before any implementation begins. Keep the focus on elegant interfaces and trade-offs, not production readiness, rollout, testing, or metrics.
10pr-stack
Manage stacked pull requests on top of plain git and GitHub CLI. Use when the user wants to create, inspect, restack, move, retarget, submit, or sync a stack of dependent branches and PRs while tracking parent branches explicitly, keeping each GitHub PR based on its recorded parent branch, and avoiding unsafe history rewrites.
8follow-my-lead
Finish an in-progress code change by reading the current git branch and especially the staged and unstaged diff to infer intent, then completing the implementation, migration work, interface changes, and repairs needed to make the change coherent. Use when the user already started work locally, wants the agent to pick up from the current branch state, wants intent inferred from unfinished edits, or wants plan-first collaboration with multiple-choice clarification before making changes.
4ask-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "ask me questions".
3brainstorm
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
3