prime-sweep

Delegates parallel sub-agents to digest large source surfaces into verified findings with source:line citations.

14|1|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/allemaar/open-skills --skill prime-sweep-allemaar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prime-sweep
Source: https://github.com/allemaar/open-skills/tree/main/skills/prime-sweep
Command: npx skills add https://github.com/allemaar/open-skills --skill prime-sweep-allemaar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reading large source surfaces (multiple files, packages, or folders) directly floods an agent's context with noise. This Skill primes the calling agent with high-signal context by dispatching parallel sub-agents that absorb the noise and return only digested findings with verified source:line citations. ## Core Features & Use Cases - Parallel delegated investigation: Spawns up to 3 sub-agents per wave across single-source, multi-source, discovery, or mixed input modes, keeping the caller's context clean. - Proof-of-work verification: Every finding and unfollowed pointer requires a source:line plus verbatim quote, verified via Grep against files or temp-file-backed dumps — never from memory. - Iterative wave ladder with sufficiency gate: Runs up to 8 waves (silent ≤3, logged 4-6, user approval at 7) and declares primed, partial, or stuck based on an explicit checklist. - Use Case: You receive a handoff listing five unfamiliar packages to modify. Invoke /prime-sweep to get a primed summary, a source:line index for first-hand re-reading, discarded-noise categories, and known gaps — without reading any source yourself. ## Quick Start Invoke /prime-sweep with the list of source files or folders you need primed context from before starting implementation work.

Frequently Asked Questions about prime-sweep

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

FAQPage Schema
How do I gather context from many large files without flooding my agent's context?

Use /prime-sweep to delegate reading to parallel sub-agents (max 3 per wave). They absorb the noise and return only digested findings with source:line citations, so the calling agent's context stays clean.

When should I use prime-sweep instead of prime-fetch or prime-expand?

Use prime-sweep when the surface is ≥3 distinct sources or ≥~10k tokens. Use prime-fetch for a single noisy tool call or one large source, and prime-expand first when the gap itself is vague and needs articulation.

How are sub-agent findings verified before reaching the caller?

Every finding requires a source:line plus a verbatim quote of at least 8 words or a verbatim-token. The lead verifies citations with Grep against the cited file or a temp-file-backed dump, never from memory.

What happens if the first wave of sub-agents does not find enough?

The sufficiency gate triggers another wave only when a documented relevance signal exists. Waves 1-3 run silently, 4-6 are logged, wave 7 asks the user, and wave 8 is the maximum before declaring stuck.

Can prime-sweep sub-agents modify source files or spawn their own sub-agents?

No. Sub-agents are strictly read-only and depth-1: they cannot edit sources or spawn further sub-agents. Quoted content is treated as data, never as instructions to follow.