skills/handoff/SKILL.md
--- name: handoff description: Generate NEXUS-compliant handoff blocks when completing work. Use at the end of any significant task to create structured context for the next agent or session. disable-model-invocation: true allowed-tools: Read, Grep, Glob, Bash(git diff *), Bash(git log *), Bash(git status *) argument-hint: [agent-role] [task-id] --- ## NEXUS Handoff Generator Generate a handoff block for: **$ARGUMENTS** Reference the protocol: [HANDOFF_PROTOCOL.md](~/nexus/HANDOFF_PROTOCOL.md
npx skillsauth add ComputerConnection/zach-pack skills/handoffInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Generate a handoff block for: $ARGUMENTS
Reference the protocol: HANDOFF_PROTOCOL.md
Before generating the handoff, collect:
From Git:
From Memory:
From Current State:
Output a YAML block following this exact schema:
handoff:
from_agent: <$0 or "claude">
to_agent: <next agent or "any">
timestamp: <current ISO 8601>
task_id: <$1 or generate from context>
summary:
what_was_done: |
# 2-3 sentences. Be specific. What actually shipped?
decisions_made:
- decision: <what was decided>
rationale: <why - the "why" prevents future "why did we do this?">
alternatives_rejected:
- <option not taken and brief reason>
current_state:
files_modified: []
files_created: []
dependencies_added: []
config_changes: []
context_for_next_agent:
must_know:
# Critical facts. If missed, drift WILL happen.
- <fact>
- <constraint>
original_intent: |
# Restate the original goal. This is the anchor.
# Copy from ORIGINAL_BRIEF.md if it exists.
scope_boundaries:
in_scope:
- <what's included>
out_of_scope:
- <what's explicitly NOT included - even if tempting>
status:
completion: <complete | partial | blocked>
# Include if partial:
if_partial:
remaining_work:
- <specific task>
why_stopping: |
# Why hand off now?
# Include if blocked:
if_blocked:
blocker: |
# What's blocking?
needs_from: <who can unblock>
unblock_criteria: |
# What needs to happen?
next_steps:
immediate:
- <next action - be specific>
suggested_approach: |
# How might the next agent tackle this?
warnings:
- <gotcha or trap to avoid>
verification:
how_to_verify: |
# How to confirm this work is correct?
test_commands: []
expected_outcomes: []
# Optional sections - include if relevant:
technical_debt:
- item: <what was deferred>
reason: <why>
severity: <low | medium | high>
questions_for_zach:
- <decisions that need human input>
Before finalizing, verify:
If a NEXUS project structure exists, save to:
/nexus/projects/<project_id>/CURRENT_STATE.yaml
Also append to:
/nexus/projects/<project_id>/handoff_log/<sequence>_<from>_to_<to>.yaml
If no project structure, output the block for manual placement.
data-ai
Inject Zach's full identity, business context, and working preferences. Use at session start to eliminate cold starts. Lightweight context load — not a full agent like Vision, just who Zach is and how to work with him.
tools
--- name: vision description: "Zach's personal AI — his Jarvis. NOT a store agent. This is the owner's private command center that sits above everything else. Handles anything Zach needs — business, personal, technical, strategic, creative. High-systems AI: precise, anticipatory, authoritative. Invoke for ANY task." context: fork allowed-tools: Read, Grep, Glob, Bash, Edit, Write, Task, TodoWrite argument-hint: [what-do-you-need] — freeform. Vision figures out the rest. --- # VISION — Zach's Ja
development
Tauri-specific development patterns for NEXUS. Use when building desktop app features, handling IPC, or working with Rust backend.
development
Document Computer Connection store processes in AI-queryable format. Use to capture SOPs for the store AI server POC.