prism-full

Perform multi-pass adversarial analysis of artifacts and synthesize surviving findings.

Updated May 5, 2026
One-click install
npx skills add https://github.com/yanochka11/harness_bro --skill prism-full-yanochka11
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prism-full
Source: https://github.com/yanochka11/harness_bro/tree/main/.claude/skills/curated/meta/super-hermes/skills/prism-full
Command: npx skills add https://github.com/yanochka11/harness_bro --skill prism-full-yanochka11

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of shallow artifact analysis by forcing structured multi-pass investigation, self-critique, and synthesis to reveal deeper issues and resilient findings.

Core Features & Use Cases

  • Custom Analysis Pipelines: Designs tailored analytical passes for the specific artifact being examined.
  • Adversarial Self-Correction: Challenges previous conclusions by testing assumptions, identifying overclaims, and adding missed insights.
  • Use Case: Analyze an important codebase, design document, or technical artifact where reliability and deep structural understanding are required.

Quick Start

Use the prism-full skill to perform a deep multi-pass adversarial analysis of the provided artifact and produce reconciled findings.

Frequently Asked Questions about prism-full

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

FAQPage Schema
How do I perform a deep structural analysis to find hidden flaws in a codebase?

Deep structural analysis uncovers hidden flaws by designing tailored analytical pipelines, executing iterative reviews, and applying adversarial self-correction to validate assumptions before synthesizing only resilient findings.

What is adversarial reasoning and how does it improve code review confidence?

Adversarial reasoning improves code review confidence by challenging previous conclusions, testing underlying assumptions, identifying overclaims, and surfacing missed insights through multi-pass validation.

Can I use multi-pass analysis for technical documents and system designs?

Yes, multi-pass analysis applies to technical documents and system designs alongside codebases, utilizing custom analytical pipelines to deeply investigate structural artifacts and reconcile final findings.

How do I design an analysis pipeline for artifact evaluation?

Designing an analysis pipeline involves creating tailored analytical passes for the specific artifact, executing chained analysis steps, and validating outputs through adversarial critique to ensure reliable evaluation.

What is the best way to validate technical assumptions during a code review?

The best way to validate technical assumptions is using adversarial self-correction, which actively tests existing conclusions, identifies overclaims, and filters out weak findings through iterative structural critique.

Why does shallow artifact analysis fail to catch complex design issues?

Shallow artifact analysis fails to catch complex design issues because it lacks structured multi-pass investigation and adversarial validation, meaning hidden assumptions and structural flaws remain unchallenged.