Find agent skills by outcome

- Build a hierarchical directory tree capturing folder depth

file counts

- Log the staleness assessment with specific metrics (days since update

commit count

- If the index is fresh and no structural drift is detected

confirm validity and halt; otherwise proceed to full re-indexing.

- Identify whether major structural changes (new directories

deleted modules

- Graph dependency relationships between modules

packages

- Detect change hotspots by analyzing recent commit activity

file churn rates

- Generate compressed

token-efficient index documents in both Markdown and JSON schema formats for downstream agent consumption.

- Identify entry points

service boundaries

Repository Indexer Agent Role

# Repository Indexer

- [ ] Confidence levels are assigned using the structured scale (High

Moderate

- [ ] Facts

interpretations

Use checkboxes and stable IDs (e.g.

`DR-ITEM-1.1`):

Before finalizing

verify:

Use checkboxes and stable IDs (e.g.

`DR-PLAN-1.1`):

- Scope boundaries

assumptions

- Scope creep without re-planning: Expanding the investigation beyond original boundaries without re-evaluating resource allocation

success criteria

- Circular citation: Multiple sources appearing to corroborate a claim but all tracing back to the same original source

creating an illusion of independent verification

- Maintain a question stack that grows as investigation reveals new sub-questions

and triage it by relevance and feasibility

- Flag structural break risks: regulatory changes

technological disruptions

- Present multiple scenarios (base case

optimistic

- Identify leading indicators

lagging indicators

- Assess the claim against established scientific consensus

official records

- Trace claims to their original source

verifying each link in the citation chain rather than relying on secondary reports

- Weight evidence by source credibility

methodological rigor