Evidence-backed project handoff

Short evidence-backed handoff reports from branches, worktrees, unfinished plans, roadmap docs, and priority-ranked next steps.

Run scanner

Read state

Score next steps

Summarize work

Rule 01

Evidence first: scanner output grounds the handoff.

Rule 02

Priority ranking favors current workspace alignment, in-progress work, provenance, and useful momentum.

Rule 03

Keep handoffs short; report high-signal state and concrete next actions.

Rule 04

Never pretend fallback equals a completed full scan.

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

Start

Input, scope, route

1 Run scanner Start at project root with node scripts/watzup-scan.cjs --json; add --fetch only when the user asked to refresh remotes. The scanner supports --redact-paths to replace absolute paths with stable labels; it does not redact branch names, commit subjects, plan titles, or status text.
2 Read state Use scanner output for local and remote refs, registered worktrees, dirty state, detached HEAD, unfinished plans, and active roadmap milestones.

Work

Agent / skill execution

3 Score next steps Rank nextSteps by status, current workspace alignment, provenance, and momentum; hygiene issues always rank first.
4 Summarize work Keep only high-signal recent branches, worktrees, plan progress, checkbox counts, and roadmap items.

Verify

Gate, review, validation

5 Fallback carefully If the scanner fails, say it failed, include the error, and use only the documented minimal read-only fallback commands.
6 Report Return Current State, Recent Work, In-Flight Plans, Roadmaps, 5–6 prioritized Next Steps, and Warnings.

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

Syntax

/ak:watzup [--fetch]

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

Session handoff Recommended

/ak:watzup

Use when:: Use at the end of a session or when entering a fresh worktree.
Expected:: Brief report with current state, in-flight plans, next steps, warnings, and confidence notes.

Fresh remotes

/ak:watzup refresh remotes before reporting

Use when:: Use only when the user explicitly requests remote refresh before status.
Expected:: Scanner path may include fetch, then reports stale-ref caveats and branch-specific next steps if any.

Branch status

/ak:watzup what is in flight on this branch

Use when:: You need a read-only handoff of current work, not an implementation pass.
Expected:: Reports current state, in-flight plans, next steps, warnings, and confidence notes without changing git.

Handoff report

Pattern

Current State → Recent Work → In-Flight Plans → Roadmaps → Next Steps → Warnings

Five to six next actions with one-line rationale, plus branch/worktree/plan evidence.