In short:
ak-watzupscans git, unfinished plans and roadmap files indocs/, then writes a short report with 5 to 6 ranked next steps, each with a one-line reason. To keep decisions and session context for a new agent, useak-handoff. It only reads: no edits, no commits, no branch switches, no fetch unless you ask.
Disclosure: I maintain AgentKit and have an affiliate relationship with it: the AgentKit link in this post is an affiliate link; buying through it gets you 30% off.
Summary
Use it when you come back to a project after a few days, open a new worktree, or are about to end a session and need to know where everything stands. Do not use it to hand off to another agent: the report only holds status and next steps, and that job belongs to ak-handoff.
flowchart LR
A["Back to the project or end of session"] --> B["ak-watzup"]
B --> C["Short report + ranked next steps"]
C --> D["You pick what to work on"]
A --> E["Need to keep decisions for a new agent"]
E --> F["ak-handoff"]The report rests on 4 things:
| Thing | Question | Example |
|---|---|---|
| Scanner evidence | What is the report based on? | Current branch, worktrees, local and remote branches, unfinished plans, docs/*roadmap*.md |
| Plan progress | How far along is each open plan? | 12/20 todos · 60% done, counted from - [ ] and - [x] boxes |
| Next-step order | What should come first? | An in-progress plan in the open worktree goes first, plans at 40 to 90% get a bonus |
| Local remote refs | Is a teammate's remote branch the latest? | By default it reads the refs already on disk, no network, with a warning |
The scanner's order is only a suggestion. Your current goal, release blockers and known risks go first, with a reason, and the original score stays visible. Uncommitted changes are not treated as blockers, and never as a reason to discard them.
Sample prompt for coming back after a few days:
/ak-watzup I'm back on <project name> after a week off.
Tell me what is in flight and what I should do first.This skill has no flags. You can type branch, worktree or status after the command, but the skill does not describe what each word changes. To refresh remotes before the scan, say so in the prompt.
Below is the detailed version: the run flow, 5 situations with prompts, the change history by ak release, and common pitfalls. The detailed version and the interactive page are for subscribers. Your agent can also search them through the portal's MCP.
Opens when your account has subscriber access
This guide is for subscribers
Once your account has access, the full piece, the interactive visual and the agent call all open.
- Sign in or create a modernEngineer accountReading access belongs to your account email.
- Choose a plan on the pricing page1, 3 or 12 months, paid by VietQR bank transfer. Access opens about a minute after the money arrives.
- Or redeem a Facebook subscriber codePeople supporting the page on Facebook get an activation code by message each month.
Already a subscriber? Sign in to read.
Use this piece in your agent
Get an API keyCopy the text below and paste it into Claude Code, Codex or whichever agent you use. The agent reads the piece and checks it against the repo you have open.
Read "ak-watzup: sum up work in flight and rank next steps" on modernEngineer and apply it to this repo.
1. Call the content_get tool of the modernengineer MCP server with locale "en", slug "ak-watzup". If the modernengineer MCP server is not connected, stop and walk me through connecting it from https://modernengineer.dev/en/mcp.
2. Summarize the main steps of the piece and point out which apply to this repo.
3. Propose concrete changes and ask me before editing any file.Connect MCP in Claude Code (once)
claude mcp add --transport http modernengineer \
https://api.modernengineer.dev/mcp \
--header "Authorization: Bearer <API key>"Reading the full piece over MCP needs an API key from a subscriber account or one that bought this guide. Without access, the agent only gets the opening.
- Version
- v1.0.0
- Updated
- 22/10/2026
- Licence
- All rights reserved
- Slug
- ak-watzup
