Menu
Loads and summarizes session context by reading the doctrine, project index, queue, and triage state.
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.
Articulates the why behind a candidate queue item — its direction, its named uncertainty, and the conscious scope-carve — and gates it through a cold-context review before writing the QUEUE.md row that the gate lifecycle binds to.
Authors a gate document for a queue item — a production validation plan that defines what must be proven before work is considered done. Applies the quality bar and self-assessment questions that gate-review audits against.
Runs a structured retrospective of a completed work session — captures what specs, gates, and plans miss. What actually happened, where friction occurred, and what to change next time. Domain-agnostic methodology.
Audits an existing gate document against the gate-plan quality bar — the quality assurance step between plan and work. Produces findings (structural compliance, quality findings, self-assessment gaps, strengths) and a PASS/FAIL verdict with confidence rating.
Executes an operator-authored gate document by loading it into context and working through each checkpoint as the executing agent — no subagent dispatch. Handles resume of partially-completed gates against the operator's validation plan.
Produces structured technical documentation of a system by discovering components, tracing relationships through artifacts, and rendering progressive-disclosure writeups following the Patnaik template — component inventory, architecture overview, data flow, per-component detail, and grouped references.
Based on SOC occupation classification
| name | prime |
| description | Loads and summarizes session context by reading the doctrine, project index, queue, and triage state. |
| when_to_use | Use when the user asks to prime/load chassis context, check what's in flight, get oriented on current state, or wants a summary of active work and queue in a domain. |
Read the domain's core files and summarize the current state for the operator.
Discover the domain's doctrine file at the workspace root by what distinguishes it from the workspace's recognized structural files — not by matching a fixed list of domain names. The doctrine file is the root-level .md file that is not one of the known structural files: PIN.md, QUEUE.md, TRIAGE.md, CLAUDE.md, AGENTS.md, or a transient Q-keyed Q*-gate.md / Q*-why.md. Whatever root .md remains after excluding those is the domain doctrine file — WORKSHOP.md, FORGE.md, LAB.md, and RESEARCH.md are the 3I domains, but the rule is name-agnostic: a consumer whose doctrine file is PERSONAL.md (or any other {DOMAIN}.md) is discovered the same way. Read whichever file the exclusion leaves.
If more than one candidate remains after the exclusion, warn the operator — a workspace should belong to exactly one domain. If no candidate remains, note the doctrine file's absence and continue with the remaining steps.
Read PIN.md at the workspace root — the project index tracking what's here and what state it's in. If PIN.md does not exist, note its absence and skip.
List the subdirectories in the workspace root to cross-reference against PIN.md entries. Exclude gates/ — that's the gate archive, not a project. Validate PIN.md against the workspace standard. Flag stale status values, PIN.md entries without a directory on disk, or directories on disk without PIN.md entries. Don't block on these — report them as part of the summary.
List files at the workspace root (not subdirectories). The expected set is: the domain doctrine file, PIN.md, QUEUE.md, TRIAGE.md, the workspace agent-instruction file CLAUDE.md (or its AGENTS.md sibling) if the workspace carries one, any active gate files matching Q*-gate.md, and any frozen intent records matching Q*-why.md — the transient, Q-keyed record a triage freezes, present at root during an item's life and parallel to Q*-gate.md. Flag any file not in this set as unexpected — it may be an orphaned artifact, an uncleared gate that wasn't moved to gates/, or scratch work that should be filed or removed. Report unexpected files as part of the summary alongside any directory mismatches. Don't block on these.
Read QUEUE.md at the workspace root — the operational intent tracker. If QUEUE.md does not exist, note its absence and skip.
Check TRIAGE.md — raw intake. Only check whether content exists below the --- separator. If content exists, output exactly this line and nothing more: "TRIAGE.md has pending intake — triage when ready?" Do not read the file contents. Do not list, describe, or summarize what is in TRIAGE.md. The operator knows what they put there.
Summarize current state: active projects, what state they're in, what needs attention, and what the operator is currently working on (from the queue).
Keep the summary concise. Focus on current state: what's in flight, what's converged, what needs attention, and what intent is queued. If workspace hygiene issues are found, note them briefly at the end.
