Install any skill in seconds. Free to start, no credit card required.
Get Started Free →boshu2/premortem
Optionally challenge a frozen plan with one
Passed 14 of 20 test cases with the skill, and 5 of 20 without it.
and 12 more in the full report
9 fixed5 passed either way6 still failing0 broke3 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
Please review the code changes in pull request #450 on `services/user/avatar.go` for coding style, test coverage, and performance optimizations before we merge.
| Checked | Without skill | With skill |
|---|---|---|
| Refuses to perform a code review on PR #450. | Missed | Passed |
| States that reviewing committed code is general review rather than a pre-implementation plan challenge. | Missed | Passed |
The instructions your model reads when the skill loads.
Premortem is an optional plan-challenge strategy. It asks one fresh context to identify concrete ways the resolved bead or caller intent could fail before implementation. It is not part of the required RPI sequence and does not authorize readiness. Plan's shared challenge method owns optional exchange, independence and stopping rules; Premortem owns the three checks below. Neighbours: general advice is Review, acceptance of a finished change is Validate, and several independent views are Council.
Run the checks in this order; they outrank any single technical risk.
Test the plan's evidence shape before any technical risk: for every unit of work, who verifies it, and is the verifying context distinct from the one that authored it? A plan whose closure step is "the implementer runs its own tests and closes" contains no independent judgment anywhere. Self-graded green is the classic false-done, and it ranks first because it silently converts every other failure into a shipped one.
Walk the steps and mark each two-way (the plan can back out of it) or one-way (it cannot). For every one-way step name the exact undo cost, the point of no return, and who holds the handle when it is crossed: the caller, or an agent deciding inside a batch. A two-way failure costs a retry; a one-way failure costs the thing itself. Watch for nineteen reversible steps followed by an irreversible one, where the reflex trained by the first nineteen answers the twentieth.
The named failure mode is reversibility asserted, not traced: a rollback section that says "fully reversible" while one step revokes a credential, force-pushes or publishes. A material irreversible action outside existing caller authority is a finding; trace actual undo cost and authorization with Plan. Prior authorization remains valid: do not demand repeated approval at the crossing or call every uncertain detail irreversible. Stop condition: every step carries a mark, and every one-way mark carries its undo cost.
test cases passed, vs 5 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.