.NET MAUI Release Readiness
dotnet/maui
Produces evidence-backed ship-readiness verdicts for .NET MAUI Servicing Releases and Previews, and drafts public-safe release handoff pages from the result.
Find how a rollout plan could fail before committing to it. An agent skill from boshu2/agentops.
Install Premortem
$ npx skills add boshu2/agentops --skill premortem -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install boshu2/agentops premortem --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/boshu2/agentops.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/premortem .claude/skills/premortem && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "premortem" agent skill from https://github.com/boshu2/agentops/tree/main/skills/premortem into .claude/skills/premortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "premortem", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/boshu2/agentops/tree/main/skills/premortemType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add boshu2/agentops --skill premortem -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install boshu2/agentops premortem --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boshu2/agentops.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/premortem .agents/skills/premortem && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "premortem" agent skill from https://github.com/boshu2/agentops/tree/main/skills/premortem into .agents/skills/premortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "premortem", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add boshu2/agentops --skill premortem -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install boshu2/agentops premortem --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boshu2/agentops.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/premortem .cursor/skills/premortem && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "premortem" agent skill from https://github.com/boshu2/agentops/tree/main/skills/premortem into .cursor/skills/premortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "premortem", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/boshu2/agentops.git --path skills/premortem--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add boshu2/agentops --skill premortem -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install boshu2/agentops premortem --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boshu2/agentops.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/premortem .gemini/skills/premortem && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "premortem" agent skill from https://github.com/boshu2/agentops/tree/main/skills/premortem into .gemini/skills/premortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "premortem", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install boshu2/agentops premortemInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add boshu2/agentops --skill premortem -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/boshu2/agentops.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/premortem .github/skills/premortem && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "premortem" agent skill from https://github.com/boshu2/agentops/tree/main/skills/premortem into .github/skills/premortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "premortem", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add boshu2/agentops --skill premortem -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install boshu2/agentops premortem --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boshu2/agentops.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/premortem .opencode/skills/premortem && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "premortem" agent skill from https://github.com/boshu2/agentops/tree/main/skills/premortem into .opencode/skills/premortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "premortem", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
premortem- GitHub stars
- 448
- Used in
- 1 other repo
- Token cost
- ~1.8k tokens
- SKILL.md length
- 864 words
- Files
- 6 (incl. scripts, references)
- Skills in repo
- 31
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Find how a rollout plan could fail before committing to it. An agent skill from boshu2/agentops.
- Works in 5 steps: Resolve the existing intent source and… → Judge from a context that did not write… → Run the three checks, then test… → …
- : asked what could go wrong
- SKILL.md covers The first check: who verifies,…, The second check: which steps…, The third check: construct the… and Workflow, plus 4 more sections
- Runs Shell scripts from its folder
What it does
Premortem is an agent skill from boshu2/agentops. 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.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts and reference files (for example `references/derivation-diff.md`, `schemas/premortem-plan-review.v1.schema.json` and `scripts/validate-output.sh`).
It sits in Product & Project Management, covering Feature launches and release readiness. The repository describes itself as: DevOps discipline for AI coding agents: shape the work, track it as a graph, and get each change judged by a context that didn't write it. The licence is Apache-2.0.
When your agent uses it
- : asked what could go wrong
- Poke holes in a plan
Example prompts
- “/premortem”
Requirements
- Python 3
- A Bash shell
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Resolve the existing intent source and inspect its acceptance, non-goals,
- Judge from a context that did not write the plan, following the shared
- Run the three checks, then test acceptance completeness, edge behavior,
- Return one complete, bounded set of concrete findings with checked and
- Stop. The caller decides whether to revise the plan or invoke RPI.
What it can do on your machine
Read from SKILL.md and the folder at commit 8704853. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 2 files in scripts/ (Shell), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Premortem loads about 1.8k tokens when it runs, and up to ~2.3k if it reads all its reference files. Until then it costs about 33 tokens; SKILL.md has 864 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from boshu2/agentops at commit 8704853, republished under its Apache-2.0 licence (© boshu2). 864 words, ~1,791 tokens.
Download SKILL.mdSave it as
.claude/skills/premortem/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- premortem
- description
- 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.
- practices
- design-by-contract, adr
- hexagonal_role
- domain
- produces
- premortem-plan-review.v1
- skill_api_version
- 1
- user-invocable
- true
- metadata.capabilities
- challenge_plan
- metadata.effects
- write_advisory_plan_review
- metadata.canonical_status
- canonical
- metadata.disposition
- keep_strategy
- metadata.graph_root
- true
Premortem
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.
The first check: who verifies, and are they fresh?
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.
The second check: which steps are one-way doors?
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.
The third check: construct the failure
For every candidate failure, attempt a concrete defeat: write the input, command sequence or repository state that would make the plan fail, and run or cite the check that shows whether the plan survives it. When execution is not available, the constructed input or sequence plus a cited fact (file and line, documented behavior, an observed output) counts as the attempt. A failure you could not construct is reported as attempted-and-blocked with the obstacle named, which is itself evidence for the plan. The named failure mode is armchair pessimism: imagined risks with no construction, which reads as diligence while testing nothing. A finding with neither a construction nor a blocking fact is deleted, not softened.
Show full SKILL.md (409 more words)Show less
Workflow
- Resolve the existing intent source and inspect its acceptance, non-goals,
evidence requirements and declared write scope. Its digest is the SHA-256 of
the exact intent text as supplied (for example
shasum -a 256 plan.md). - Judge from a context that did not write the plan, following the shared challenge method for identity, model selection, authorization and bounds. A plan the caller wrote can be judged here, with the caller as author. If this context wrote the plan and no fresh context can be started, run the checks anyway, state that the independence leg is missing, and return inline findings; never describe them as independent.
- Run the three checks, then test acceptance completeness, edge behavior, scope and dependencies against cited repository facts. For integration or extension plans where anchoring on the working design is the risk, add the derivation-diff challenge.
- Return one complete, bounded set of concrete findings with checked and not-checked scope.
- Stop. The caller decides whether to revise the plan or invoke RPI.
Council or Dueling Idea Genies may be caller-supplied evidence, but Premortem requires neither and cannot turn consensus into approval.
Prompt
Premortem this plan before I implement: bead ag-4f21 proposes rewriting
`scripts/regen-all.sh` to call `ao gate check` instead of shelling out to
the Python generators, touching cli/internal/gates/regen.go. Plan and
acceptance are in the bead. Find concrete ways it fails.It's working if
Observable in the trace, without reading the prose, and the rubric a fresh independent judge scores this skill against:
- Every unit of work carries a named verifier, and any unit verified by the context that authored it comes back as a finding.
- Every step carries a two-way or one-way mark, and each one-way mark names its undo cost and its point of no return.
- Every reported finding cites a defeat attempt (the input, command or repository state constructed) or the fact that blocked the construction.
- The finding set is bounded: a review that flags every step has reported nothing.
Boundary
- Emit advisory findings, no verdict of any version, readiness, admission, or permission.
- Do not implement, validate the candidate, retry, repair, schedule, claim, change acceptance, operate Git, close work, release, or deliver.
- Any plan edit creates a new subject for a later caller-initiated Premortem.
Output
Return findings inline by default:
Findings (most consequential first)
1. <step> - <how it fails> - <construction, or the fact that blocked it> - <consequence>
Verifiers: <unit>: <who verifies>; self-verified units are findings
One-way steps: <step> - <undo cost> - <point of no return> - <who holds the handle>
Checked: <what was examined>. Not checked: <what was not>.
Independence: <judge context, distinct from author> or "missing: <reason>"When the caller requests a durable review, return premortem-plan-review.v1
with the intent digest, author and judge context IDs, findings, evidence
references, checked, and not_checked, and check it with this skill's
scripts/validate-output.sh. The schema requires distinct author and judge
IDs, so a review without an independent judge stays inline. An empty finding
set means only that this optional challenge found no concrete defect; it is
never a lifecycle gate.
© boshu2, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files (scripts, references) in skills/premortem of boshu2/agentops.
- SKILL.md
- references/derivation-diff.md
- references/premortem.feature
- schemas/premortem-plan-review.v1.schema.json
- scripts/validate-output.sh
- scripts/validate.sh
Open the folder on GitHubat commit 8704853
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in boshu2/agentops, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Premortem next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Premortem this skillboshu2/agentops | 448 | 1 repos | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| .NET MAUI Release Readinessdotnet/maui | 23k | — | ~15k | Automated safety check: Pass | MIT | |
| Release ValidationMesh-LLM/mesh-llm | 3.5k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Final Release Reviewopenai/openai-agents-python | 30k | — | ~5.4k | Automated safety check: Pass | MIT | |
| Final Release Reviewopenai/openai-agents-js | 3.9k | — | ~4k | Automated safety check: Pass | MIT | |
| Acceptance Demo GeneratorChachamaru127/claude-code-harness | 3.2k | — | ~3.4k | Automated safety check: Notes | MIT |
Similar skills
- Official
Release Validation
Mesh-LLM/mesh-llm
A skill your agent uses when validating a MeshLLM release candidate or current HEAD against the last GitHub release, assembling the canonical feature/fix/modification inventory, testing locally…
- Official
Final Release Review
openai/openai-agents-python
Assess a Python SDK release candidate or release plan against the previous release and recommend ship or block.
- Official
Final Release Review
openai/openai-agents-js
Assess a JS SDK release candidate or release plan against the previous release and recommend ship or block.
Acceptance Demo Generator
Chachamaru127/claude-code-harness
Renders a single HTML page showing each acceptance criterion as verified or not, with a ship, wait, or reject recommendation for non-engineers.
Schematic
blader/schematic
Reverse engineer a detailed product and technical specification document from a git branch's implementation.
More from boshu2/agentops
All 31 skills in this repoAgent Native
boshu2/agentops
Dispatch independent tasks to parallel workers or subagents without write collisions.
Council
boshu2/agentops
Compare independent opinions from several models or contexts without inflating agreement.
Craft Goal
boshu2/agentops
Draft or lint a bounded long-running goal prompt with a finish line and hard limits.
Doc
boshu2/agentops
Write or update READMEs, docs, repo instructions and handoff notes, checked against source.
Idea Genie
boshu2/agentops
Brainstorm evidence-backed options for what to build, or stress-test an idea.
Implement
boshu2/agentops
Change or repair code, config or services without weakening tests; report what ran and what did not.
Related
Categories
Questions about Premortem
What does Premortem do?
Find how a rollout plan could fail before committing to it. An agent skill from boshu2/agentops. Premortem is an agent skill from boshu2/agentops. Find how a rollout plan could fail before committing to it.
When should I use Premortem?
Premortem fits situations like: : asked what could go wrong; poke holes in a plan.
How do I install Premortem in Claude Code?
Run `npx skills add boshu2/agentops --skill premortem -a claude-code`. Or copy the skill folder (skills/premortem in boshu2/agentops) into .claude/skills/premortem in your project. Claude Code loads it when a task matches its description.
How do I install Premortem in Codex?
Run `npx skills add boshu2/agentops --skill premortem -a codex`. Or copy the skill folder (skills/premortem in boshu2/agentops) into .agents/skills/premortem in your project. Codex loads it when a task matches its description.
Can I use Premortem in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add boshu2/agentops --skill premortem -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/premortem, .gemini/skills/premortem, .github/skills/premortem and .opencode/skills/premortem in your project.
What does Premortem need to run?
Going by SKILL.md and its folder, Premortem needs a shell for the scripts in its folder. Our summary lists: Python 3; A Bash shell.
Does Premortem access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Premortem safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Premortem use?
Premortem is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Premortem use?
About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 558 tokens, read only when the agent opens those files.
What are the alternatives to Premortem?
Skills that share tags, products or a category with Premortem: .NET MAUI Release Readiness (dotnet/maui, 23k stars), Release Validation (Mesh-LLM/mesh-llm, 3.5k stars), Final Release Review (openai/openai-agents-python, 30k stars) and Final Release Review (openai/openai-agents-js, 3.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Premortem?
boshu2 (a GitHub user) maintains it in boshu2/agentops, which has 448 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 9, 2026.
Source: boshu2/agentops on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.