Menu
Configure or reconfigure aigent-OS identity, priorities, authority, projects, people, and decision logic
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | setup |
| description | Configure or reconfigure aigent-OS identity, priorities, authority, projects, people, and decision logic |
| trigger | /setup |
/start owns the day-one onboarding arc. /setup is the deeper configuration flow and may also be used later to revise one section.
Read .aigent/state.json first.
ready, route through /start unless the operator explicitly requested advanced setup.ready, ask which configuration area needs revision rather than replaying the entire interview.Before writing, set status: setup-in-progress while preserving any prior completedAt. On interruption, the next /start or /setup should resume from the last durably completed section.
Ask one question at a time and write each completed section immediately.
Ask for the operator's role, responsibilities, preferred collaboration style, and risk posture. Update system/00_identity.md without replacing framework-owned doctrine.
Ask for the top two or three active priorities, the most urgent outcome, operating mode, and blockers. Update vault/memory/ACTIVE_PRIORITIES.md.
Ask what the AI may handle autonomously, what needs confirmation, what is human-only, and whether spending has an escalation threshold. Update system/12_authority_matrix.md.
Ask what makes the operator accept or reject opportunities, their active-work limit, and their most common time trap. Update system/14_decision_framework.md.
For each active project, capture purpose, current state, priority, next action, and relevant people. Create or update notes under vault/projects/ and vault/people/, then connect them from active priorities with wikilinks.
Ask whether any specialized agents are useful now. For each accepted agent, capture name, scope, tools, model tier, escalation boundary, and success criteria. Store the definition in vault/agents/ with valid name: and tools: frontmatter so the installer can register it in .claude/agents/.
After all requested sections are durably written:
vault/memory/SESSION_LOG.md..aigent/state.json to:{
"schemaVersion": 1,
"status": "ready",
"completedAt": "<ISO-8601 timestamp>"
}
.aigent/first-run-done for compatibility with older installs./open, normal work, and /close.Do not mark the installation ready when required writes failed.
The capsule verb, invoked explicitly — reconcile from the live memory, write a resume-ready capsule, then stop. Mid-session checkpoint or completion capsule; a rolling best-effort version of the same write also runs automatically on every Stop event via daemons/stop-capsule-writer.mjs.
The resume verb, invoked explicitly — load the newest valid capsule by created_at, re-ground against live memory, then ACT on waiting_on. Mid-session or on explicit ask; the post-clear boot fires the same procedure automatically via daemons/resume-verb.mjs.
Run the volunteering ledger before declaring work done. Forces surfacing of what changed/didn't, what was noticed-but-not-fixed, what was guessed, and what tradeoffs were made on the principal's behalf. The standard - the principal should never be surprised later by something the agent knew at the time.
Capture a confident agent claim (Phase 1) or resolve one as right/wrong (Phase 2) in vault/memory/TRUST_DECAY.md. Builds the longitudinal record of agent calibration over time. Pairs with /honesty-check (which should reduce Phase 1 frequency) and /diagnose (which surfaces causes that often reveal Phase 2 events).
One evidence-gated pass that sequences /dream, /reconcile, /sweep-now, and /digest over your own vault, with a /system-check gate and a ledger-review pass over the measurement layer (Honesty Ledger, Trust Decay, Failure Modes). Stays exactly as human-gated as the legs it calls -- stages, never auto-applies. Skips a leg gracefully when there is nothing to do; every leg that runs leaves an evidence line.
Dispatch Hestia to run all 3 vault sweeps (DELEGATION_TRACKER stale items, HEAT_INDEX dormant flips, broken wikilinks) and append the result to HESTIA_SWEEP_LOG.