Skip to content

hashgraph-online/awesome-codex-plugins / plugins/boshu2/agentops/skills/premortem

premortem

Verified

Find how a rollout plan could fail before committing to it. Use when: asked what could go wrong or to poke holes in a plan.

FileKindSize
SKILL.mdskill md7.6 KB
references/derivation-diff.mdmarkdown1.5 KB
references/durable-review.mdmarkdown1.7 KB
schemas/premortem-plan-review.v1.schema.jsonconfig1.3 KB
scripts/validate-output.shexecutablescript2.4 KB
scripts/validate.shexecutablescript1.5 KB

references/derivation-diff.md

View on GitHub
# Derivation-diff challenge

Loaded by [Premortem](../SKILL.md) for integration- or extension-class plans
when anchoring on the working plan is the consequential risk.

Select an independent derivation using
[Plan's shared challenge method](../../plan/references/challenge.md), then
compare. Give one fresh context only the intent source and the relevant ground
truth (the vendor docs and stock behavior for integration work, the
repository's patterns and behavior spec for extension work) and never the
author's design. Have it sketch its own design from that ground truth alone.
Compare that independent design with the working plan in the advisory findings;
each supported divergence is a question to resolve. Convergence is weak
evidence that the plan follows the ground truth; divergence names where it may
not.

The challenger answers two questions with an artifact, not an opinion:

- Cathedral: is this the smallest real thing, or does it rebuild what already
  exists? Artifact: the simplest version that satisfies acceptance, plus the
  named reason it is insufficient. No named reason means build the simple one.
- Grain: for integration work, does every component the plan writes have a
  native counterpart in the substrate? Artifact: the native-counterpart list,
  one row per component the plan authors, naming the substrate feature it
  duplicates or the reason none exists.

These are integration- and extension-class checks. The Grain list applies only
to integration-class work; do not impose it on routine feature work.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 321kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 321kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 321kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 321kUpdated Claude CodeCodexVerifiedInstall