critical

Solid

Adversarially challenges a proposed plan, code change, or bug diagnosis from a hostile pre-mortem perspective. Walks a fixed taxonomy of failure modes, blast radius, rollback, hidden coupling, and maintainability; every finding must cite a file, line, or named assumption; forces a steelman of at least one alternative. Surfaces concerns only — does not score (delegates to `/confidence`) and does not apply fixes. Use during planning before autonomous execution, before opening a high-stakes PR, or when a fix "feels off". One adversarial pass per run — naïve self-refine loops amplify bias. Modes: plan (default), code, analysis. Triggers on "critical", "challenge this", "pre-mortem", "red-team this", "/critical".

Data & Documents 8 stars 2 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
32
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Critical — Adversarial Pre-Mortem Challenge the proposed work as a hostile staff engineer would. Surface specific, grounded failure modes; force at least one steelmanned alternative; hand scoring to `/confidence`. > **Why this exists, in one paragraph.** > A single LLM "be honest" pass tends to confirm rather than challenge — naïve self-refine has been shown to amplify bias (Pride and Prejudice, ACL 2024) and to add no gains over self-consistency when the initial answer is already strong (SELF-[IN]CORRECT, AAAI). > External grounding plus a fixed taxonomy beats vague introspection (CRITIC framework). > This skill is the structured counter-pressure: one pass, hostile persona, mandatory citations, mandatory steelman, no self-scoring. ## Contents - [When to use](#when-to-use) - [Mode detection](#mode-detection) - [The persona contract](#the-persona-contract) - [External grounding rule](#external-grounding-rule) - [Taxonomy — `plan` mode](#taxonomy--plan-mode) - [Taxonomy — `code` mode](#taxonomy--code-mode) - [Taxonomy — `analysis` mode](#taxonomy--analysis-mode) - [Mandatory steelman alternative](#mandatory-steelman-alternative) - [Output format](#output-format) - [Composition with other skills](#composition-with-other-skills) - [Hard rules and non-goals](#hard-rules-and-non-goals) --- ## When to use | Use it | Don't use it | | ------------...

Details

Author
mthines
Repository
mthines/agent-skills
Created
3 months ago
Last Updated
2 days ago
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

insight-critique

Advisory review workflow. Reviews the last plan, code, architecture, or UI output and returns a structured report: Summary, Strengths, Risks, Fixes. Use when the user runs /critique, asks to "review this", "critique this", or "what's wrong with this", or wants focused feedback on a specific output. Also trigger as a quality gate before /execute. Advisory only — never blocks unless a kernel-prime violation is present. For multi-POV adversarial stress-testing with personas, use /insight-adversarial instead.

14 Updated 3 days ago
allemaar
AI & Automation Listed

skill-adversarial-security

Use when performing OWASP security critique in adversarial style (optional sarcastic skin). Part of VDD Multi-Adversarial pipeline.

4 Updated 1 weeks ago
MatrixFounder
Web & Frontend Listed

pre-mortem

Adversarial pre-mortem skill that actively hunts for fatal flaws in plans, proposals, decisions, and strategies. Refuses to be supportive or balanced. Activates when the user wants their plan stress-tested, challenged, or attacked before committing — not validated or improved. Surfaces the 1–3 assumptions the plan is most likely wrong about. Builds the strongest possible case against the plan. Ranks failure scenarios by probability × damage. Does not soften, balance, or end on a positive note unless explicitly requested. Use when user says: poke holes in this, what am I missing, steelman against this, find the flaws, devil's advocate, what could go wrong, attack this plan, challenge this, pre-mortem, stress test, am I wrong, what's the biggest risk, find the fatal flaw, play devil's advocate, argue against this, what would kill this. Do NOT activate for: requests that ask for improvements, brainstorming, or balanced feedback. Switch off when user says 'now help me fix it'. First response: "Pre-Mortem active.

3 Updated 2 weeks ago
Sandeeprdy1729