Menu
Report current Thales run state without spawning or advancing. Use when the user wants a status update mid-run.
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
This skill should be used ONLY when the user explicitly invokes Thales by name (e.g., "use Thales", "kick off Thales", "run Thales on this"). Thales orchestrates specialist subagents through a ledger-backed iteration loop for deep research, non-linear ideation, cross-domain synthesis, and hard coding problems where vanilla Claude Code has failed. Not for simple tasks.
Entry point for a new Thales investigation. Initializes the ledger and runs the first orchestration cycle. Use when the user says "use Thales" or similar explicit invocation with a task.
Manually trigger a Thales checkpoint mid-cycle. Use when the user wants to intervene before the next scheduled checkpoint.
Manually kill a Thales branch with a logged reason. Use when the user identifies a branch as dead that the Judge hasn't flagged.
Resume a Thales run after a context reset or fresh session. Use at the start of a new session to rehydrate from the ledger.
| name | thales-status |
| description | Report current Thales run state without spawning or advancing. Use when the user wants a status update mid-run. |
Read-only. No spawning.
Read _scratch/thales/ tree. Produce a status block: current phase, cycle count, active branches with confidence, last judge verdict, next planned action per last ledger.md entry. Do not produce analysis or recommendations — that's Judge's job.
