In short:
ak-atoztakes a request or an issue, settles a brief with you through anak-adviseinterview, asks for everything it needs in one pass, then runs on its own until each acceptance item in the brief is verified. Inside, it callsak-plan, splits the work across parallel sub-sessions and reviews in a separate session, so you do not need to call any other skill. It does not widen or change the scope after you Confirm, and it does not fix out-of-scope bugs: it opens a separate issue instead.
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 know exactly what you want and want to say it once and go do something else, or when you want to go all the way from a GitHub issue to a PR. You do not need it when you only want advice (use ak-advise) or only want to prepare and stop before running (use ak-goal-warmup).
flowchart LR
A["Request or issue URL"] --> B["ak-atoz"]
B --> C["ak-advise interview, you click Confirm"]
B --> X["You choose Abort: stop"]
C --> D["You hand over everything needed in one pass"]
D --> E["Runs on its own: ak-plan, parallel sub-sessions, separate review"]
E --> F["Reviewed PR, correctly labeled issue, final report"]It rests on 4 points:
| Point | Question | Example |
|---|---|---|
| The brief is the contract | After you confirm, what may it do and not do? | The brief records the goal, acceptance (Done means), non-goals and constraints. Once you click Confirm, it does not narrow, change or widen the scope on its own. |
| The handover list | Where would the automated run get stuck if something is missing? | "Need push access to the repo, checked with gh auth status. Need PAYMENT_API_KEY in the env file, only checked for presence, the value is never printed." |
| Stop conditions | When is it allowed to come back and bother you? | About to delete data or force-push when the brief does not allow it, about to spend money or send a message on your behalf, a token expiring mid-run. |
| Orchestrator and sub-sessions | Who writes the code, who checks it? | The main session only plans, splits the work, monitors, merges and verifies. Code is written in separate sub-sessions, each in its own worktree. The final review runs in a fresh session, free of the code writers' context. |
Reversible choices like branch names, small libraries or file structure are decided on the spot at gate 2 and recorded as defaults for you to change, instead of asking. In return, once you Confirm, the brief is the contract: if you want to change acceptance or widen the scope, it stops and asks rather than following along on its own.
Sample prompt for a new feature:
/ak-atoz "Add a PDF invoice export button on the order detail page of <app name>.
Outcome: users click Download invoice and get a PDF with the correct amount and tax.
Constraints: do not change the orders table schema, keep the existing orders API.
Not doing: emailing invoices, multi-language invoice templates.
Done when: there is a test for the amount on the PDF, and the PR is open with a clean review."| Flag | What it is for | Since ak |
|---|---|---|
--yagni | Settles the scope on the smallest version that does the job | 3.0.0-beta.32 |
Below is the detailed version: the run flow, 5 situations with prompts, each flag explained (when to use it, when you do not need it, what you get, which flags it combines with), 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-atoz: hand off a task once, it runs to done" on modernEngineer and apply it to this repo.
1. Call the content_get tool of the modernengineer MCP server with locale "en", slug "ak-atoz". 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-atoz
