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/01-office-lease.md

View on GitHub
# Example 1 - a three-year office lease

Source: an invented decision, written for this example. No real company,
nothing confidential, no third-party material. Both halves are real agent
output on the same facts: the BEFORE is what a general-purpose agent answered
when the decision was put to it with no skill in play, the AFTER is what this
skill produced. Both are abridged wherever you see an ellipsis, and punctuation
is normalised to this repository's style; no wording is changed.

Kept because the BEFORE is good. That is the point of it. It is not a lazy
answer that a better prompt would fix - it is a careful, well-informed answer
that the person still cannot act on or audit.

## BEFORE - the same decision, no skill (~90 lines)

> ## The short version
>
> You're committing three years and roughly **$1.7-2.0M all-in**, backed by a
> **director's personal assets**, to test a hypothesis you cannot measure for
> 12-18 months, with **7.7 months of cash in the bank**, in a market that's
> discounting 15-20%, under a three-week deadline set by the counterparty.
>
> Almost every one of those factors independently argues for slowing down...
>
> *(Working from your numbers only. Two assumptions worth confirming: that the
> $310k burn excludes the office, and that $28k is net of service charge...)*
>
> ## 1. The cost model is missing 30-40%
> ... **Realistic total $1.8-2.2M**... **Runway impact.** $2.4M / $310k = 7.7
> months today... you're at **~5.8 months**...
>
> ## 2. The personal guarantee is the real tail risk
> ... **It bites precisely when the company fails.**... **It creates a live
> governance conflict.**...
>
> ## 3. Your own survey is telling you something you may be discounting
> ... Expect **4-8 regretted departures in year one**...
>
> ## 4. The diagnosis may be wrong, and it's cheap to check
> ... **55% retention on what denominator?** If it's 3 of 6 juniors, n=3 cannot
> carry a $2M decision...
>
> ## 5. The structure is backwards on timing
> ... **"Three weeks or it goes" is very likely manufactured.**...
>
> ## 6. Two execution details that quietly break the plan
> ... **The space is too big if the mandate fails and too small if it
> succeeds.**...
>
> ## What I'd actually recommend
>
> **Don't sign in three weeks.** Instead: 1. Buy the experiment, not the
> conclusion... 2. Fix the mentorship problem in parallel... 3. If you do
> lease, renegotiate as a tenant in a soft market...
>
> **Tripwires - agree these before you sign anything:** don't proceed if fewer
> than ~two-thirds of the 12 remote-contract staff agree in writing to new
> terms; if more than two senior mentors signal departure; if post-outlay
> runway is under 9 months without committed funding...

**What is wrong with it**

| Defect | Where |
|---|---|
| No verdict anywhere | Six sections of analysis, then the answer as the last heading. The reader has to reach the bottom to learn what to do |
| You cannot tell what was skipped | Six areas, chosen by the writer. Competitor response is never mentioned - considered and empty, or never looked at? Nothing says |
| Nothing is scored | Every risk is prose. Which is likeliest, which is worst, and which you would not see coming are three different questions, and the reader is left to separate them |
| The load-bearing belief is a footnote | "Two assumptions worth confirming" in italics under the opening. The one belief the whole decision rests on is never isolated |
| Warnings nobody can act on | "Don't proceed if more than two senior mentors signal departure" - measured how, checked when, by whom? |
| The ordinary failures are never swept | The class of decision is never named, so the ways this kind of deal usually dies are never worked through as a list |

All six are cured somewhere below. The first two are cured on the screen; the
other four are cured underneath it, which is why this example shows all four
layers rather than stopping at part one.

## AFTER - part one, the screen (24 lines)

