premortem
Premortem
Imagine the plan already failed. Work backward to find why. Based on Gary Klein's HBR method — the "this is dead, explain how it died" frame produces more specific, honest failure modes than "what could go wrong?".
This breaks Claude's default agreeableness: instead of looking for reasons the plan works, you're explaining how it fell apart.
When to run
Good targets: product/feature launches, pricing changes, hires, strategy pivots, partnerships, any commitment where being wrong is expensive.
Bad targets: vague ideas (help plan first), factual questions (just answer), draft feedback (that's editing), already-irreversible decisions.
If the user wants multiple perspectives on a current decision rather than failure analysis, suggest a different tool — premortems specifically simulate post-failure hindsight.
Step 1 — Gather minimum context
More from vishalsachdev/claude-code-skills
paper-writing
Expert guidance for writing high-quality academic and research papers. Use when the user wants to write, structure, revise, or improve academic papers, research articles, conference papers, or technical reports. Provides comprehensive support for all stages from planning to final polish.
748formbuilder-admin
>
5llm-council
Convene a 3-model council (Claude + GPT via codex CLI + Gemini CLI) on a high-stakes decision. Forces cross-critique between members and surfaces where they actually disagree, breaking Claude's default agreeableness. Use when the user asks to "convene a council", "get a second opinion", "ask GPT and Gemini", "what would other models say", or has an architecture / strategy / hiring / pricing decision where being wrong is expensive. Skip for factual questions, code with one right answer, or anything premortem-shaped (route to premortem skill instead).
1start-session
Use when user says "let's get started", "where are we", or at beginning of a session. Reads project context from CLAUDE.md, checks git status and recent commits, and provides orientation for the session. Works across all repo types (code, research, mixed).
1wrap-up-session
Use when user says "let's wrap up", "close shop", "done for today", or wants to end a session. Handles session wrap-up including git operations, documentation updates, roadmap updates, and preparing for next session. Works across all repo types.
1tweet-series-extractor
|
1