recheck-against-upstream-deeplisted

Escalate upstream-conformance discipline to a heavy fan-out: dispatch fresh-context subagents doc-by-doc over a whole subsystem, framework, or repo, comparing each surface against its CURRENT official upstream docs, then report an inline divergence ledger. Use when: 'recheck the whole subsystem against upstream', 'audit every surface against the docs', 'deep upstream conformance pass', 'check the entire framework config against upstream', 'we depend on a lot of upstream surfaces and they may have drifted'. For a single inline recheck of the surface in play, use the sibling recheck-against-upstream.
melodic-software/claude-code-plugins · ★ 13 · AI & Automation · score 73

Install: claude install-skill melodic-software/claude-code-plugins

# Recheck against upstream — deep The fan-out tier of the sibling `/discipline:recheck-against-upstream`. Same upstream-conformance discipline; heavier execution. Where the base skill rechecks the one surface in play inline, this one fans fresh-context subagents out over a whole subsystem, framework, or repo — doc-by-doc — the execution tier the base skill's context cannot cover from within itself. The shared method — re-anchor, audit, correct forward, report, and the tone that firing this is not an accusation — lives in [`${CLAUDE_PLUGIN_ROOT}/context/re-anchor-audit-correct.md`](../../context/re-anchor-audit-correct.md). The discipline this re-anchors, its portable baseline, and the three divergence categories (gap / deliberate / undocumented) live in the sibling [`recheck-against-upstream`](../recheck-against-upstream/SKILL.md). Read both; this file adds only the fan-out delta. There is no separate copy of the discipline or the taxonomy here — update the sibling and this tier follows. ## When this tier, not the inline recheck Reserve the fan-out for when the upstream surface area is broad enough to justify the subagent cost: a whole framework's configuration, an entire integration's API usage, a subsystem that leans on many upstream contracts at once. For a single surface or a short session, the inline recheck in the sibling is the right tool; this tier is overkill. ## The fan-out Run this in place of the sibling's inline audit and correct-forward steps: 1. **Enumer