Oleks
e3b67e9716
commands/offload-audit.md cited 'spec §7' for the one-agent-per-audit rule;
that constraint now has a real home at FR-8.3 (added alongside the recursion
fix, commit 06cb5b8) and the file was out of spec-review's scope to touch.
tasks.md 8.4 predates FR-9 and still pointed a manual memory checkpoint at
wing_claude_memory/working-practice, while FR-9.3's shipped wing/room split
routes the same kind of cross-target judgment to claude-plugins/
inference-arbitrage-lessons via bin/audit-snapshot memory-notes. Two
destinations for one category of content defeats the point of a single
accumulating room, so 8.4 now points at the one the automated path already
writes to.
Suite: unchanged, exit 0 on all tests.
30 lines
1.7 KiB
Markdown
30 lines
1.7 KiB
Markdown
---
|
|
description: Audit a Claude Code plugin for steps that should be a deterministic script instead of raw inference — measure, classify, file the well-evidenced candidates, and write the run summary. Usage — /offload-audit <plugin|path> [--days N]
|
|
argument-hint: <plugin name or path> [--days N]
|
|
allowed-tools: ["Bash", "Read", "Grep", "Glob", "Skill", "Agent"]
|
|
---
|
|
|
|
# /offload-audit
|
|
|
|
Run the full audit on **$ARGUMENTS**.
|
|
|
|
1. Parse `$ARGUMENTS` into a target (a plugin name or a directory path) and an
|
|
optional `--days N` window, defaulting to 30.
|
|
2. If no target was given, ask which plugin to audit. Do not guess one, and do
|
|
not default to the current directory — auditing the wrong plugin wastes a
|
|
full transcript scan.
|
|
3. Invoke the `offload-audit` skill and follow it exactly, including both filing
|
|
gates (the overrule case, FR-4.2; the evidence-stability check against the
|
|
previous window, FR-4.5) and the marker search. For a heavy target, or when
|
|
the report should not consume this session's context, hand the work to
|
|
`Agent(subagent_type="inference-arbitrage:offload-analyst")` instead — one
|
|
agent for the whole audit, never one per skill (FR-8.3). **This delegation
|
|
happens at most once, from this top-level command to the analyst.** The
|
|
analyst instance you spawn is the delegation target, not another decision
|
|
point — it never re-delegates the whole audit to a further `offload-analyst`
|
|
instance, however large the target looks from inside.
|
|
|
|
Filing is implicit: a candidate that clears the rubric gate and the value
|
|
threshold is filed without asking. Everything below the gate is reported as a
|
|
boundary question and filed nowhere.
|