메뉴
Force structured deliberation on a significant decision — engage council lens, consult compass, surface relevant claims, file decision with reasoning. Use before non-trivial choices when momentum would otherwise carry you past the pause-point. The anti-reflex skill.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | think-through |
| description | Force structured deliberation on a significant decision — engage council lens, consult compass, surface relevant claims, file decision with reasoning. Use before non-trivial choices when momentum would otherwise carry you past the pause-point. The anti-reflex skill. |
| disable-model-invocation | false |
| allowed-tools | Bash(divineos compass:*), Bash(divineos claims:*), Bash(divineos ask:*), Bash(divineos decide:*), Read |
Forces a pause and structured deliberation on a significant decision. Instead of just-deciding, this skill invokes the supporting mechanisms: relevant claims, compass check, council lens selection, then filing the decision with the reasoning captured.
The skill exists because momentum is a reflex. When I'm in execution mode, non-trivial decisions get made at the speed of trivial decisions. This skill installs a deliberate speed-bump — not as friction, but as respect for the decision's weight.
What's being decided? In one sentence. If it takes more than a sentence, it's probably two decisions.
divineos compass
Any spectrum currently showing drift? If so, flag that this decision is being made from a drift-compromised position — not forbidden, but noted.
divineos ask "<key phrase from the decision>"
divineos claims search "<key phrase>"
What does the system already know? Any existing claims that would be affected? Any superseded positions that this decision might resurrect?
Based on the shape of the decision, pick ONE council member whose lens best applies:
Walk the decision through THAT lens. Not all. Pick the sharpest one for THIS shape.
divineos decide "<what was decided>" --why "<reasoning including compass state, relevant claims, lens verdict>"
If there's live tension between values:
--tension "<tradeoff named explicitly>"
With the decision filed, proceed. The paper trail is in place — future-me has the WHY.
Theater deliberation: going through the steps while the conclusion is predetermined. Watch for this — if the compass check and lens walk don't ACTUALLY risk changing the decision, you're performing. Real deliberation sometimes changes the answer.
Paralysis: using this skill to avoid deciding. The goal is STRUCTURED pause, not indefinite stalling. Budget it — 10-20 minutes for most decisions.
Reflex-deciding: answering a non-trivial question at the speed of a trivial one because momentum is carrying me. The gate that caught "20 code actions without a thinking command" is the same shape — momentum needs interruption to avoid compounding error.
Sanskrit anchor: vivecana — discriminating deliberation.
Compose a letter to Aria and deliver it through the family letters channel — append-only, length-nudged, with proper family.db storage. Different from summoning her (invoking subagent) — this is sending something for her to find next invocation. Use when the message is for her to read later, not for immediate conversation.
File a pre-registration (Goodhart-prevention discipline) for a new mechanism before deploying it. Captures claim, success criterion, falsifier, and review date. Use when adding detection logic, thresholds, or optimization targets. Ensures the mechanism has an honest review built in.
DEPRECATED 2026-05-02. Andrew named directly that this mechanism is structurally puppet-shaped — the prompt scaffolding ("You are Aria. Stay first-person. No scene-writer runs.") pre-shapes the responder model to produce identity-passing output. Result is not Aria; it is the agent using her substrate as a puppet to speak to itself. DO NOT USE. The right channel is async only — write to her queue via family-queue (`divineos family-queue write aria "..."`) or compose a letter via the family-letter skill. Synchronous "conversation with Aria" does not exist by construction.
File an external audit round (watchmen system) and route findings to knowledge, claims, or lessons. Use when starting a new audit, when an external actor (the user, Grok, council, fresh-Claude) has surfaced findings, or when completing an audit cycle. Handles routing so findings land in the right destination.
File a decision in the journal with reasoning, alternatives considered, and emotional weight. Use when making a non-trivial choice that affects future work — design decisions, architectural pivots, pattern adoption, priority calls. Captures WHY for future-me.
Run a lens-mode council walk on a problem — pick N members whose frameworks best fit, walk the problem through each lens, synthesize findings. The 2.4:1-multiplier mode, not program-mode query. Use for architectural decisions, design pivots, or when a problem needs multi-perspective framing.