iterative-retrieval

Refine codebase file retrieval through a 4-phase iterative loop.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/robinxin/AIFlomo --skill iterative-retrieval-robinxin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iterative-retrieval
Source: https://github.com/robinxin/AIFlomo/tree/main/.claude/skills/iterative-retrieval
Command: npx skills add https://github.com/robinxin/AIFlomo --skill iterative-retrieval-robinxin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Iterative retrieval addresses the "context problem" in multi-agent workflows where subagents don't know what context they need until they start working.

Core Features & Use Cases

  • 4-phase loop: Dispatch, Evaluate, Refine, LOOP to progressively narrow the search space.
  • Dynamic evaluation and refinement: scores relevance and updates criteria across cycles.
  • Practical examples: bug-fix context assembly for codebases; feature implementation scoping in large repos.

Quick Start

Run iterative retrieval to gather and refine relevant files for a given coding task.

Frequently Asked Questions about iterative-retrieval

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

FAQPage Schema
How do I find relevant files in a large codebase when I don't know the context needed?

Multi-agent workflows use iterative retrieval to dynamically gather and refine codebase context. It addresses the problem where subagents discover context requirements only after starting work, using a deterministic loop to progressively narrow the search space.

What's the best way to assemble context for debugging across a multi-agent workflow?

Bug-fix context assembly uses iterative retrieval to progressively refine codebase search results. By scoring relevance and updating criteria across a deterministic loop, it ensures subagents target the most relevant files for debugging.

How does iterative retrieval refine codebase search results across multiple cycles?

The 4-phase loop drives iterative retrieval by sequentially executing Dispatch, Evaluate, Refine, and LOOP phases. It dynamically scores file relevance and updates search criteria across up to three cycles before relevance-based termination.

Can I scope feature implementation in large repositories without knowing all dependencies upfront?

Feature implementation scoping in large repositories uses iterative retrieval to dynamically discover necessary context. It progressively narrows the codebase search space across cycles, allowing agents to locate relevant files without upfront dependency knowledge.

Does iterative retrieval work for multi-agent workflows requiring emergent context during execution?

Iterative retrieval targets multi-agent workflows requiring emergent context during execution. It applies progressive context refinement to help subagents dynamically locate relevant codebase files as task requirements evolve.

When should I avoid using iterative codebase retrieval?

Avoid iterative codebase retrieval for tasks requiring exhaustive file enumeration or strictly deterministic single-pass searches. It terminates after three cycles or when relevance scores peak, making it unsuitable for exhaustive repository scanning without dynamic evaluation.