القائمة
Structured work handoff across context boundaries: triage decisions, constraints, and remaining work into a prompt-quality transfer document. Invoke whenever task involves handing off work — session restart, teammate delegation, async resumption, or any context boundary crossing.
Design and iterate Claude Code skills: SKILL.md structure, description formulas, content architecture, and quality evaluation. Invoke whenever task involves any interaction with Claude Code skills — creating, reviewing, evaluating, debugging, or improving skills.
Project glossary for consistent domain terminology. Invoke whenever task involves creating, updating, or referencing a glossary, defining domain terms, establishing ubiquitous language, or when inconsistent naming causes confusion in code or planning artifacts.
Task creation for issue trackers — structured descriptions, acceptance criteria, field categorization, and tracker linking. Invoke whenever task involves creating work items in any issue tracker — bugs, features, stories, tasks, or any tracked work from standalone requests or decomposition documents.
Coding workflow covering discovery, planning, implementation, and verification. Invoke whenever task involves any interaction with code — writing, modifying, debugging, refactoring, or understanding codebases. Runs discovery protocol before language-specific skills engage.
Rust language conventions, idioms, error handling, concurrency (CPU-bound parallelism with threads/rayon and I/O-bound async with Tokio), the cargo/clippy/rustfmt toolchain, and rustdoc. Invoke whenever task involves any interaction with Rust code — writing, reviewing, refactoring, debugging, or understanding .rs files and Cargo projects.
Rust testing conventions and frameworks: built-in #[test], integration, and doctest layout plus the cargo-nextest runner and the proptest, insta, criterion, mockall, and rstest ecosystem. Invoke whenever task involves any interaction with Rust tests — writing, running, configuring, or debugging tests in .rs files and Cargo projects.
| name | handoff |
| description | Structured work handoff across context boundaries: triage decisions, constraints, and remaining work into a prompt-quality transfer document. Invoke whenever task involves handing off work — session restart, teammate delegation, async resumption, or any context boundary crossing. |
| disable-model-invocation | true |
A handoff document is a prompt — an instruction set for the receiving agent. Triage your context into a structured, information-dense transfer document that preserves high-value state and drops noise.
Two modes, determined by who receives the handoff:
If the user doesn't specify, ask.
Separate your context into two categories before writing anything.
Keep — state that must survive the boundary:
Drop — noise in transfer:
Generate a markdown document. Omit sections with no content — empty headers are noise.
# Handoff: [task name]
## Context
[1-2 sentences: what this work is about and its current state]
## Decisions
- [decision]: [rationale]
## Constraints
- [constraint]: [why it matters]
## External Resources
- [resource type]: [identifier/URL]
## Remaining Work
1. [highest priority next step]
2. [subsequent steps...]
## Verification State
- [what was tested/verified and result]
- [what remains untested]
## Open Questions
- [question]: [context needed to resolve]
Same structure as self-handoff, with these sections added before Decisions:
## Codebase Orientation
- [key file/directory]: [relevance to this task]
## Recommended Skills & Tools
- [skill or tool]: [why it's needed]
## Conventions
- [convention]: [where it's documented]
Target 500-2000 tokens. When work is large:
After generating the handoff, verify:
If Decisions or Remaining Work is empty when work was done, the triage missed something. Re-examine the conversation.