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

Marketing Kit

/ak:watzup

Project status handoff

Generate a short, evidence-backed handoff from Git refs, worktrees, unfinished plans, and roadmap docs, with prioritized next steps and rationale.

01

Run scanner

02

Read state

03

Summarize work

04

Measure plans

Rule 01

Status and handoff only; never turn a wrap-up into implementation.

Rule 02

Evidence-backed summaries beat broad branch dumps.

Rule 03

Priority next steps should explain why they outrank the alternatives.

Rule 04

Do not pretend the full scan succeeded when fallback inspection was used.

Execution Map

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

01

Start

Input, scope, route

  1. 1 Run scanner From the project root, run scripts/watzup-scan.cjs with JSON output before writing the report.
  2. 2 Read state Capture branch or detached HEAD, dirty/clean state, active worktree, and scanner warnings.
02

Work

Agent / skill execution

  1. 3 Summarize work Select only the highest-signal recent branches and worktrees instead of dumping every ref.
  2. 4 Measure plans List unfinished plans with X/Y checkbox counts and percentage done across plan.md and phase files.
03

Verify

Gate, review, validation

  1. 5 Scan roadmap Include active milestones from roadmap or milestone docs when they exist.
  2. 6 Rank next steps Use scanner nextSteps priority, rationale, workspace alignment, status, provenance, and momentum signals.
04

Close

Report, handoff, artifact

  1. 7 Warn honestly Call out stale remotes, detached HEAD, dirty state, and any scanner failures instead of hiding uncertainty.
  2. 8 Fallback read-only If the scanner fails, say so and use minimal read-only Git/worktree/plan/roadmap inspection.

Syntax, arguments, subcommands

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

Syntax

/ak:watzup [branch|worktree|status]

Arguments

[branch|worktree|status]

Status focus

Optional handoff focus: current or named branch, active worktree, or overall checkout status. Omit it for the default local scan. Scanner helper flags stay on the scanner, not on this slash command.

/ak:watzup status

Subcommands

branch Branch focus
/ak:watzup branch

Summarize the current or highest-signal branch without dumping every ref.

Outcome: Branch-centered current state, recent work, unfinished plans, ranked next steps, and warnings.

/ak:watzup branch
worktree Worktree focus
/ak:watzup worktree

Orient around the active worktree, dirty or detached hygiene, and plans visible there.

Outcome: Active worktree path, branch or detached HEAD, dirty-state hygiene, in-flight plans, and the highest-ranked action.

/ak:watzup worktree
status Status focus
/ak:watzup status

Report overall checkout status: branch or detached HEAD, dirty/clean, plans, roadmap, and warnings.

Outcome: Local-only status handoff with checkbox progress, ranked next steps, and honest scanner or fallback warnings.

/ak:watzup status

Special Operations

Hygiene ranks first

Dirty worktrees and detached HEAD states outrank normal roadmap work because they can lose context.

No network by default

Remote refs stay local unless the user explicitly asks for fresh remote state.

Not conversation compaction

Use ak-handoff when a fresh agent needs decisions, rationale, and session context.

Sample Prompt

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

End-of-session handoff Recommended 
/ak:watzup
Use when:
You need a short local snapshot of what is in flight and what to do next.
Expected:
Runs the local JSON scanner, reports branch or detached HEAD, dirty state, in-flight plans with checkbox progress, ranked next steps, and warnings without inventing slash flags.
Branch focus 
/ak:watzup branch
Use when:
You want the highest-signal branch story instead of every ref in the repo.
Expected:
Centers the handoff on the current or highest-signal branch, counts unfinished plan checkboxes, and ranks next steps with rationale instead of dumping every ref.
Worktree orientation 
/ak:watzup worktree
Use when:
You entered a worktree or detached checkout and need the local situation quickly.
Expected:
Highlights the active worktree, branch or detached commit, dirty-tree or detached-HEAD hygiene, unfinished plans, and the highest-ranked action.
Checkout status 
/ak:watzup status
Use when:
You need overall checkout status, plan progress, and honest warnings without a remote fetch.
Expected:
Reports local-only checkout status, plan.md plus phase checkbox progress, roadmap milestones when present, ranked next steps, and scanner or fallback warnings.

Handled Scope

  • Run scanner
  • Read state
  • Summarize work
  • Measure plans
  • Scan roadmap
  • Rank next steps

Artifacts Produced

Brief handoff report

Pattern

Current State → Recent Work → Plans → Roadmaps → Next Steps → Warnings

Short status with progress annotations and five to six priority-ranked actions.

Next