Challenge ideas and designs with adversarial thinking and pre-mortem analysis.
npx skills add https://github.com/baphled/dotopencode --skill devils-advocate-baphled
Please help me install this Agent Skill. Skill: devils_advocate Source: https://github.com/baphled/dotopencode/tree/main/skills/devils-advocate Command: npx skills add https://github.com/baphled/dotopencode --skill devils-advocate-baphled
This Skill helps identify potential flaws, weaknesses, and failure modes in ideas, designs, and decisions by employing adversarial thinking and pre-mortem analysis.
Use the devils_advocate skill to challenge the proposed architecture for the new user authentication system.
High-intent search queries and answers about installing and using this skill.
Pre-mortem analysis is a technique that assumes a design has failed and works backward to identify causes. It helps combat groupthink and happy path bias by deliberately challenging proposals to uncover vulnerabilities and hidden flaws before implementation.
Yes, adversarial thinking challenges microservice architectures by stress-testing for security, scale, and complexity risks. It applies steelmanning to validate designs and proactively identify partial failure scenarios and circular dependencies during architectural reviews.
The best way to combat groupthink during a design review is employing pre-mortem analysis and adversarial thinking. This prevents over-reliance on happy path scenarios by deliberately challenging proposals and finding vulnerabilities in the design.
You need pre-mortem analysis during planning phases and design validation before finalizing implementations. It simulates potential failure scenarios to proactively design mitigations, combatting happy path bias and uncovering hidden flaws in decisions.
Pre-mortem analysis for architectural reviews is limited if the initial design lacks sufficient detail for steelmanning. Without concrete architectural proposals, adversarial thinking cannot effectively stress-test scale, partial failure, and complexity risks.
adilkalamStress-test proposals through a six-phase adversarial analysis framework.
riethmayerIdentify failure modes in plans, prompts, or strategies by reasoning backward from outcomes.
lyndonklFacilitate structured adversarial review of plans using role-playing and risk assessment matrices.
Destynova2Analyze codebases for god functions, circular dependencies, dead code, and module boundaries.
