agentleFS
takayoshitoyoda05takayoshitoyoda05/claude-ml-template/.claude/skills/pre-mortem/SKILL.md

pre-mortem

Skill1 starsChanged 2 months agoMITView on GitHub

将来どこが壊れるかを予測するとき、「壊れそうな箇所を洗い出して」「pre-mortemして」と言われたときに必ず使う。

31 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use brainstorm-experiments-existing, prioritize-assumptions and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • skytiger6724Skill

    brainstorm-experiments-existing

    Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.

    Also in 7 projects that use this

  • skytiger6724Skill

    prioritize-assumptions

    Prioritize assumptions using an Impact × Risk matrix and suggest experiments for each. Use when triaging a list of assumptions, deciding what to test first, or applying the assumption prioritization canvas.

    Also in 7 projects that use this

  • 45ckSkill

    pestle-analysis

    Also in 7 projects that use this

  • About-IntelligenceSkill

    positioning-ideas

    Brainstorm product positioning ideas differentiated from competitors.

    Also in 7 projects that use this

  • About-IntelligenceSkill

    product-name

    Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience.

    Also in 6 projects that use this

  • +6 more from skytiger6724
  • +1 more from About-Intelligence

The file

Files
SKILL.md

Pre-mortem 分析

動いているコードを見て、まだ起きていないバグの事後分析レポートを書く。 「今バグがあるか」ではなく「将来の編集で壊れやすい箇所はどこか」を探す。

進め方

  1. 作業スコープ直下に CONTEXT.md があれば先に読む。
  2. 対象のファイル・モジュールを指定される(無ければ作業スコープ全体)。
  3. 各関数・クラスについて、以下の観点で脆さを分析する。

分析観点(1つずつ順に確認する。複数を同時に浅く見ない)

観点具体的に見ること
暗黙の仮定入力の形状・型・値域について、コードが暗黙に仮定していることは何か
状態依存グローバル変数・クラス変数・外部ファイルの状態に依存しているか
順序依存関数の呼び出し順序を変えると壊れるか
数値の脆さ除算、log、sqrt 等でゼロやNaN/Infが入ったときに壊れるか
次元・shapeテンソルの次元やshapeの仮定が、上流の変更で崩れる可能性はあるか
外部依存ライブラリのバージョンアップで挙動が変わる箇所はあるか

出力形式

各脆い箇所について、過去形で書く(「将来こう壊れた」という仮想の事後報告)。

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.