IterativeDepth

Runs 2-8 structured lens passes over a problem to surface hidden requirements and ISC criteria.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/Kaleb-Rupe/aurora --skill iterativedepth-kaleb-rupe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: IterativeDepth
Source: https://github.com/Kaleb-Rupe/aurora/tree/main/claude/skills/Thinking/IterativeDepth
Command: npx skills add https://github.com/Kaleb-Rupe/aurora --skill iterativedepth-kaleb-rupe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Single-pass analysis of a problem or request often misses requirements, edge cases, and stakeholder needs that only become visible from other angles. This Skill applies structured multi-angle exploration so requirement extraction produces richer, more complete ISC criteria before work begins. ## Core Features & Use Cases - Eight Structured Lenses: Literal, Stakeholder, Failure, Temporal, Experiential, Constraint Inversion, Analogical, and Meta perspectives grounded in 20 established techniques from cognitive science, AI/ML, requirements engineering, and design thinking. - Depth Scaling by SLA: Fast mode runs 2 lenses inline, Standard runs 4 with parallel background agents, and Deep runs all 8 with agent parallelization. - Use Case: Before scoping an ambiguous feature request, run iterative depth to discover anti-criteria, failure modes, and stakeholder needs that a single reading of the request would never reveal, then feed the enriched criteria into task creation. ## Quick Start Ask the assistant to use iterative depth on your problem statement to explore it from multiple angles and surface hidden requirements.

Frequently Asked Questions about IterativeDepth

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

FAQPage Schema
How do I run multi-angle analysis on a problem before planning?

Invoke iterative depth on the problem statement and it runs 2-8 structured lens passes, each examining the same problem from a different angle such as stakeholder needs or failure modes. The findings are synthesized into deduplicated ISC criteria.

What lenses does iterative depth analysis use?

It uses eight lenses: Literal, Stakeholder, Failure, Temporal, Experiential, Constraint Inversion, Analogical, and Meta. Each is grounded in established techniques like Six Thinking Hats, Misuse Cases, and Viewpoint-Oriented Requirements Engineering.

How many passes should I use for requirement exploration?

Depth is set by SLA or explicit request: Fast runs 2 lenses, Standard runs 4, and Deep runs all 8. You can also specify an exact number between 2 and 8, and lenses are selected in order of general applicability.

Can iterative depth run analysis passes in parallel?

Yes. Standard mode runs the first two lenses inline and spawns background agents for the rest, while Deep mode spawns paired or individual agents per lens. Each agent receives the problem, its lens definition, and criteria found so far.

When should I not use multi-pass requirement analysis?

Skip it for Instant SLA tasks where speed matters more than completeness, since the workflow returns immediately. It is designed for problems where hidden requirements carry real cost, not trivial or fully specified requests.