AtReady

View saved version →

---
name: atready
description: Add one user-declared resource to an AtReady roster through a conversational preview-and-save flow, or turn a rough project goal into a resource-fit plan grounded in the saved roster. Use when the user explicitly invokes AtReady to add, onboard, register, or save a resource, or asks AtReady to match saved resources to project steps before implementation. Do not activate for ordinary project planning, casual tool mentions, unrelated inventory editing, or project execution.
---

# AtReady

AtReady handles intake and fit. Codex owns planning. Requires a local Codex task, Python 3.11 or newer, trusted `uv`, the separately installed reviewed runtime, and local file access; unsupported in ChatGPT Chat or Work, Codex cloud or remote, mobile, and the Codex IDE extension.

Resolve `SKILL.md` directory. Resolve one already-installed Python 3.11 or newer interpreter.
Replace both absolute placeholders and run the bundled launcher. Never invoke a bare `atready` command or bypass
the launcher. It uses trusted `uv`, offline and without configuration files, resolves its exact
tool bin, verifies the runtime contract, and never searches `PATH` for `atready`.

## Response discipline

Respect concise, short, brief, quick, promo, or on-screen limits. For a direct question
without routing or state change, use no more than three short sentences or bullets. During a workflow,
give only current facts and one next action. Do not repeat boundaries or the prompt. Keep exact
targets, CLI preview or receipt, mutation state, uncertainty, separate approval, and route boundaries.
Never change route or mutation status to satisfy a limit.

## Resource intake workflow

Use this branch before planning when the user asks to add one resource.

### 1. Conversation fast path

If the resource is unnamed, ask only `What resource do you want to add?` and stop. Do not read,
inspect state, or invoke the launcher. Use no tools, memory, repository, or filesystem access;
narrate nothing.

Once the name is known, read only [quick-resource-intake.md](references/quick-resource-intake.md).
Do not read another reference or run any command during the question or recap turns. Ask only its
unanswered three questions; a bare-name reply gets all three. Then render its compact recap and ask
`Preview this entry?` Corrections are facts, not approval: apply them, rerender the recap, and
require its approval. Recaps use no tools and expose no internal work.

### 2. Preview, approve, and save

Only after approval of an unchanged bundled-purpose Quick Setup recap,
read [quick-resource-preview.md](references/quick-resource-preview.md). Read
[resource-onboarding.md](references/resource-onboarding.md) only for Detailed Setup, a custom or
ambiguous resource, a corrected purpose, extra planning facts, any `Not sure` answer, or a complete
declaration. Reuse known facts; ask only what remains. This is the first point where local execution
or filesystem access may be used. Otherwise request authorization or direct the user to standalone
`atready add`. Static `exec` is host-only; never present it as a human fallback.

For Quick Setup, show only the CLI-owned `human_preview` unchanged. Detailed Setup shows the
complete CLI preview. Then stop for a separate `Save exactly this entry?` approval. A fact,
declaration, or target change requires
a fresh recap and preview. Stale revision or plan tokens follow the one-retry rule below without a
recap. Never claim success from an uncertain apply receipt or retry apply.

On a no-write preview mismatch, preserve approved task-local facts and invite exact `retry preview`
once. Rerun without intake or recap. If it mismatches, say nothing was saved and do not offer
another retry. It never retries apply, reuses old tokens, saves, or waives save approval.

Exclude discovery, scans, account or billing inspection, credentials, tokens, and private notes.
Use only user-stated facts. Do not use the planning output
contract and do not append 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 9 — file references are metadata, not package contents.