prism-reflect

Analyze artifacts for structural problems and hidden constraints through reflective reasoning.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps analysts uncover hidden trade-offs, blind spots, and structural constraints that ordinary artifact reviews often miss.

Core Features & Use Cases

  • Structural Analysis: Examines artifacts through adversarial reasoning, transformation analysis, and conservation laws to identify deep problems.
  • Meta-Analysis: Reviews its own conclusions to expose limitations in the analytical approach and reveal overlooked factors.
  • Constraint Transparency: Produces reports showing what was optimized, what was sacrificed, and what additional investigations are recommended.

Quick Start

Ask the prism-reflect skill to analyze this artifact, identify hidden constraints, and generate a constraint transparency report.

Frequently Asked Questions about prism-reflect

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

FAQPage Schema
How do I identify hidden constraints and structural problems in a design evaluation?

Uncovering hidden constraints in a design evaluation requires multi-phase reflective reasoning and adversarial examination of artifacts. This structural analysis exposes deep trade-offs, blind spots, and limitations that ordinary reviews often miss.

What is meta-analysis in code review and how does it expose blind spots?

Meta-analysis in code review evaluates the conclusions of the review itself to expose limitations in the analytical approach. It applies adversarial reasoning to reveal overlooked factors and structural blind spots missed during initial assessment.

How do I generate a constraint transparency report for system analysis?

Generating a constraint transparency report for system analysis requires structured output detailing what was optimized, what was sacrificed, and recommended investigations. It tracks persistent constraints through multi-phase reflective reasoning.

Can I use reflective reasoning to review assumptions in software engineering artifacts?

Yes, reflective reasoning can review assumptions in software engineering artifacts by applying conservation laws and transformation analysis. It adversarially examines structural problems to validate and expose hidden system design constraints.

What are the limitations of relying on ordinary artifact reviews for structural analysis?

Ordinary artifact reviews lack meta-analysis and adversarial reasoning, causing them to miss deep structural problems. Without persistent constraint tracking and conservation laws, hidden trade-offs and analytical blind spots remain overlooked.