The body adds genuine domain expertise Claude lacks, but the 'ritual vs analytical tool' theme is restated in the intro, the 'adds clarity vs ritual' section, failure modes, the 12 considerations, and the closing, and the closing largely restates the opening. Not 3 because this redundancy could be tightened; not 1 because it is not padded with concepts Claude already knows.

Provides concrete artifacts — a job-statement template with three worked examples, specific interview prompts ('Walk me through the last time you did X'), hire/fire criteria lists, and a 12-point audit checklist — but a large portion is conceptual framing and diagnosis rather than step-by-step executable instruction. Not 3 because guidance is embedded in framing prose rather than copy-paste-ready throughout; not 1 because concrete templates and prompts are present.

Sequences exist (the discovery section: structure interviews around struggling moments → gather job statements after → cluster → name) and a litmus test acts as a checkpoint, but checkpoints are mostly implicit and the multi-mode methodology lacks a tightly sequenced end-to-end flow. Not 3 because validation checkpoints are not explicit; not 1 because steps and an audit checklist are present.

A clear overview body pointing to 8 well-signaled, one-level-deep reference files via 'Detail in [references/...]' links, plus a consolidated 'Reference files' index; all referenced files exist. Matches the 3 anchor: clear overview, appropriately split, easy navigation, no nested references.

Lists multiple specific concrete capabilities — 'Job statements, struggling moments, hire and fire criteria, the difference between feature-thinking and job-thinking' — rather than vague language. Not the 2 anchor because it is comprehensive across the methodology's deliverables, not just naming the domain.

Explicitly answers what ('The Jobs-to-be-Done framework as applied product methodology...') and when ('Triggers on...', 'Also triggers when a team is over-relying on feature-request lists...'). Not capped at 2 because explicit trigger guidance is present, equivalent to a 'Use when' clause.

'Triggers on jobs-to-be-done, JTBD, job statements, struggling moments, hire criteria, fire criteria, switch triggers, functional emotional social jobs, outcome-driven innovation' gives good coverage of the natural terms a PM would actually say, including common variations. Not 2 because both the canonical term and abbreviations plus situational triggers are present.

A clear JTBD niche with distinct, methodology-specific triggers (job statements, hire/fire criteria, struggling moments) unlikely to fire for unrelated skills. Not 2 because the triggers are specific to JTBD rather than overlapping with generic product/synthesis skills.