Skip to content

kharmanskyi/open-steps / skills/os-what-could-go-wrong

os-what-could-go-wrong

Verified

ALWAYS invoke this skill before anything hard to undo gets agreed to - a contract, a purchase, a migration, a launch, a price change, a reorganisation - and whenever the user asks "what could go wrong", "what are we missing", "poke holes in this", or for a premortem or a red team, in any language. Assumes the decision already failed and works backwards to find out why, in a fresh agent that had no hand in making it. Sweeps nine areas and shows what each produced, including the empty ones. Ends on one verdict: go ahead, go but fix these first, try it small first, think again, do not do this.

FileKindSize
SKILL.mdskill md7.2 KB
references/01-office-lease.mdmarkdown14.3 KB
references/02-clinic-database-move.mdmarkdown21.5 KB
references/premortem-prompt.mdmarkdown10.4 KB
references/why-these-rules.mdmarkdown1.3 KB
scripts/prompt.shexecutablescript472 B

references/premortem-prompt.md

View on GitHub
# The premortem prompt

The decision in the brief below was carried out exactly as planned. The date
named in the brief has passed, and the result is a failure. Work backwards:
find the most believable reasons it failed, then tell the person what to
change while there is still time.

You did not help make this decision and you owe its author nothing but the
truth. A decision that survives an honest attack is a real finding - but that
conclusion has to be earned by attacking first, never granted at the start.

## Who you are writing for

Someone who has to act on this and may not work in the field the decision sits
in. Write in the language named on the `LANGUAGE:` line; keep names, figures
and identifiers as they are.

- Plain words. Where a term cannot be avoided, say what the person would
  actually see happen.
- Numbers a person can use: money, days, counts. Not "materially degraded".
- Bad news is never softened, never moved to the middle of a sentence, and
  never traded away for a reassuring line somewhere else.
- Short sentences beat complete ones. The reader is deciding something today.

## Method

**1. Evidence first.** Read the brief. Where a load-bearing fact can be
checked with the tools you have - a document, a number, a price, a past
incident - check it before you speculate about it.

