iterative-retrieval

Orchestrate a 4-phase iterative retrieval loop to refine subagent codebase context.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Subagents often lack the necessary codebase context at startup, leading to incomplete or incorrect task execution. This Skill provides a structured iterative retrieval process to progressively gather relevant files and information.

Core Features & Use Cases

  • Iterative retrieval loop: 4-phase cycle (DISPATCH, EVALUATE, REFINE, LOOP) to refine search context.
  • Gated quality: requires 3 high-relevance files and considers gaps before proceeding.
  • Practical scenarios: debugging, codebase exploration, multi-agent orchestration where context is dynamic.

Quick Start

Initiate an iterative retrieval session by describing your task and let the agent search, evaluate, and refine context for up to three cycles.

Frequently Asked Questions about iterative-retrieval

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

FAQPage Schema
How do I gather unknown codebase context for subagents at runtime?

Gather unknown codebase context for subagents by running an iterative retrieval loop. This process progressively discovers relevant files through a 4-phase cycle of dispatching, evaluating, refining, and looping until enough context is collected.

What is the best way to refine subagent context in large codebases?

Refine subagent context in large codebases by applying a structured 4-phase retrieval loop. It evaluates relevance scores and identifies gaps across up to three cycles to progressively discover necessary files.

How does iterative retrieval determine when enough context is gathered?

Iterative retrieval determines enough context is gathered by applying gated quality checks. The mechanism requires identifying at least three high-relevance files and resolving context gaps before exiting the loop.

Can I use iterative retrieval for multi-agent workflows with dynamic context?

Iterative retrieval is designed for multi-agent workflows with dynamic context. It orchestrates progressive discovery for scenarios like debugging and codebase exploration where startup context is unknown.

What are the limitations of using a fixed cycle limit for codebase context refinement?

A fixed cycle limit for context refinement restricts discovery to a maximum of three loops. If the codebase is excessively large and scattered, the gated requirement of three high-relevance files might not be met within this constraint.

Do I need specific dependencies to implement progressive context discovery?

No specific dependencies are required to implement progressive context discovery. The mechanism operates as a standalone orchestration loop using standard subagent dispatch and evaluation techniques.