handofflisted

Create handoff documents for tightly scoped implementation tasks sized to fit in a single Claude Code context window (target 50-60% max context). Handoffs embed core mandates, verification loops, and spec context so they can be passed to dedicated short-lived subagents that implement the task and exit. Designed for subagent dispatch (pass handoff as prompt to a Task tool subagent).
matthull/my-skills · ★ 0 · AI & Automation · score 75

Install: claude install-skill matthull/my-skills

# Handoff — Task Context Briefing Creator Create self-contained handoff documents that brief a competent implementing agent on **what** to build and **where** to look — never **how** to build it. Each handoff is sized for a single Claude Code context window (target: 50-60% max context). Handoffs embed core mandates directly (injection in depth). Practice skills are referenced as mandatory loads for the implementer. **The architect loads this skill and writes handoffs directly.** There is no separate "handoff writer" agent — the agent with the deepest codebase understanding writes the briefing. **Workflow:** `/spec` → `/taskout` → **`/handoff`** (architect writes) → subagent dispatch (via Task tool) ## Usage ``` /handoff <task-reference-or-description> ``` **Examples:** - `/handoff @specs/project/TASKS.md task 1.1` — Single task from TASKS.md - `/handoff @specs/project/TASKS.md task 1.1 1.2 1.3` — Multiple tasks in parallel - `/handoff implement user authentication service` — Freeform description - `/handoff @specs/project/tasks.md T001-T003` — Task range ## Input Modes ### Mode A: Task File Reference (Preferred) - **Pattern:** `@<file-path> task <task-numbers>` - Extract file path and task numbers, spawn parallel subagents ### Mode B: Freeform Description - **Pattern:** Any text without `@` or `task` keyword - Process directly in main conversation ### Mode C: Task Range - **Pattern:** `@<file-path> T001-T003` - Parse range, extract tasks, spawn parallel subagents