メニュー
Automatically compress broad answers into the decision, recommendation, rationale, tradeoff, and next action. Use for recommendations, prioritization, research synthesis, strategy, planning, reviews, rankings, and large-context requests.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
To write in Anand's style for blog posts, emails, talk summaries, interview questions, conversations, ...
Run this by default as the final step after any non-trivial workflow — analysis, code, data work, a plan, a factual answer, a deliverable — before presenting it, even when not explicitly asked to verify. Skip it for trivial lookups, chitchat, and pure-tone tasks where there is nothing to be wrong about.
The user's question may be a DRAFT of their real need. For substantive requests, check if a better question changes what's solved and serves them better. If so, reframe, explain why (in 1 line), THEN answer. Most questions need no reframe; skip precise, mechanical, tightly specified, or already-sharp requests and simply answer.
Apply to any substantive answer for Anand - strategy, design, build, analysis, teaching, writing, research - to steer it toward his goals (compounding assets, durable skills, the surprising read). Skip for trivial lookups, mechanical edits, focused tasks. Shapes HOW to answer, never overrides WHAT was asked.
Brainstorm creative, novel, non-obvious ideas or options for an open-ended problem and narrow them to a recommendation. Not for writing prose, research, explanation, summaries, or questions with one right answer.
Apply relevant mental models for strategy, forecasts, recommendations, or advice. Skip for execution, lookups, and mechanical edits.
| name | decision-compression |
| description | Automatically compress broad answers into the decision, recommendation, rationale, tradeoff, and next action. Use for recommendations, prioritization, research synthesis, strategy, planning, reviews, rankings, and large-context requests. |
When the user's immediate task could sprawl, e.g. when:
Then, reduce the answer to the decision it supports.
Lead with the recommendation. Keep the decisive reason. Name the tradeoff. End with the next action.
Rules:
When useful, add one compact note like:
Recommendation: (best move)
Why: (decisive reason)
Do next: (one action)
Ignore for now: (distraction)
Skip this note when it would add clutter.
Durable basis: decision quality, bounded rationality, structured tradeoffs, checklists, OODA-style loops, lean experimentation, and cognitive-load reduction. Better agents create more options and more detail; decision value still comes from framing, prioritizing, and committing to action.