メニュー
Use when joining a new company, taking over legacy products, or proposing strategies that were previously attempted to avoid repeating past mistakes
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | historian-decision-model |
| description | Use when joining a new company, taking over legacy products, or proposing strategies that were previously attempted to avoid repeating past mistakes |
A process for improving decision quality by excavating and analyzing organization history to understand the context of past failures before charting a new path.
Core principle: Learn from mistakes you didn't personally live through.
┌─────────────────────────────────────────────────────────────────┐
│ 1. EXCAVATE │
│ Research past decisions and outcomes │
│ Talk to long-tenured employees │
├─────────────────────────────────────────────────────────────────┤
│ 2. CONTEXTUALIZE │
│ Analyze "Why" decisions were made at that time │
│ What was the environment/constraints? │
├─────────────────────────────────────────────────────────────────┤
│ 3. IDENTIFY BAGGAGE │
│ Map internal resistance and emotional blockers │
│ "We tried that before" = baggage signal │
├─────────────────────────────────────────────────────────────────┤
│ 4. FORMULATE HYPOTHESIS │
│ Create strategy informed by historical context │
│ Address what was different then vs. now │
├─────────────────────────────────────────────────────────────────┤
│ 5. DECIDE & ITERATE │
│ Commit to direction without needing 100% certainty │
│ Learn from results │
└─────────────────────────────────────────────────────────────────┘
| Principle | Description |
|---|---|
| Excavate actively | Don't assume you know the past |
| Context matters | Same idea can fail or succeed based on timing |
| Baggage is real | Emotional weight blocks rational evaluation |
| Commit anyway | History informs but doesn't dictate |
Source: Anneka Gupta (Rubrik CPO) via Lenny's Podcast
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.