> # What could go wrong - signing a 3-year, $1.04M city-centre office lease and mandating 3 days a week
>
> | | |
> |---|---|
> | **Verdict** | **Think again** |
> | **Why** | At $310k/month burn against $2.4M cash, the company runs out of money around month 6 after signing - roughly ten months before month 12, the date it planned to grade this decision by. |
> | **Worst case** | $348,000 of cash gone before anyone sits down, ~$1.04M of non-cancellable rent, one director personally liable for the unpaid remainder, 7-11 of 40 staff gone, and no measurement that can tell you whether any of it worked. |
>
> **The biggest risks**
>
> 1. The runway ends before the answer arrives. $348,000 out up front, burn
>    rises ~11%, cash hits zero ~2.4 months after move-in; the success metrics
>    are dated month 6 and month 12. (risk 1)
> 2. Attrition lands on the people you can least replace, and it starts at the
>    announcement - two months before move-in, when every dollar is already
>    committed. 11 of 31 survey respondents already flagged themselves. (risk 2)
> 3. The personal guarantee converts a company failure into one director's
>    personal debt, and after signature that director's own interests argue
>    against an honest month-6 review. (risk 3)
>
> **The thing nobody is questioning**
>
> That this is a decision about how the company works, with a cost attached -
> rather than a financing decision with a culture story attached.
>
> **Fix before you commit**
>
> - Do not sign inside the three-week window. Ask for it to be extended; if the
>   answer is no, walk and see whether the phone rings... (risk 6)
> - Trade the personal guarantee against the six-month deposit. Landlords
>   normally take one or the other. Worth $84,000 of cash or one director's
>   house. (risks 3, 6)
> - Decide the 12 remote contracts in writing, before any expectation is
>   announced. Then check the arithmetic: with 12 exempt, 80% is unreachable
>   until headcount passes 60. (risk 5)
> - Start measuring cycle time today, from the existing tracker. One day of
>   work. Without a baseline, "a measurable drop in time-to-ship" cannot be
>   passed or failed at month 12. (risk 4)
> - ...
>
> **The decision, rewritten**
>
> Do not sign this lease in this window. Spend the next quarter on the free
> version of the same thesis: baseline cycle time from the tracker, put a named
> mentor and daily pairing on every junior, and take 20-30 flexible desks or a
> 12-month serviced office near where staff already cluster - well under
> $150,000 a year, cancellable, no guarantee...

## AFTER - the outside view, which the BEFORE has no equivalent of

> ### What usually kills decisions like this
>
> Two classes stacked: **a long, non-cancellable fixed commitment signed under
> a deadline**, and **a return-to-office mandate imposed on staff who were
> hired remotely**.
>
> Committed leases usually fail in six ordinary ways. (1) *The commitment
> outlives the plan*... (2) *Runway math* - the lease survives the tenant...
> (3) *Concessions left on the table because of a clock*... (4) *Fit-out
> overruns and schedule slips*... (5) *Dilapidations and exit costs*... (6)
> *The exit that isn't* - sublease rights look like an escape hatch and recover
> a fraction, slowly, in the same weak market that made you want out.
>
> Mandates usually fail in four. (7) *Attrition concentrates in the most
> marketable staff*... (8) *Compliance gets measured as attendance rather than
> as the outcome the office was meant to buy*... (9) *The mandate is announced,
> softened under pressure*... (10) *A symptom is attributed to the wrong
> cause*...
>
> **Live here: all ten.** Growth to 65 is unfunded (1). Runway is 7.7 months
> against a 36-month term (2). Zero concessions in a market listing 15-20%
> below asking (3)...
>
> **Not live:** the space being too small - 6,000 sq ft is about right for 65
> hybrid and generous for 40. Landlord insolvency mid-term is possible but
> unevidenced... A regulatory shock that empties offices again is a tail risk
> nobody can forecast, but note there is no break clause if one comes.

The "not live" paragraph is the part that makes this checkable. A reader can
disagree with it. Nothing in the BEFORE can be disagreed with in that way,
because nothing in it says what was considered and dismissed.

## AFTER - the record of the sweep

> ### What was checked
>
> - **Will people use it** - Two risks. The 80% target is arithmetically
>   unreachable as written (risk 5), and the thing it is meant to buy was never
>   diagnosed (risk 4).
> - **Money** - Three risks. The runway (risk 1), the deal terms against the
>   market (risk 6), and the sublet that doesn't recover what people think
>   (risk 7).
> - **Building it** - One risk. $180,000 across 6,000 sq ft is $30/sq ft, and
>   the four-month window has no facilities hire in it yet (risk 8).
> - **Running it day to day** - One risk... (risk 10).
> - **The people involved** - Two risks... (risks 2, 3).
> - **Things you depend on** - Folded into risks 6, 7 and 8: the landlord is
>   the counterparty on the deadline, on sublet consent, and on holding
>   $168,000 that may not be in escrow...
> - **Legal and rules** - Folded into risks 3 and 5...
> - **People misusing it** - One risk. Presence theatre keeps the metric green
>   and the money flowing past the point the thesis failed (risk 9)...
> - **What others do about it** - Real, but as a mechanism inside risk 2 rather
>   than its own card: remote-first competitors treat a dated mandate as a
>   recruiting signal...

