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:codex-goal

Guide Codex /goal work

Guide Codex /goal work with one durable objective, explicit checkpoints, validation commands, and a verifiable stop condition.

01

Check availability

02

Apply use test

03

Draft objective

04

Name inputs

Rule 01

Durable objective, not generic iteration.

Rule 02

Validation is part of the contract, not an afterthought.

Rule 03

Pause for ambiguity instead of inventing product decisions.

Rule 04

Official Codex documentation is the source of truth for /goal behavior.

Execution Map

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

01

Start

Input, scope, route

  1. 1 Check availability Confirm /goal appears in Codex slash commands; if missing, enable the documented goals feature.
  2. 2 Apply use test Require longer-than-one-turn mechanical work, verifiable validation, and enough clarity for autonomous progress.
02

Work

Agent / skill execution

  1. 3 Draft objective Write one objective, not a mixed backlog; name the exact desired end state.
  2. 4 Name inputs Tell Codex which plan, issue, files, or docs to read first.
03

Verify

Gate, review, validation

  1. 5 Set constraints Preserve contracts and prohibit weakening, narrowing, skipping, or deleting tests to satisfy the goal.
  2. 6 Define validation Specify the command or explicit artifact Codex must use after each checkpoint.
04

Close

Report, handoff, artifact

  1. 7 Set stop condition Stop when the verifiable end state is reached or when further work needs human input.
  2. 8 Review final diff After Codex finishes, inspect the resulting diff before merging or relying on it.

Syntax, arguments, subcommands

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

Syntax

/ak:codex-goal <objective | goal draft>

Arguments

<objective | goal draft> Required

Objective or draft

Describe the long-running Codex work to turn into a bounded goal contract, or paste an existing draft for review. The Skill does not start the Codex goal for you.

/ak:codex-goal "Finish the TypeScript migration, preserve behavior, keep strict mode clean, and make the focused test suite pass"

Sample Prompt

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

Migration goal Recommended 
/ak:codex-goal "Complete the React Query migration for the account pages; preserve public behavior and pass pnpm test account"
Use when:
A scoped mechanical migration needs Codex-native /goal guidance across checkpoints.
Expected:
Drafts a reviewable /goal contract with one objective, read-first files, unchanged contracts, checkpoint validation, and a verifiable stop condition.
Goal draft review 
/ak:codex-goal "Review this /goal draft: modernize the billing module and make it better"
Use when:
You already wrote a goal draft and need to catch vague scope, missing validation, or unsafe autonomy before starting it.
Expected:
Tightens the draft into one durable objective or rejects it as a poor /goal fit, with constraints, validation, and human-input stop points.
Suitability check 
/ak:codex-goal "Should I use /goal to refactor the checkout tests over several checkpoints?"
Use when:
You need to decide whether a longer task is mechanical and verifiable enough for Codex Goal mode.
Expected:
Applies the three-part use test, flags exploratory or decision-heavy risk, and either produces a bounded goal contract or recommends another workflow.

Handled Scope

  • Check availability
  • Apply use test
  • Draft objective
  • Name inputs
  • Set constraints
  • Define validation

Related skills

Next