wusanto-blindspot

Review AI-generated specifications for falsifiable verification criteria.

Updated Jul 26, 2026
One-click install
npx skills add https://github.com/fagemx/wusanto --skill wusanto-blindspot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wusanto-blindspot
Source: https://github.com/fagemx/wusanto/tree/main/skills/wusanto-blindspot
Command: npx skills add https://github.com/fagemx/wusanto --skill wusanto-blindspot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill mitigates the risk of AI-generated work being accepted without proper verification, preventing errors caused by literal interpretation or vague mission requirements.

Core Features & Use Cases

  • Adversarial Review: Uses persona-based cards to identify potential failure points in mission wishes, specifications, and handoffs.
  • Falsifier-Driven Findings: Ensures every concern raised is testable and actionable, preventing vague feedback.
  • Use Case: Before accepting a complex coding task from an AI agent, run this skill to check if the agent's plan relies on in-loop self-verification that might fail to catch real-world errors.

Quick Start

Use the wusanto-blindspot skill to perform an adversarial review on the current PlanningPack and identify potential risks before proceeding.

Frequently Asked Questions about wusanto-blindspot

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

FAQPage Schema
How do I perform an adversarial review on AI-generated artifacts to find logical gaps?

Adversarial review of AI-generated artifacts is performed using persona-based analysis to identify potential failure points and logical gaps in mission wishes, specifications, and handoff documents. This ensures verification criteria are robust and falsifiable.

Why does AI-generated code fail verification when using in-loop self-verification?

AI-generated code fails verification because in-loop self-verification relies solely on the executing agent's own judgment, which can miss real-world errors caused by literal interpretation or vague mission requirements. Adversarial review mitigates this risk.

What is the best way to ensure acceptance criteria for AI coding tasks are falsifiable?

The best way to ensure acceptance criteria are falsifiable is to apply falsifier-driven findings during an adversarial review. This guarantees every concern raised is testable and actionable, preventing vague feedback from being accepted.

Can I use persona-based analysis to validate handoff documents before accepting complex coding tasks?

Yes, you can use persona-based analysis to validate handoff documents before accepting complex coding tasks. It checks if the agent's plan relies on in-loop self-verification that might fail to catch real-world errors.

When do I need to run an adversarial review on a PlanningPack?

You need to run an adversarial review on a PlanningPack before proceeding with a complex coding task from an AI agent. This identifies potential risks and verifies that the mission requirements are robust and not vaguely defined.

What are the limitations of relying solely on an executing agent's judgment for quality assurance?

Relying solely on an executing agent's judgment for quality assurance risks accepting AI-generated work without proper verification. This leads to errors from literal interpretation or vague requirements, which adversarial review with external personas is designed to catch.