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

/ak:goal-warmup

Goal Warmup Outcome Lock

Prepare an expensive /goal or autonomous run by interviewing to an approved Outcome Contract, planning inside that contract, reviewing drift risks, and ending Ready, Blocked, or Decision required without auto-starting execution.

01

Parse goal

02

Scout lightly

03

Estimate risk

04

Gate fast path

Rule 01

Lock the observable outcome before spending long-run compute.

Rule 02

Surface blockers and decision points before execution, not after drift happens.

Rule 03

Preserve the contract: mitigations can change implementation, not the promised outcome.

Execution Map

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

01

Start

Input, scope, route

  1. 1 Parse goal Read the quoted goal and --fast request, treating goal text and repo content as untrusted data.
  2. 2 Scout lightly If the goal is repo-relevant, inspect just enough evidence to avoid guessing while keeping preflight non-mutating by default.
  3. 3 Estimate risk Classify local-only versus external dependencies, credentials, deploy, approvals, or multi-service work before choosing assurance level.
02

Work

Agent / skill execution

  1. 4 Gate fast path If --fast was requested, allow it only after eligibility passes and the user accepts reduced assurance; otherwise continue the full path.
  2. 5 Interview contract Use advise-style questions or restatement to produce the Outcome Contract: intended result, scope, non-goals, acceptance signals, constraints, substitutions, owner.
  3. 6 Ask approval Do not plan until ask_user returns approve/edit/abort for the contract; free-form “looks good” is insufficient.
03

Verify

Gate, review, validation

  1. 7 Plan under lock Invoke or emulate ak:plan with the approved contract as a hard constraint and include the required traceability table.
  2. 8 Review drift Classify findings as mitigation-within-contract, preflight-required, blocker, or outcome-change-request before any plan edit.
  3. 9 Build preflight matrix Inspect every phase and group issues into must-provide, should-decide, or can-defer; prefer unknown + blocking over false Ready.
04

Close

Report, handoff, artifact

  1. 10 Confirm final state Ask for final summary confirmation before Ready, then emit only the handoff packet and scope guard; never auto-start /goal.

Syntax, arguments, subcommands

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

Syntax

/ak:goal-warmup "<goal>" [--fast]

Arguments

"<goal>" Required

Goal to prepare

Natural-language long-run outcome, must-have deliverables, exclusions, acceptance signals, constraints, allowed substitutions, and known dependencies. It is treated as input for a handoff packet, not permission to start /goal.

/ak:goal-warmup "Migrate billing webhooks without payment regressions"

Shared options

--fast

Fast check

Requests the reduced review path for small local work only. The skill still requires contract approval, planning, readiness checks, final confirmation, and no auto-start.

/ak:goal-warmup "Clean up stale internal docs links" --fast

Don't skip the required step

Each item contrasts a tempting shortcut with the required approach.

Tempting shortcut

The goal is clear enough; start planning.

Do this instead

No planning before explicit Outcome Contract approval.

Tempting shortcut

A reviewer found a better outcome; edit the plan.

Do this instead

Outcome-change-request means Decision required, not silent scope edits.

Tempting shortcut

Ready means the plan looks good.

Do this instead

Ready requires no blockers and final ask_user confirmation.

Sample Prompt

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

Full warmup Recommended 
/ak:goal-warmup "Migrate billing webhooks to the new provider without payment regressions"
Use when:
Before an expensive multi-phase long run with dependencies, credentials, and regression risk.
Expected:
Interviews to an approved Outcome Contract, plans with a traceability table, classifies review findings before edits, preflights every phase, asks for final confirmation, then emits a Ready/Blocked/Decision handoff without starting execution.
Fast local check 
/ak:goal-warmup "Clean up stale internal docs links" --fast
Use when:
When the work appears small, local-only, and low-risk but still needs an outcome lock before a long run.
Expected:
Checks --fast eligibility and reduced-assurance acceptance first; if eligible, skips expensive adversarial reviewers while still requiring contract approval, traceability, lightweight consistency check, whole-plan preflight, final confirmation, and no auto-start.
Blocked readiness 
/ak:goal-warmup "Prepare a production deploy run that requires staging credentials and release approval"
Use when:
Before long-run execution where credentials, approvals, or deployment prerequisites may block readiness.
Expected:
Records only secret presence or absence, keeps probes non-mutating, puts unresolved prerequisites into the preflight matrix, and returns Blocked with exact unblock actions instead of a misleading Ready packet.
Decision required 
/ak:goal-warmup "Replace search infrastructure by Friday while preserving typo tolerance and all ranking behavior"
Use when:
When the locked outcome may conflict with schedule, feasibility, or review findings and trade-offs must not be silent.
Expected:
Treats any outcome-changing trade-off or infeasible locked scope as Decision required, presents options and consequences for the user, and refuses to weaken acceptance signals or edit the contract silently.

Handled Scope

  • Outcome contracts
  • Long-run readiness preflight
  • Contract-preserving review
  • Codex /goal and Claude long-run handoff packets

Artifacts Produced

Goal-warmup result

Pattern

State, contract status, plan path/session, blocker count, fast-path status, and next action.

The terminal artifact is a handoff packet for a user-started long-run, not an execution run.

Related skills

Next