adversary

Analyze development plans for edge cases, security vulnerabilities, and scalability bottlenecks.

82|23|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Rune-kit/rune --skill adversary-rune-kit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adversary
Source: https://github.com/Rune-kit/rune/tree/main/skills/adversary
Command: npx skills add https://github.com/Rune-kit/rune --skill adversary-rune-kit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill identifies critical flaws in plans before any code is written, preventing costly rework and ensuring robust designs.

Core Features & Use Cases

  • Pre-implementation Red-Teaming: Challenges plans for edge cases, security holes, scalability bottlenecks, error propagation, and integration conflicts.
  • Cost Reduction: Catches flaws at the planning stage, which is 10x cheaper than finding them during implementation.
  • Use Case: Before building a new authentication flow, run the adversary skill on the design document to uncover potential security vulnerabilities and race conditions that could be exploited.

Quick Start

Run the adversary skill on the plan file located at .rune/features/new_auth/plan.md.

Frequently Asked Questions about adversary

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

FAQPage Schema
How do I perform pre-implementation red-team analysis on a development plan?

Pre-implementation red-team analysis challenges development plans to identify edge cases, security vulnerabilities, scalability bottlenecks, and integration conflicts before code is written. This catches design flaws at the cheapest possible stage.

What is the best way to identify security vulnerabilities and error propagation risks before coding?

The best way to identify security vulnerabilities and error propagation risks before coding is running adversarial analysis across five dimensions on your plan document. This process uncovers flaws early, preventing costly rework during implementation.

How do I analyze a design document for scalability bottlenecks and integration conflicts?

To analyze a design document for scalability bottlenecks and integration conflicts, run an adversarial skill on the plan file. It evaluates the plan across multiple dimensions to expose hidden design weaknesses before development begins.

Does pre-implementation risk assessment require any specific dependencies or environments?

Pre-implementation risk assessment requires no external dependencies. It operates as a standalone script component, needing only your development plan file as input to perform the adversarial analysis.

When do I need to run adversarial plan analysis during the software engineering lifecycle?

You need to run adversarial plan analysis during the planning stage, before any code is written. Finding flaws at this stage is significantly cheaper than discovering security holes or race conditions during implementation.

What happens to critical security findings uncovered during plan analysis?

Critical security findings uncovered during plan analysis are escalated to the sentinel skill. This ensures severe vulnerabilities identified during the five-dimensional adversarial review receive appropriate downstream attention.