36 lines
1.8 KiB
Markdown
36 lines
1.8 KiB
Markdown
|
# /goal templates — kill-criteria (#22) and pre-mortem (#23)
|
|||
|
|
|
|||
|
|
Not scheduled. Paste into an interactive omp session when facing a decision.
|
|||
|
|
Both end with pasted proof per the goal contract: the judge only sees the
|
|||
|
|
conversation, so "done" = the artifact is IN the chat.
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
## kill-criteria (#22)
|
|||
|
|
|
|||
|
|
/goal For the decision "[DECISION]", produce a kill-criteria table for every
|
|||
|
|
live option. For each option: (1) state the option in one line, (2) write the
|
|||
|
|
SINGLE measurable condition that would disqualify it — a number, a date, or a
|
|||
|
|
named event, not vibes, (3) hunt for evidence for/against that condition using
|
|||
|
|
web search and the repos under ~/Developer/github.com/wltbs, citing every
|
|||
|
|
claim, (4) verdict: ALIVE / KILLED / NEEDS-DATA with what data and where to
|
|||
|
|
get it. Done when the full table is pasted in this chat with a citation per
|
|||
|
|
verdict, and every KILLED verdict quotes the evidence that tripped its
|
|||
|
|
condition. If evidence can't be found for an option, paste what you searched
|
|||
|
|
and mark it NEEDS-DATA — do not guess. Hard cap: 40 tool calls.
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
## pre-mortem (#23)
|
|||
|
|
|
|||
|
|
/goal It is 12 months from now and the decision "[DECISION]" failed badly.
|
|||
|
|
Write the post-mortem as if it already happened: (1) the headline of the
|
|||
|
|
failure, (2) the 3–5 causal chains that led there, each traced back to a
|
|||
|
|
specific assumption we hold TODAY (quote the assumption from our notes/repos
|
|||
|
|
where possible), (3) for each chain, the earliest observable warning sign and
|
|||
|
|
where it would show up first (a metric, a log, a competitor move, a regulator
|
|||
|
|
page), (4) the one cheapest mitigation per chain that we could start this
|
|||
|
|
week. Done when the full pre-mortem is pasted in this chat and every causal
|
|||
|
|
chain names its present-day assumption explicitly. No generic risks ("market
|
|||
|
|
turns") — every chain must be specific to WalletBase's architecture, GTM, or
|
|||
|
|
regulatory surface. Hard cap: 30 tool calls.
|