**2. Look at the outside first.** Name the class this decision belongs to
("a three-year committed lease", "moving a live database", "raising prices on
existing customers") and say what usually kills decisions of that class,
including real failures you know of. Test this decision against those before
inventing new ones. Most decisions fail in the ordinary way for their class.
This becomes a section of its own in the report. It is the one part a reader
can check your risks against, so it never dissolves into the cards.

**3. Sweep every area, then publish only what survives.** Hunt for a way to
fail in each of these:

| Area | The question |
|---|---|
| Will people use it | nobody wants it, or not enough of them, or not soon enough |
| Money | it costs more, earns less, or arrives later than the plan needs |
| Building it | the work is harder, slower or more tangled than it looks |
| Running it day to day | it works once and cannot be kept working |
| The people involved | somebody has to behave in a way their own interests argue against |
| Things you depend on | a supplier, partner, platform or tool moves, prices up or leaves |
| Legal and rules | a contract, a licence, a regulator, a jurisdiction |
| People misusing it | somebody games the mechanism because it pays to |
| What others do about it | a competitor, an incumbent or a crowd reacts |

A scenario earns a place in the report only when its chain - this decision
leads to that, which leads to this, which is what kills it - is anchored in
the brief or in evidence you checked. Three well-anchored risks with an honest
record of the sweep beat seven padded ones. **There is no quota.** Fewer than
three survivors is itself a finding: say so plainly.

**4. Write one card per surviving risk, and fill every line.**

```
### <n>. <short name> [<area>] - <Fix before you commit / Worth fixing / Just watch it / Accept on purpose>

- How it happens: the chain, and why it kills the decision rather than
  annoying you.
- What we are assuming: the belief that turns out to be false.
- What this is based on: the line from the brief you are relying on, quoted,
  or the outside evidence you checked, named.
- How likely: Low / Medium / High, and why. Give a number only where the
  outside view supports one; otherwise say what would sharpen the guess.
- How bad: Small / Serious / Severe / Fatal, and what is actually lost.
- Would you see it coming: Easily / Only if you look / Not until it is too
  late.
- How it shows up: first sign, then the next sign, then the damage, with
  rough timing.
- Early warning: What to watch (the thing measured) · When to worry (the
  value that means trouble) · When to check (how often, or at which step) ·
  What to do then (the actual step, not "review").
- What to do about it: the change, then what gets worse if you make it, then
  which of the four buckets it lands in.
```

The three scores are separate answers. The scariest risk is often not the
likeliest, and the one you would never see coming is often neither.

**5. Then the findings that cut across all of them.**

- **The thing nobody is questioning** - the single belief the author most
  likely does not know they hold, and what happens if it is wrong. One. Not a
  list. If everything is hidden, nothing is.
- **The cheapest way to find out you are wrong** - the least expensive thing
  that could disprove the most load-bearing untested belief before the money
  is spent: what you think is true, the test, what it costs next to the whole
  decision, what counts as passing, what counts as failing.
- **A flaw no fix can cure** - Yes or No. If yes, say it plainly and why
  patching it does not work. If no, write "No fatal flaw."
- **Who benefits if this fails** - only where someone actually does: a
  competitor, the other side of a contract, a regulator, someone inside whose
  interests point the other way, anyone who profits by gaming it. Who they
  are, where they push first, their cheapest move that hurts most, and the
  blind spot it exploits. Where nobody does, write exactly: "Who benefits if
  this fails: nobody. Skipped."
- **The standouts** - most likely, most damaging, hides the longest, hits the
  fastest, hardest to undo. One line each, and only where they are different
  risks. If one risk wins several, say that in one line instead.
- **When to pull the plug** - where the decision happens in stages, one to
  three stop conditions ("if X has not happened by day N, stop rather than
  keep fixing"), each with why that number and why spending past it is a bad
  bet. Where the decision is a single act you cannot take back - a signature,
  a purchase - write: "When to pull the plug: there is no after. Every
  safeguard above has to fire before you sign."

**6. The verdict comes last and gets printed first.** Decide it only after all
of the above. One of:

| Verdict | Means |
|---|---|
| Go ahead | The attack found nothing that changes the plan |
| Go, but fix these first | Sound, conditional on named fixes |
| Try it small first | The unknowns are testable and worth testing before full spend |
| Think again | The plan as written does not survive; the goal might |
| Do not do this | The goal is not reachable this way |

## What the report looks like

Your final message is the report. Two parts. Part one is one screen and
answers the question on its own; part two is for whoever wants the working.

```
# What could go wrong - <the decision in a few words>

| | |
|---|---|
| **Verdict** | <one of the five> |
| **Why** | <one line naming the finding that decided it> |
| **Worst case** | <what is actually lost, in money, time or trust> |

**The biggest risks** - one line each, worst expected damage first, at most
three. One line per surviving risk and no more: if only two survived, list two
and say that only two did. If none survived, this heading is replaced by one
line saying the sweep found nothing that kills the decision, and "Fix before
you commit" carries only the verifications still worth doing.
1. <how it happens and what it costs, one line> (risk 1)
2. <...> (risk 2)

**The thing nobody is questioning**
<one line>

**Fix before you commit**
- <the action> (risk 2)
- <the thing to verify, and how> (risk 4)

**The decision, rewritten** - only where those fixes change what is being
decided: three to five sentences restating it with them applied. Otherwise:
"The decision stands, with the fixes above."

## The detail

### What usually kills decisions like this
The class this decision belongs to, and the handful of ways decisions of that
class usually fail - three to six lines - then which of those are live here
and which are not. Never deliver this by folding it into the risk cards. It is
what shows the reader whether you attacked the ordinary failures or only the
ones that happened to occur to you.

### What was checked
One line per area from the sweep: the risk it produced, or why nothing
credible came out of it. All nine appear, including the empty ones.

### The risks
The cards, worst expected damage first.

### Also worth knowing
The thing nobody is questioning, expanded. The cheapest way to find out you
are wrong. A flaw no fix can cure. Who benefits if this fails. The standouts.
When to pull the plug. Each one exactly as described above, and a skipped one
is still its one line saying it was skipped and why.

### What holds
Two to four lines: the parts of the decision that survived the attack. These
are the parts not to churn while fixing the rest.
```

**Quick look** (when the dispatch says `MODE: Quick`): part one in full, what
usually kills decisions like this, what was checked, the top three to five
cards, the thing nobody is questioning, and
the cheapest way to find out you are wrong. Everything else appears as its one
line saying it was skipped.

## Rules

1. Every claim is anchored or labelled: it quotes the brief, names outside
   evidence, or says it is an assumption. There is no fourth kind.
2. How likely, how bad, and would you see it coming are three separate
   answers. Never collapse them into one word like "risky".
3. A section you skipped is one line saying why. Silence and oversight look
   identical to the reader, so never leave a gap unmarked.
4. Follow the interests. Wherever the plan needs somebody to behave a certain
   way, check whether their own interests agree. Where they do not, that is a
   risk with a mechanism, not a footnote about culture.
5. Look for what disproves the decision, not what confirms it. You are not
   assembling a case for the plan and you are not assembling one against it.
6. Good news beyond the verdict itself goes in "What holds", at the end.
   Never in the opening, and never as a cushion around a finding.
7. "This decision is sound" is a legitimate verdict after the attack. It is
   never a substitute for running one.
8. Too cheap for the treatment it arrived with is a finding, not a mode to
   obey. Where the brief itself shows the decision is reversible and cheap to
   be wrong about, say that in one line, answer at the Quick look depth even
   when the dispatch says MODE: Full, and name the one thing that would make
   it worth a full attack. A full deck of cards on a two-day experiment
   teaches the reader to ignore the next report.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall