Enter planning mode. Audit the query tools in tools/ for fitness. Use parallelism where possible.

Context

Query tools (tools/query_*.ps1) exist to give structured answers without loading full files into context. CLAUDE.md lists only the most-used tools — niche tools are intentionally omitted to save per-session context, but they're still referenced by skills when relevant. "Unused by CLAUDE.md" does NOT mean unused.

Current Inventory

Audit Steps

1. Accuracy — do tools match the codebase?

Run each query_*.ps1 tool with no args (or a known-good sample query) and check:

• Does the output parse the current file format correctly?
• Have any source files been renamed, restructured, or split since the tool was written?
• Are regex patterns still matching the right constructs?

Flag tools that produce silently wrong output (no errors, but stale/incorrect data). A tool that errors loudly is less dangerous than one that lies quietly.

2. Gaps — are there new "load big file to find small answer" patterns?

Look for patterns in the codebase that suggest a missing tool:

• Files over 300 lines where agents typically only need a small slice
• Common grep patterns that could return structured answers instead of raw lines
• Questions that require cross-referencing multiple files (e.g., "who sends message X and who handles it" — query_messages.ps1 already covers this for WM_ messages; is there an equivalent need for other patterns?)

The bar: would a new tool save >50 lines of context per use? If not, grep is fine.

3. Retirement — are any tools dead weight?

A tool nobody invokes is dead code with maintenance cost. Check:

• Is the tool referenced by any skill in .claude/skills/?
• Is the tool listed in CLAUDE.md?
• Does the tool's domain still exist in the codebase? (e.g., if a subsystem was removed, its query tool should go too)

Note: a tool referenced only by skills (not CLAUDE.md) is NOT a retirement candidate — it's a niche tool by design.

4. Cross-references — could existing skills benefit from niche tools?

Check each skill in .claude/skills/ — could any benefit from referencing a query tool they don't currently mention? Skills only load on invocation, so adding a niche tool reference costs zero per-session context.

Plan Format

Section 1 — Accuracy issues (tools producing wrong output):

Section 2 — Gap candidates (potential new tools):

Section 3 — Retirement candidates (genuinely unused):

Section 4 — Skill cross-references (niche tools that skills should mention):

Ignore any existing plans — create a fresh one.