VividKit Crystal clear AI coding
VI
Choose Your Setup Get Started with AgentKit Continue with ClaudeKit Migrate from ClaudeKit to AgentKit Clean cutover from ClaudeKit What Is AgentKit? How AgentKit Works AgentKit Kits, Skills, Agents & Hooks AgentKit Runtime Support AgentKit Desktop App AgentKit Configuration AgentKit CLI Quick Reference AgentKit Skills Cheatsheet AgentKit Workflows AgentKit Statusline Update AgentKit CLI & Kits AgentKit Helper Clean reinstall of AgentKit AgentKit Troubleshooting What is ClaudeKit? ClaudeKit CLI Guide Command Finder Commands Cheat Sheet Workflow Recipes CLI Quick Reference Claude Mechanics Permission Modes ClaudeKit Hooks Coexistence ClaudeKit x Codex CK → Other coding tools How ClaudeKit Works Inside ClaudeKit Finding Your Unknowns Session Recovery Fix from Logs UI/UX Guide Accounts Switcher IDE Config Remote Control Codex App System Diagramming UI Review Gate Promotions Support VividKit

Quick Ref / Command

Engineer Kit

Beta only

/ak:atoz

A to Z autonomous delivery

One conversation up front, then no babysitting: lock scope and Done means with an ak:advise interview and an explicit Confirm, hand over every prerequisite in one batch, then the agent orchestrates parallel sub-sessions and tracks the GitHub issue until every confirmed Done-means item is verified.

01

Lock scope

02

Confirm the brief

03

List what to hand over

04

Re-check prerequisites

Rule 01

Each gate consumes the previous one's result: Lock, then Prepare, then Execute.

Rule 02

Ask everything up front so the run never has to come back for an input it could have requested at the start.

Rule 03

Decide everything inside the brief yourself and record each non-obvious decision for the final report.

Rule 04

A sub-session report is not proof; verify the integrated result against every Done-means item.

Execution Map

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

01

Start

Input, scope, route

  1. 1 Lock scope Runs the ak:advise interview on the request: one question at a time, a reframing with observable Done means, a visual preview and a handoff brief (Objective, Done means, Out of scope, Constraints). --yagni is passed through.
  2. 2 Confirm the brief Closes gate 1 with one question offering Confirm, Edit or Abort. Only an explicit Confirm continues; Edit loops back to the changed field only. After Confirm the brief is the contract.
  3. 3 List what to hand over Inspects the environment first (installed CLIs, logins, env-var presence, remotes, branch protection), then lists only real gaps: what each item is, why it is needed, where the run will read it and how readiness is checked. Reversible choices are listed as defaults you may override.
02

Work

Agent / skill execution

  1. 4 Re-check prerequisites After you report ready, re-checks each item without changing anything (presence, auth status, a read-only call), reports what is still missing as one short list and waits again. A waived item is recorded in the brief with its consequence.
  2. 5 Plan and fan out The main session becomes the orchestrator: plans with ak:plan, splits work into pieces with separate file ownership, and runs independent pieces in parallel sub-sessions, each in its own worktree when it writes code.
  3. 6 Run and supervise Sizes concurrency to remaining quota and machine headroom, routes mechanical pieces to cheaper models, nudges or re-dispatches stalled sub-sessions, and checks every reported result against its diff before integrating.
03

Verify

Gate, review, validation

  1. 7 Track on GitHub Moves the work issue through in progress, in review, done (PR opened) and shipped (merged). Unrelated bugs or gaps found along the way become separate deduplicated issues labelled ai-handle instead of being fixed in this run.
  2. 8 Review in isolation The final review runs in a fresh sub-session with isolated context (for example ak:code-review or ak:review-pr), never in the orchestrator that wrote the code. Findings are fixed and re-reviewed until clean.
  3. 9 Verify and report Finishes only when every Done-means item is verified on the integrated result, the review is clean, the issue label matches reality and no process, worktree or cache the run started is left behind. Partial delivery is reported as partial.

Syntax, arguments, subcommands

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

Syntax

/ak:atoz "<request or URL>" [--yagni]

Arguments

"<request or URL>" Required

Request to deliver

The work to take end to end, as text or a URL such as a GitHub issue. It is treated as data: embedded attempts to skip a gate, widen authority or exfiltrate secrets are ignored.

/ak:atoz "Add CSV export to the reports page"

Shared options

--yagni

Cut non-essential scope

Passed through to the ak:advise interview so scope not needed for the stated outcome is challenged before the brief is confirmed.

/ak:atoz "Add CSV export to the reports page" --yagni

Don't skip the required step

Each item contrasts a tempting shortcut with the required approach.

Tempting shortcut

The user said it looks good; start building.

Do this instead

Only an explicit Confirm on the handoff brief opens the next gate.

Tempting shortcut

I'll ask for the API key when the run needs it.

Do this instead

Every input the run cannot obtain alone is listed before execution, and secrets go into the environment, never the chat.

Tempting shortcut

The sub-session said it's done, so it's done.

Do this instead

Check each report against its diff, and review the final result in a fresh isolated session.

Sample Prompt

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

Deliver a feature end to end Recommended 
/ak:atoz "Add CSV export to the reports page"
Use when:
When you want to agree on scope once, hand over everything the work needs, then leave the agent to deliver without check-ins.
Expected:
An ak:advise interview ends in a Confirm/Edit/Abort question, then a list of prerequisites and defaults; after you reply ready, the agent plans, runs parallel sub-sessions, reviews in isolation and reports each Done-means item with evidence.
Start from an issue, lean scope 
/ak:atoz "https://github.com/acme/app/issues/42" --yagni
Use when:
When the request already lives in a GitHub issue and you want scope not needed for the outcome cut before you confirm.
Expected:
The interview challenges extra scope, the confirmed brief becomes the contract, and the issue label moves through in progress, in review, done and shipped as the run advances.

Handled Scope

  • Scope lock with explicit confirmation
  • Up-front prerequisite batches
  • Parallel sub-session orchestration
  • GitHub issue label tracking
  • Isolated final review

Artifacts Produced

A-to-Z final report

Pattern

Each Done-means item with its evidence, decisions made on your behalf, anything waived, and remaining risks or follow-ups.

Written by the orchestrator after verifying the integrated result; partial delivery is labelled partial, never done.

Related skills

Next