factory-adversarial-reasoning

Validate non-trivial software decisions against SDLC governance and YAGNI principles.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/e2its/myrmion-AI-factory --skill factory-adversarial-reasoning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: factory-adversarial-reasoning
Source: https://github.com/e2its/myrmion-AI-factory/tree/main/.claude/skills/factory-adversarial-reasoning
Command: npx skills add https://github.com/e2its/myrmion-AI-factory --skill factory-adversarial-reasoning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of unvetted, non-compliant, or over-engineered decisions in software development workflows, ensuring all non-trivial choices are rigorously tested against SDLC rules and product objectives before implementation.

Core Features & Use Cases

  • Mandatory FOR/AGAINST Double Pass: Requires every non-trivial proposal or selection to be evaluated for both strengths and weaknesses before being accepted.
  • Governance & Product Alignment Checks: Tests all options against corporate SDLC rules, defect prevention controls, security policies, and product roadmap goals.
  • Do-Less YAGNI Lens: Automatically flags over-engineering risks, prioritizing simpler stdlib, native, or existing dependency solutions over unnecessary new code.
  • Use Case: When an agent proposes adding a new third-party authentication library for a simple internal tool, this Skill forces evaluation of whether the choice violates DRY rules, introduces unnecessary security risk, or if a simpler native platform authentication feature would suffice.

Quick Start

Use the factory-adversarial-reasoning skill to validate any proposed non-trivial design, tooling, or scope decision against SDLC governance and product goals before finalizing your recommendation.

Frequently Asked Questions about factory-adversarial-reasoning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce adversarial reasoning for software design decisions?

Apply a mandatory FOR/AGAINST double pass to validate non-trivial choices against SDLC rules and product goals before implementation, preventing unvetted or over-engineered software design decisions.

What is a FOR/AGAINST double pass in SDLC governance?

A FOR/AGAINST double pass in SDLC governance is an adversarial validation mechanism requiring every non-trivial proposal to be evaluated for both strengths and weaknesses before acceptance.

How can I prevent over-engineering and validate YAGNI principles in agentic development?

Prevent over-engineering and validate YAGNI principles in agentic development by applying a Do-Less lens that flags unnecessary new code, prioritizing simpler stdlib or existing dependency solutions over complex additions.

Does this approach work for evaluating new third-party tooling versus native platform features?

Yes, this approach evaluates new third-party tooling versus native platform features by forcing governance checks to determine if new dependencies introduce unnecessary security risks or violate DRY rules.

When do I need mandatory decision validation in my software development workflow?

You need mandatory decision validation in your software development workflow when making non-trivial selections for design, tooling, scope, or implementation approaches within governed SDLC processes.

What are the limitations of applying YAGNI minimalist implementation principles to defect prevention?

Limitations of applying YAGNI minimalist principles to defect prevention include the potential to oversimplify complex security requirements, though it effectively reduces risk by avoiding unnecessary code generation.