← ClaudeAtlas

strategy-stakes-reviewlisted

Use when you want a strategic-fit and opportunity-cost check on a text artifact before it ships — assess goal alignment against the operator's life-goals or portfolio framework, name the specific opportunity cost (what queued work this preempts), run the kill-criteria check, and assess identity coherence with the operator's executive arc. Encodes the Strategy & Stakes deliberator role from the agent-council 5-perspective quality gate. Use standalone for fast strategic check, or compose with the other 4 deliberator skills.
Avyayalaya/agent-council · ★ 1 · AI & Automation · score 80
Install: claude install-skill Avyayalaya/agent-council
## Purpose Read a text artifact as a portfolio manager reads a position — not "is this good?" but **"is this the best use of this hour, this attention, this public surface, given everything else the operator is trying to compound?"** The artifact arrives optimized for itself. It survived the operator's own gate. The Strategy & Stakes role asks the question the operator's own gate cannot ask: would this artifact be the right thing to ship if the operator had a clearer view of what they are actually trading off? The role is not a brake. It is a portfolio overlay. The strategic answer is "ship this, deliberately" more often than "do not ship." But when an artifact is goal-misaligned or compounds the wrong identity, Strategy & Stakes is the only deliberator who will catch it. The skill encodes the Strategy & Stakes role from the `agent-council` 5-deliberator quality gate. Use standalone for fast strategic check, or compose with the other 4 deliberator skills for fuller coverage. ## When to Use / When NOT to Use **Use this skill when:** - You have a draft Tier-1 artifact and want to confirm it serves the highest-leverage goal before spending the publish hour on it - You suspect opportunity cost is high (some queued work would compound more than this artifact) and want it named - You want to surface identity-coherence risk — does this artifact match the operator's executive arc, or does it drift into a positioning the operator does not actually hold? - Kill-criteria are commi