In short:
ak-sowatlooks at what you just did, an issue or a PR through a product owner's eyes, then tells you what it means for users, whether you are prioritizing the wrong thing, and up to 3 next steps. You pick a step and hand it to a doing skill, such asak-planorak-fix. It does not change code or issue state.
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 just finished something, or have an issue or PR in hand, and want to know "so what". Do not use it to fix code or close issues: it only analyzes and advises.
flowchart LR
A["Recent work, issue or PR"] --> B["ak-sowat"]
B --> C["What it means for users"]
B --> D["Up to 3 ordered next steps"]
D --> E["You pick one and hand it to the right skill"]
B --> F["Stop, analysis only"]It answers 4 questions:
| Lens | Question | Example |
|---|---|---|
| So what | What did the work change for users or the product? | The new checkout page is in code but not released yet |
| Priority correction | Are you pouring effort into low-value work? | Tweaking animation while failed sign-ups block existing users |
| Next steps | What next, why now, what does success look like? | Fix email confirmation, success when sign-up completion returns to its old level |
| Facts and inference | What has evidence, and what is only a guess? | Checked: tests pass. No evidence yet: whether users use it |
The priority correction only appears when the current direction is clearly wrong, and it must name a concrete trade-off. It may add a defer or skip list for work that is tempting but not worth it right now.
Sample prompt for right after you finish:
/ak-sowat Recent changes on branch <branch name>.
Desired outcome: new users create their first project within 5 minutes.
Tell me what this means and what to do next.This skill has no flags. After the command, write one of three things: recent changes, an issue, or a PR, plus a few sentences about the outcome you want.
Below is the detailed version: the run flow, 5 situations with prompts, the input that takes the place of flags, 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-sowat: point out what is worth doing next" on modernEngineer and apply it to this repo.
1. Call the content_get tool of the modernengineer MCP server with locale "en", slug "ak-sowat". 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-sowat
