---
description: Sweep the transcript corpus for something and build a cited report
---

Call the `mcp__archilyzer__sweep_plan` tool with this exact `request` string,
passed through **verbatim and unsplit**:

$ARGUMENTS

Then follow the plan it returns, starting with its ⚠ warnings if it has any.

<!--
Why this file exists
--------------------
Claude Code parses an MCP *prompt*'s arguments as `text.trim().split(/\s+/)`
zipped against the declared argument names. It is not quote-aware, the last
argument does not absorb the remainder, and tokens past the declared count are
dropped silently. With the nine arguments the `sweep` prompt declares, a real
request became link="This" channel="search" group="deleted" directive="videos."
batch_size="Why" — and everything from the actual question onward vanished.

`$ARGUMENTS` in a slash command is different: it is replaced with the entire
raw argument string, untokenised, so URLs, `?`, `=`, `&` and punctuation all
survive. A tool argument is structured JSON, so it arrives intact from there.

Two things to keep in mind when editing this file:

  - Do NOT also use `$1` / positional placeholders in this body. Those DO
    tokenize, and mixing them re-introduces the bug this file exists to avoid.
  - The tool name embeds the MCP server name **as registered on this machine**
    (`archilyzer`). If you registered the server under another name, change the
    `mcp__<name>__sweep_plan` prefix to match. `foo:bar` namespacing is
    plugin-only, so the command you type is `/sweep`, not `/archilyzer:sweep`.

The sweep discipline itself — citation format, extractor budget, base-link
expansion, the coverage rule — deliberately lives in the server
(`mcp/src/instructions.ts`), not here, so it cannot drift out of sync with the
tools it names.
-->