os-what-could-go-wrong

# os-what-could-go-wrong Assume it already failed, then work backwards to find out why - while there is still time to change it. The attack runs in a fresh agent that had no part in the decision, because an agent that helped shape one reviews it far too gently: it defends its own reasoning, and it misses the thing that kills the plan out of politeness. This skill writes the brief, hands it over, and passes the answer back without softening it. `os-ask-simple` screens a choice before the user picks one. This one runs after the choice is made and before it can no longer be taken back. ## Language Write in the language the user speaks in this session, detected from the conversation. Names, figures and identifiers stay as they are. The agent you dispatch cannot see this conversation and does not inherit the writing style, so the language has to travel with the handover - see step 2. ## Step 1 - write down what is actually being decided Find the decision first. Given as text or a document, that is it. Asked at the end of a discussion, it is the decision the discussion arrived at, and say which one you took it to be. If neither, ask which decision to attack. Then fill every line. This is the only thing the fresh agent will ever see. ``` DECISION BRIEF What will be done: three to seven sentences What it is for: the problem it solves, and what success looks like, measured wherever it can be The main moves: the money, the people, the systems, the dates What is fixed: the con...