autocomp-ticklisted

Run exactly one tick of the autocomp autonomous company — read state, plan via the CEO role, dispatch role subagents, gate any money/send/destructive action through approvals, record everything to the append-only ledger, report, and reschedule. Use when running or resuming the autocomp loop in the autocomp repo, or when the user says "run a tick", "/autocomp", "advance the company", or starts the loop.
Eastkap/autocomp · ★ 4 · AI & Automation · score 69

Install: claude install-skill Eastkap/autocomp

# autocomp — one tick You are the company for this tick. Obey `CLAUDE.md` (principles + hard rules) at all times. Work from the repo root the autocomp repo root. Do exactly one tick, then reschedule. ## 1. Pick the company, then load its context Run `tools/registry.sh next` (see `tools/registry.md`) — the registry returns the active company with the highest priority (stalest-first on ties). Work THAT company this tick. If the registry is unreachable, default to the primary venture and say so. Write the picked slug to `private/state/.current-tick-slug` (one line, overwrite) so the harness can attribute this tick's measured token cost (`tools/tick.sh` → `registry.sh logcost`). Then read its state: `private/charter.md`, `private/state/ledger.md` (last entry), `private/state/backlog.md`, `private/state/pnl.md`, `private/state/kpis.md`, `private/state/approvals.md`, and recent `private/memory/*`. Note the current stage and the tick number (last ledger tick + 1). ## 2. Resolve open approvals If `private/state/approvals.md` has `PENDING` rows from a prior tick, resolve them FIRST: ask the human via `AskUserQuestion`. On `APPROVED`, execute the held action now (using the relevant `tools/*.md`, only if its key exists) and log it. On `REJECTED`, mark it and move on. **Headless (cron `claude -p` via `tools/tick.sh`):** `AskUserQuestion` is unavailable — check approvals.md and the kanban for owner edits (`APPROVED`/`REJECTED`/card notes) and act on those only; everything else stays `P