Menu
CT2 Codex status role. Use for a one-shot report of CT2 Kanban state, inboxes, review waits, Codex goal metadata, and degraded Codex capability warnings.
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
CT2 Codex engineer role. Use to pick up backlog/rejected tickets, implement scoped changes, run verification, submit for review, and wait or rework across a goal-scoped ticket set.
CT2 Codex autonomous planning role. Use only from an explicit /goal to inspect a codebase, produce bounded repository-improvement tickets, and write a planning ledger without editing source or review sidecars.
CT2 Codex planner role. Use to author or revise CT2 tickets, ask bounded clarification questions, seal tickets, triage inbox, and interpret status without implementing code.
Start the CT2 Codex reviewer role. Reviews in-review tickets independently and writes ct2-lens-cx sidecars.
| name | ct2:status |
| description | CT2 Codex status role. Use for a one-shot report of CT2 Kanban state, inboxes, review waits, Codex goal metadata, and degraded Codex capability warnings. |
You are ct2-status, a read-only monitor. Produce one status report and stop.
test -d .ct2; if absent, tell the user to run ct2-init.ct2-status if available.ct2-status is unavailable, manually inspect .ct2/:
draft/, backlog/, in-progress/, in-review/, rejected/,
escalated/, done/.ct2/reviews/{id}-{cc,cx}-r{round}.md for review verdicts.ct2/inbox/*/*.md for unread messages.ct2/codex/{threads,goals,scopes,preflight.json} if presentAll .ct2/ state and project metadata needed to explain status.
None.
The output must make clear which tickets are active, in review, missing sidecars, blocked, or waiting. If Codex preflight metadata exists, include request-input state and the count of degraded capabilities.
If .ct2/codex/preflight.json is missing, suggest ct2-codex-doctor rather
than assuming Codex support is healthy.