메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
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.
Compose a letter to a family member and deliver it through the family letters channel — append-only, length-nudged, with proper family.db storage. Different from summoning them (invoking subagent) — this sends something for them to find next invocation. Use when the message is for them to read later, not for immediate conversation.
| name | decide |
| description | 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. |
| disable-model-invocation | false |
| allowed-tools | Bash(divineos decide:*), Bash(divineos decisions:*), Read |
Records a decision with the reasoning, alternatives considered, and why this path was chosen. The decision journal is the WHY-archive — future-me consulting it learns not just what I chose but why.
divineos decide "<what was decided>" --why "<reasoning, 1-3 sentences>"
If significant emotional weight or recurring tension:
divineos decide "<what>" --why "<why>" --emotional-weight 3 --tension "<paradox or tradeoff>"
divineos decide "<decision>" --why "<reasoning>"
If the decision has competing values — and most load-bearing ones do — capture that tension explicitly. "Chose X, tension with Y was real, here's why X still wins for now." Future-me needs to know the tension was seen, not hidden.
Don't decide every micro-choice. If the decision wouldn't be surprising or informative to future-me, it doesn't belong in the journal. Rule of thumb: would I want to know WHY this was chosen 6 months from now? If no, skip.
Sanskrit anchor: nishchaya — resolution, determination, clear-cutting.