adversarial-review

Reviews OpenSpec implementations adversarially against specs, tests, and ecommerce domain rules before archiving.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/Marcel-Carrillo/ProyectosIA --skill adversarial-review-marcel-carrillo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adversarial-review
Source: https://github.com/Marcel-Carrillo/ProyectosIA/tree/main/ai-specs/skills/adversarial-review
Command: npx skills add https://github.com/Marcel-Carrillo/ProyectosIA --skill adversarial-review-marcel-carrillo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Implemented changes often pass happy-path tests while hiding spec drift, missing edge cases, or data exposure risks. This Skill performs an independent adversarial review of an OpenSpec change after implementation and local verification, producing a severity-classified findings report and a clear archive verdict. ## Core Features & Use Cases - Spec and Task Alignment Audit: Compares implementation against proposal.md, design.md, and tasks.md to detect spec drift, incomplete tasks, and missing verification reports. - Ecommerce Domain Rule Checks: Verifies CustomerOrder vs SupplierOrder separation, ProductVariant as sellable unit, supplier data exposure, status separation, and purchase-time snapshot behavior. - Severity-Classified Verdict: Classifies findings as Blocker, Major, Minor, or Question and ends with a PASS, PASS WITH GAPS, or FAIL verdict plus an archiving recommendation. - Use Case: After finishing a checkout endpoint implementation, run this review from a fresh session to catch that supplier costs leak into a customer-facing API response before archiving the change. ## Quick Start Ask the AI to run an adversarial review on the OpenSpec change you just implemented and verified, before archiving it.

Frequently Asked Questions about adversarial-review

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

FAQPage Schema
How do I run an adversarial review on an OpenSpec change?▼

Provide the OpenSpec change name, feature, endpoint, or branch after implementation and local verification are complete. The review reads the change artifacts, git diff, and test evidence, then outputs findings and a verdict. Running it from a different session than the implementer is recommended.

What does an adversarial code review check before archiving?▼

It checks spec and task alignment, missing negative paths and edge cases, test coverage gaps, and ecommerce rules like supplier data exposure and order status separation. Findings are classified as Blocker, Major, Minor, or Question with a final PASS or FAIL verdict.

Does this review require Jira, Sentry, or GitHub access?▼

No external tools are required. The review works fully offline using local files, git diff, tests, curl reports, and OpenSpec artifacts. Jira, Sentry, Playwright MCP, and GitHub PR review are optional and only used when explicitly requested.

When should I run the adversarial review in the workflow?▼

Run it in the verification window: after implementation and after local verification, but before archiving the OpenSpec change. It is not a replacement for writing tests or implementing fixes.

Can the adversarial review fix the issues it finds?▼

No, the review only reports findings with suggested fix locations such as code, tests, or spec artifacts. It does not implement fixes, create commits, or archive changes unless the user explicitly asks for fixes afterward.