--json Structured evidence
Emit structured evidence for the handoff. This does not refresh remote refs.
/ak:watzup --json Ctrl K
Quick Ref / Command
Engineer 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 Run scanner From the project root, run scripts/watzup-scan.cjs with JSON output before writing the report.
- 2 Read state Capture branch or detached HEAD, dirty/clean state, active worktree, and scanner warnings.
02
Work
Agent / skill execution
- 3 Summarize work Select only the highest-signal recent branches and worktrees instead of dumping every ref.
- 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
- 5 Scan roadmap Include active milestones from roadmap or milestone docs when they exist.
- 6 Rank next steps Use scanner nextSteps priority, rationale, workspace alignment, status, provenance, and momentum signals.
04
Close
Report, handoff, artifact
- 7 Warn honestly Call out stale remotes, detached HEAD, dirty state, and any scanner failures instead of hiding uncertainty.
- 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 [--json] [--fetch] [--since <date>] [--max-branches <n>] [--plan-limit <n>] [--max-plan-refs <n>] [--redact-paths]Shared options
--fetch Refresh remotes
Run git fetch --all --prune before scanning. This contacts configured remotes and updates/prunes local remote-tracking refs; omit for the default local-only report.
/ak:watzup --fetch--since <date> Commit sample window
Limit sampled commits per branch. This does not limit plan or roadmap discovery.
/ak:watzup --since 2026-08-01--max-branches <n> Branch summary limit
Limit branches summarized. Omitted branches still exist.
/ak:watzup --max-branches 20--plan-limit <n> Short-output plan limit
Limit unfinished plans included in short output. This does not prove excluded plans are complete.
/ak:watzup --plan-limit 8--max-plan-refs <n> Tracked plan ref limit
Limit ranked refs inspected for tracked plan files. A warning records truncation.
/ak:watzup --max-plan-refs 40--redact-paths Redact absolute paths
Replace absolute paths with stable labels. This does not redact branch names, commit subjects, or document content.
/ak:watzup --redact-pathsSpecial 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 JSON scanner, reports branch or detached HEAD, dirty state, in-flight plans with checkbox progress, ranked next steps, and warnings.
Refresh remote refs first
/ak:watzup--fetch
- Use when:
- You explicitly authorize a remote refresh before the handoff because local remote-tracking refs may be stale.
- Expected:
- Runs the scanner with fetch enabled, then separates fresh ref evidence from checkout status, plans, roadmap milestones, next steps, and warnings.
Fresh worktree orientation
/ak:watzup- 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.
Cross-branch plan scan
/ak:watzup- Use when:
- You want visible worktrees and tracked refs checked for unfinished plans and checklist progress.
- Expected:
- Deduplicates visible and tracked plan evidence, counts plan.md plus phase-file checkboxes, and ranks next steps by status, alignment, provenance, and momentum.
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.