Assumes Claude's competence (uses SIGINT/OSINT/HUMINT/FININT/TECHINT without over-explaining, no basic-concept padding), but includes rhetorical flourishes that could be trimmed — 'regenerating the same report weekly is theater', 'a watch that cries wolf gets ignored by cycle three — the bar is what keeps the audience' — matching the mostly-efficient-but-could-be-tightened anchor; not 3 because those motivational asides don't each earn their tokens.

Provides a copy-paste-ready output schema with fill-in slots, six sequenced Application steps, a 4-option Final Step, and specific worked examples (a bar-clearing changelog entry and the empty changelog), matching the anchor for specific, copy-paste-ready guidance; not 2 because the guidance is complete and concrete rather than pseudocode-level.

Clear six-step sequence with explicit checkpoints — a search-plan gate ('Continue unless revised'), the materiality-bar filter, Fact/Inference/Assumption labels — and the output schema acting as a checklist, matching the clear-sequence-with-checkpoints anchor; not 2 because validation/quality gates are explicit, and the task is not a destructive/batch operation requiring a fix-retry loop.

Body is organized into clear sections and offloads the fill-in template to template.md and worked runs to examples/sample.md and examples/sample-industrial.md as one-level-deep, clearly signaled references, matching the well-signaled-one-level-deep anchor; not 2 because content is appropriately split rather than inlined. (The referenced bundle files are not present in this review directory to physically verify, but the in-body structure is sound.)

Lists multiple concrete capabilities ('delta monitoring against a prior competitive snapshot', 'cited evidence', 'battle-card update flags', 'runs unattended') rather than vague language, matching the anchor for several specific concrete actions; not 2 because the action coverage is comprehensive rather than partial.

Clearly answers both what it does ('Scheduled delta monitoring against a prior competitive snapshot...material shifts only, cited evidence, battle-card update flags') and when to use it via an explicit 'Use when tracking competitors on a cadence' trigger, matching the anchor for both what and when with explicit triggers.

'Use when tracking competitors on a cadence' is a natural trigger, but coverage is thin and misses common variations a user would say ('competitor watch', 'what changed', 'monitor competitors'), matching the anchor for some relevant keywords with missing variations; not 3 due to limited breadth.

Occupies a clear niche (delta monitoring against a prior snapshot with battle-card update flags) with distinct triggers unlikely to fire for unrelated skills, matching the clear-niche anchor; not 2 because the delta/battle-card framing is specific rather than overlapping.