القائمة
Use before launching products or signing contracts, when needing to combat sunk cost fallacy, or when standard pre-mortems fail to change behavior
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when designing AI agent products, defining roadmaps for agentic workflows, or evaluating how to evolve AI from passive tool to proactive partner in software development
Shift from rigid roles (PM, Designer, Engineer) towards a model where individuals use AI to bridge skill gaps, enabling smaller and flatter teams. Use in early-stage startups or innovation units where speed is critical.
Use when designing AI agents or chatbots, when raw model outputs feel like a black box, or when building natural language interfaces that need structure and trust
Use when building AI-powered products or agents, when raw model intelligence isn't enough to solve user problems, or when designing the architecture for agentic workflows
View yourself as an entity with infinite dimensions rather than a single good/bad identity. Strengths and weaknesses are often the same trait in different contexts. Use during performance reviews or when receiving tough feedback.
Review your calendar, color-code activities by energy impact (Green/Red), and systematically delegate draining tasks to maximize time in your Zone of Genius.
| name | pre-mortem-kill-criteria |
| description | Use before launching products or signing contracts, when needing to combat sunk cost fallacy, or when standard pre-mortems fail to change behavior |
An enhancement to the standard pre-mortem that moves beyond simply imagining failure to establishing pre-committed actions based on specific negative signals.
Core principle: Thinking about failure isn't enough; you must commit to actions BEFORE you see the signals.
┌─────────────────────────────────────────────────────────────────┐
│ 1. MENTAL TIME TRAVEL │
│ Fast forward: Imagine the project has FAILED │
├─────────────────────────────────────────────────────────────────┤
│ 2. SIGNAL IDENTIFICATION │
│ "What early clues indicated the failure?" │
│ List specific, observable signals │
├─────────────────────────────────────────────────────────────────┤
│ 3. DEFINE KILL CRITERIA │
│ Convert clues into measurable thresholds │
│ Example: "CPA > $50" or "Customer won't demo" │
├─────────────────────────────────────────────────────────────────┤
│ 4. PRE-COMMITMENT │
│ Establish rule: "If [Criteria] occurs, we [Kill/Pivot]" │
│ Write it down and share with team │
├─────────────────────────────────────────────────────────────────┤
│ 5. ACTIVE MONITORING │
│ Scan for criteria during execution │
│ Act immediately when triggered │
└─────────────────────────────────────────────────────────────────┘
| Principle | Description |
|---|---|
| Pre-commit | Lock in actions before rationalization kicks in |
| Signal focus | Identify correlates of failure, not just the failure itself |
| Prospective waste | Think about future waste, not sunk cost |
| Automatic triggers | When criteria hit, action is mandatory |
Source: Annie Duke (First Round Capital, WSOP Champion) via Lenny's Podcast