Nine lines, nine areas, including the ones that produced no card of their own
and why. This is the part that answers "what did you not look at", and it is
the reason the sweep can be trusted without the reader repeating it.

## AFTER - one risk card, to show the shape

> ### 5. The 80% target is impossible as written, and the only way to make it possible breaks 12 contracts [Will people use it / Legal] - Fix before you commit
>
> - **How it happens:** 12 of 40 staff are on explicitly remote contracts... If
>   they are exempt - which the brief assumes but has not decided - the maximum
>   attendance is **28 of 40 = 70%**, at perfect compliance from everyone who
>   can comply. The 80% target fails on announcement day, by definition... If
>   instead they are *not* exempt, you are unilaterally changing an expressly
>   agreed contractual term for 30% of the company... There is no third option,
>   and the brief has chosen neither.
> - **What we are assuming:** "That a three-day expectation is enforceable
>   against staff hired remotely" - the author's own assumption...
> - **What this is based on:** "All 40 staff, of whom 12 were hired on
>   explicitly remote contracts..." "80% of staff in the office three or more
>   days a week by month six."
> - **How likely:** **High**, and for the arithmetic, certain. My estimate of
>   the realistic month-6 figure... **20-23 people at 3+ days, about 50-58%**...
> - **How bad:** **Serious.** The headline success criterion is unachievable,
>   so the month-6 review has no honest way to pass...
> - **Would you see it coming:** **Easily.** It is division. Nobody has done it.
> - **How it shows up:** Announcement week: the first question in the all-hands
>   is "does this apply to the remote team?", and there is no answer. Weeks
>   2-8: exemption requests from non-exempt staff... Month 6: 50-58% against a
>   target of 80%, and a debate about the denominator instead of the outcome.
> - **Early warning:** *What to watch* - the exemption policy: written, dated,
>   with named criteria and a named decider · *When to worry* - no written
>   policy exists on the day of the announcement, or exemption requests exceed
>   4 in the first month · *When to check* - before signature, and weekly for
>   the first eight weeks after announcement · *What to do then* - publish the
>   criteria and the appeal route the same day...
> - **What to do about it:** Decide the exemption in writing before you
>   announce anything, and restate the goal as a number that can be reached...
>   **What gets worse:** a written exemption for 12 people makes the two-tier
>   company explicit and visible... That resentment is real - and it exists
>   either way; writing it down just makes it manageable.

Three separate scores, and the one that does the most work is the cheapest:
"Would you see it coming: Easily. It is division. Nobody has done it." The
early warning names a signal, a threshold, a checkpoint and an action, so it
can be handed to somebody. Compare the BEFORE's "if more than two senior
mentors signal departure", which cannot.

## What this example changed in the format

1. **The outside-view section exists because of this pair.** The first run
   attacked the reference class properly, but only inside individual cards, so
   nothing named it and a reader could not check whether the ordinary ways such
   deals die had been swept. Asked directly, the agent confirmed there was no
   standalone section. "What usually kills decisions like this" is now a
   section of its own, and cards cite it. On the re-run above it produced ten
   named killers and a "not live" list.
2. **Part one stopped showing three numbered risk slots.** A template with
   exactly three slots reimposes the quota that three separate rules exist to
   remove. It now says at most three, one per surviving risk, and says what to
   write when nothing survived.
3. **Every line of "Fix before you commit" carries its risk number.** Without
   them the list reads as loose advice. With them each item traces back to the
   mechanism that earned it, and an item with no card behind it is visible as
   padding.
4. **The empty areas are worth as much as the full ones.** Here "things you
   depend on" and "what others do about it" produced no card of their own. Both
   still get a line saying where the mechanism went instead. That is the
   difference between a sweep and a list of whatever came to mind.
5. **Still visible above: the report leaks specialist words.**
   "Dilapidations", "escrow", "covenant", "in escrow or the landlord's money" -
   all appear without saying what the person would actually see happen, which
   is the rule at the top of the analysis prompt. Part one is clean; the detail
   is not. The output here is kept as it came, because a record that gets
   edited stops being a record. The example where the rule holds further down
   is [example 2](02-clinic-database-move.md), a database move: its detail
   layer says what a clinic would see beside every specialist term but four,
   and it lists those four.
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