prism-discover

Identifies 10-20 distinct analytical domains for artifacts before deep-dive analysis.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of tunnel vision when analyzing complex artifacts by forcing a comprehensive, multi-dimensional exploration of potential investigation domains.

Core Features & Use Cases

  • Domain Discovery: Identifies 10-20 distinct analytical lenses ranging from technical architecture to psychological and regulatory implications.
  • Strategic Framing: Helps users decide which specific areas of an artifact warrant a deep dive before committing to full-scale analysis.
  • Use Case: Before performing a security audit on a new codebase, use this skill to identify that you should also be looking at documentation strategy and team scaling assumptions.

Quick Start

Use the prism-discover skill to list all possible analytical domains for the current project file.

Frequently Asked Questions about prism-discover

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

FAQPage Schema
How do I uncover hidden analytical angles for a technical artifact?

Multi-perspective analysis prevents tunnel vision by mapping 10-20 distinct analytical domains, from technical architecture to regulatory implications. This structured domain mapping ensures you uncover non-obvious investigation angles before committing to a deep-dive evaluation.

What is the best way to frame strategic analysis before a deep dive?

Strategic framing requires high-level domain mapping to identify which specific areas of an artifact warrant a deep dive. Applying this structured exploration before full-scale analysis prevents tunnel vision across codebases, business plans, and technical documentation.

Can I use multi-perspective analysis on both codebases and business plans?

Yes, you can apply multi-perspective domain discovery to codebases, business plans, and technical documentation. The process identifies diverse analytical domains across these artifacts to facilitate comprehensive evaluation of non-obvious investigation angles.

How do I identify analytical domains before performing a security audit?

Identify analytical domains by applying structured domain mapping prior to the audit. This reveals non-obvious investigation angles, showing that a codebase security audit should also evaluate documentation strategy and team scaling assumptions.

Are there limitations to using high-level domain mapping for artifact evaluation?

High-level domain mapping provides strategic framing and domain discovery, but does not perform the deep-dive investigation itself. It satisfies the requirement for structured mapping prior to analysis, requiring downstream tools for detailed evaluation.