Structured multi-angle exploration running 2-8 sequential passes over the same problem, each through a different scientific lens, to surface hidden requirements and edge cases invisible from one angle; each pass yields new ISC criteria
When you ask an AI to analyze a problem, it runs one pass and gives you the obvious answer — the surface requirements, the happy path, the constraints the user mentioned. That's it. Everything invisible from that single angle stays invisible: the stakeholder who wasn't in the room, the failure mode that only shows up under load, the implicit assumption that makes the whole approach wrong in six months. Single-pass analysis is fast, but the missed requirements are what blow up mid-execution.
IterativeDepth runs 2–8 sequential passes through the same problem, each from a structurally different lens. Lens 1 extracts what was literally said. Lens 2 asks who else is affected. Lens 3 assumes the solution shipped and looks for what breaks. Lens 4 examines what changes over time. Lens 5 asks how it should feel. Lens 6 inverts constraints to surface hidden assumptions. Each pass outputs new ISC criteria the previous passes couldn't see — the Explore workflow runs all passes, stops when yields repeat, and feeds the combined criteria into the ISA. The technique draws from validated work across 20 frameworks: Gadamer's hermeneutic circle for progressive pre-understanding, de Bono's Six Thinking Hats for structured angle rotation, Wang et al.'s Self-Consistency for why multiple reasoning paths beat one, and Finkelstein's Viewpoint-Oriented Requirements Engineering for the stakeholder lens.
What you say to your DA, and what the IterativeDepth skill actually does.
The thinking, frameworks, and architecture that distinguish this skill from a generic version of the same task.
IterativeDepth examines one problem through several structurally different lenses — literal, stakeholder, failure, temporal, and more — merging what each angle surfaces into ISC criteria a single pass misses. Grounded in 20 established techniques across cognitive science, AI/ML, requirements engineering, and design thinking (see ScientificFoundation.md).
A done run produces:
Passes stop when a new lens repeats what earlier lenses already found. Non-redundant angles are what matter; more angles for their own sake are not.
TheLenses.md is a catalog of eight exploration angles. Draw from it — pick the lenses the problem calls for, in whatever order, as many as earn their keep. No fixed count, no prescribed sequence: a security problem leans on the failure and adversary angles, a UX problem on the experiential one. Let the problem select the lenses.
TheLenses.mdScientificFoundation.mdEach workflow is one job the skill runs. The trigger phrases route your request to the right one — this is the skill's routing table.
Workflows/Explore.md iterative depth, explore deeper, multi-angle
Say any of these to your DA and LifeOS activates the IterativeDepth skill automatically:
Or invoke explicitly:
Skill("IterativeDepth")Auxiliary files the skill loads at runtime — frameworks, guides, configs.
The thinkers, books, frameworks, and research this skill is built on. The ideas belong to them — the integration belongs to LifeOS.
Install LifeOS on your machine — your DA gets the IterativeDepth skill plus 46 others, all hooked into one Life OS.