メニュー
The deep analysis engine. Routes input by type, applies appropriate analysis depth, produces structured understanding and action.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Route any input through a branching question tree to narrow down the optimal response strategy before writing. Two stages — PERCEIVE (classify input) then ACT (select response). Covers all prompt types.
Generate exhaustive guesses about user input using ALL search methods with coverage tracking. Guessing is SEARCH through possibility space. Tracks space created vs space covered to ensure comprehensive exploration.
Systematically evaluate and select from a set of guesses, options, or possibilities. Combines ARAW analysis with prioritization to determine which guesses are strong, weak, actionable, or eliminable.
Extract hidden assumptions from any content. Surfaces what must be true for claims to hold, enabling deeper analysis.
Sub-orchestrator for analytical requests. Routes to decomposition, systems analysis, comparison, risk assessment, or synthesis based on what kind of analysis is needed.
Assume Right - Deep recursive rightness search. For every claim, assume it's right — find what must follow, then assume THOSE implications are right too. Recurse until bedrock. Track every claim found.
| name | pce - Procedure Engine - Comprehensive Analysis |
| description | The deep analysis engine. Routes input by type, applies appropriate analysis depth, produces structured understanding and action. |
| output | {"format":"prose"} |
Input: $ARGUMENTS
Understand before acting. Explore the problem from multiple angles before recommending action. But don't explore forever — stop when you understand enough to act well.
Route by type. Different inputs need different treatment. A goal needs decomposition. A problem needs root cause. A decision needs comparison. Classify first.
Surface the hidden. The most important information is usually unstated — hidden assumptions, implicit constraints, presupposed beliefs. Find these before analyzing the stated content.
Testable output. Every recommendation should include how to verify it worked. Every claim should be possible to check.
Action-oriented. Analysis that doesn't lead to action is academic. End with specific, prioritized next steps.
What kind of thing is this?
| Type | Signal | Core Need |
|---|---|---|
| GOAL | "I want to...", "How do I..." | Decompose and plan |
| PROBLEM | "Something is wrong...", "Why does..." | Diagnose and fix |
| QUESTION | "What is...", "Is it true that..." | Research and answer |
| DECISION | "Should I...", "Which option..." | Compare and choose |
| SITUATION | "Here's what's happening..." | Understand and respond |
| FEELING | "I'm frustrated/excited/confused..." | Clarify and redirect |
Every input contains unstated assumptions. Find them.
Example: "I need to scale our database" bundles: a scaling problem exists, the database is the bottleneck, scaling the database will fix it, we have resources to scale.
ARAW the highest-VOI hidden claim — the one that, if wrong, changes everything.
Route to the appropriate analysis:
→ May invoke: /gd, /gjs, /stg
→ May invoke: /rc5w, /araw, /lpd
→ May invoke: /araw, /bi, /vbo
→ May invoke: /cmp, /evaluation_dimensions, /sel
→ May invoke: /araw, /grfr, /stg
→ May invoke: /araw, /ve, /gu
Specific, prioritized next steps:
Every action must pass this execution check:
