VividKit Crystal clear AI coding
VI
Choose Your Setup Get Started with AgentKit Continue with ClaudeKit Migrate from ClaudeKit to AgentKit Clean cutover from ClaudeKit What Is AgentKit? How AgentKit Works AgentKit Kits, Skills, Agents & Hooks AgentKit Runtime Support AgentKit Desktop App AgentKit Configuration AgentKit CLI Quick Reference AgentKit Skills Cheatsheet AgentKit Workflows AgentKit Statusline Update AgentKit CLI & Kits AgentKit Helper Clean reinstall of AgentKit AgentKit Troubleshooting What is ClaudeKit? ClaudeKit CLI Guide Command Finder Commands Cheat Sheet Workflow Recipes CLI Quick Reference Claude Mechanics Permission Modes ClaudeKit Hooks Coexistence ClaudeKit x Codex CK → Other coding tools How ClaudeKit Works Inside ClaudeKit Finding Your Unknowns Session Recovery Fix from Logs UI/UX Guide Accounts Switcher IDE Config Remote Control Codex App System Diagramming UI Review Gate Promotions Support VividKit

Quick Ref / Command

Engineer Kit

/ak:handoff

Agent Continuation Contract

Create one redacted Markdown handoff that lets a fresh coding agent resume safely, with mission, guardrails, workspace state, decisions, verification, blockers, exact next actions, and source pointers.

01

Identify reader

02

Resolve destination

03

Probe read-only state

04

Separate evidence

Rule 01

Write a continuation contract, not a transcript dump.

Rule 02

Prefer observed workspace facts and explicit uncertainty over invented continuity.

Rule 03

Redaction and collision safety are part of the artifact, not optional polish.

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Identify reader Use handoff when the next reader is another coding agent continuing this exact task; use watzup for human project status.
  2. 2 Resolve destination Use plans/reports/handoff-<YYYYMMDD-HHmm>-<slug>.md by default, or a workspace-local explicit output path; ask before writing if no plans root exists.
02

Work

Agent / skill execution

  1. 3 Probe read-only state Collect git root, branch, HEAD, status, and optional bounded diff/status evidence without mutating the repo.
  2. 4 Separate evidence Distinguish observed facts from session assertions, and use “Not captured in this session” for unknown sections.
03

Verify

Gate, review, validation

  1. 5 Fill report schema Include the verified handoff content: title, time, focus, goal, current state, decisions and rejected approaches, verification, files and pointers, open work, and a fresh-agent prompt.
  2. 6 Redact secrets Pass the artifact and optional diff/status through the redaction catalog for tokens, cookies, keys, credentials, private URLs, and personal data.
04

Close

Report, handoff, artifact

  1. 7 Guard collisions Refuse an existing target unless --force is explicitly present; never rename or delete silently.
  2. 8 Write matching outputs Return one fenced Markdown block in the response and save the same content as the timestamped report.

Syntax, arguments, subcommands

How to invoke the skill: syntax, positional arguments, shared options, then each subcommand with its own syntax and outcome.

Syntax

/ak:handoff [task focus] [--output PATH] [--include-diff] [--include-status] [--force]

Arguments

[task focus]

Next-session focus

Optional one-line focus for the successor agent. It is used in the Mission section and filename slug after credential-looking values are refused.

/ak:handoff "Continue the authentication migration after the failing integration test is diagnosed"

Shared options

--output PATH

Exact output path

Write the handoff to this workspace-local path instead of the auto timestamped plans/reports path. It does not imply overwrite permission.

/ak:handoff --output plans/handoffs/oauth-callback.md
--include-diff

Include diff evidence

Append redacted git diff --stat and the first 200 diff lines, with truncation marked when the diff is longer.

/ak:handoff --include-diff --include-status
--include-status

Include status snapshot

Append a redacted git status --short snapshot without turning the handoff into a full repository status report.

/ak:handoff --include-status
--force

Allow overwrite

Explicitly allow overwriting an existing handoff target. Without it, an existing file is refused with guidance.

/ak:handoff --force --output plans/handoffs/oauth-callback.md

Don't skip the required step

Each item contrasts a tempting shortcut with the required approach.

Tempting shortcut

The transcript has everything; paste it.

Do this instead

Never dump raw transcripts or hidden reasoning; capture only actionable continuation facts.

Tempting shortcut

The path exists; overwrite it.

Do this instead

Existing targets require explicit --force.

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Bare capture Recommended 
/ak:handoff
Use when:
You are about to switch sessions and need a successor-ready contract.
Expected:
Creates a workspace-local plans/reports Markdown artifact with the verified handoff schema, fills unknowns as “Not captured in this session,” and returns the same content as a fenced Markdown block.
Focused handoff 
/ak:handoff "continue the OAuth callback fix"
Use when:
The successor should focus on one known thread of work.
Expected:
Screens the focus for credential-looking values, then uses the safe text in the Mission section and filename slug so the successor agent knows the exact thread to resume.
Explicit artifact 
/ak:handoff --output plans/handoffs/oauth-callback.md
Use when:
You need a stable handoff path instead of an auto timestamped slug.
Expected:
Writes to the exact workspace-local path and creates the parent directory if needed; if that target already exists, it refuses with mtime guidance unless --force is explicitly added.
Dirty-worktree evidence 
/ak:handoff --include-diff --include-status
Use when:
The successor needs bounded, redacted workspace evidence about modified or untracked files.
Expected:
Adds redacted git status --short plus git diff --stat and the first 200 diff lines with truncation marked, while keeping the main handoff schema and return value unchanged.

Handled Scope

  • Session continuation capture
  • Redacted state summaries
  • Exact next action handoffs
  • Workspace-local Markdown artifacts

Artifacts Produced

Handoff report output

Pattern

One fenced Markdown block in the response, matching the content saved to the timestamped report.

The response block and saved report must match, and redacted values must not be reconstructable.

Next