domains / families / agent-tooling / os-what-could-go-wrong

os-what-could-go-wrong

separate

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.

When to use

When not to use

Skill page

Source

RepositoryPath
kharmanskyi/open-stepsskills/os-what-could-go-wrong/SKILL.md