iterative-depth

Run 2–8 structured lens passes to refine binary-testable requirements.

7|2|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/ajbmachon/ajbm-skills --skill iterative-depth-ajbmachon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iterative-depth
Source: https://github.com/ajbmachon/ajbm-skills/tree/main/plugins/development-skills/skills/thinking/iterative-depth
Command: npx skills add https://github.com/ajbmachon/ajbm-skills --skill iterative-depth-ajbmachon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Iterative depth helps you miss fewer requirements by exploring the same problem through multiple structured perspectives, surfacing constraints, risks, stakeholders, and success criteria that single-pass analysis often overlooks.

Core Features & Use Cases

  • Lens-based multi-pass exploration: Runs 2–8 passes over the same problem using fundamentally different lenses to generate and refine criteria.
  • Time-budgeted depth control: Uses short/medium/long budgets (or a user-specified pass count) to scale coverage without wasting effort.
  • Requirement synthesis with deduplication: Merges and prioritizes new and refined criteria across lenses, including anti-criteria.
  • Routing for common intent: Triggers map “iterative depth / explore deeper / multi-angle” and “quick depth / fast angles” to the correct workflow mode.
  • Example use cases: Turning an ambiguous request into actionable requirements, improving planning/engineering acceptance criteria, and strengthening reviews by explicitly enumerating failures and edge cases.

Quick Start

Ask Claude Code to use iterative depth on your problem and request a specific time budget or number of passes to generate enriched success criteria.

Frequently Asked Questions about iterative-depth

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

FAQPage Schema
How do I extract richer requirements from an ambiguous project request?

Multi-angle requirement elicitation extracts richer criteria by running 2 to 8 structured exploration passes over the same problem using fundamentally different lenses. This iterative depth approach surfaces hidden constraints, risks, and stakeholders that single-pass analysis often overlooks.

What is the best way to create binary-testable acceptance criteria for software planning?

Applying iterative multi-pass analysis to software planning generates refined binary-testable success criteria and anti-criteria. By merging and prioritizing new requirements across different analytical lenses with deduplication, it ensures comprehensive acceptance criteria coverage.

How does multi-angle analysis improve risk assessment and debugging workflows?

Multi-angle analysis improves risk assessment and debugging by exploring the same problem through multiple structured perspectives. This lens-based approach explicitly enumerates potential failures and edge cases, strengthening reviews and hypothesis generation that single-pass workflows miss.

Can I control the depth and time budget of requirement exploration passes?

You can control requirement exploration depth using short, medium, or long time budgets, or by requesting a specific pass count. This time-budgeted routing scales coverage across 2 to 8 lens passes without wasting effort.

When do I need iterative depth for deep requirement elicitation instead of standard analysis?

You need iterative depth when standard single-pass analysis overlooks constraints, stakeholders, or success criteria. It is specifically designed for ambiguous requests, planning, criterion creation, and deep requirement elicitation where missing edge cases or failures is costly.

Are there limitations to using lens-based multi-pass exploration for decision support?

Lens-based multi-pass exploration for decision support requires allocating sufficient time budgets for multiple passes to be effective. While it scales coverage without wasting effort, users must specify appropriate pass counts to avoid incomplete deduplication and prioritized synthesis of refined criteria.