Diagnostic Tool Skill

What This Is

A Diagnostic Tool sorts someone into one of 3–5 categories — then shows them where they are in a progression, what's keeping them stuck there, and what the next stage requires.

This is NOT a revelation tool (which surfaces what they already have) or a calculator (which computes a number). A revelation tool says "you have more than you thought." A diagnostic says "you're stuck at Stage 2 — here's why, and here's what Stage 3 requires."

The value is the sort. They didn't know which category they were in. Now they do — and the category name reframes the problem.

When to Use This Tool Type

Use a Diagnostic when:

• The person doesn't know which version of the problem they have
• There are 3–5 meaningfully different categories that require different responses
• The categories form a natural progression (Stage 1 → Stage 4) or represent distinct types
• The offer addresses different stages differently — the copy needs to change based on where they are

Do NOT use when:

• The insight is "you have more than you thought" (use a Revelation Tool)
• The person needs their own numbers calculated (use a Calculator)
• There's really only one answer and the questions are theater (that's a quiz, not a diagnostic)
• The categories aren't meaningfully distinct — if the advice is the same for every result, the tool is pointless

Architecture

HERO (context + promise)
    ↓
INTRO SCREEN (frames what the tool does, sets expectation, intentional entry)
    ↓
Q1–Q5: SINGLE-SELECT (each answer maps to one category)
    ↓
RESULTS PAGE
    → Category label (color-coded, e.g. "Your Result: Not Documented")
    → Diagnostic title (personalized to their category)
    → Chain visualization (shows all stages, highlights "you are here")
    → "What this means" (explanation of their category)
    → "What to do next" (action specific to their stage)
    → "What keeps practices stuck here" (the blocker — this is the sales mechanism)
    → Bridge to companion tool (cross-link to another campaign asset)
    → Offer bridge (stage-specific copy connecting their blocker to the paid service)
    → CTA
    → Disclaimer
    → Retake button

The Critical Pattern: Category Sorting

This is what makes a diagnostic work. Every question sorts, and the sorting must:

1. Map each option to exactly one category. Option A = Category 1, Option B = Category 2, etc. No ambiguity. No shared scoring across dimensions.
2. Use consistent category order across all questions. If your categories progress from worst to best (Stage 1 → Stage 4), options A–D should follow that order in every question.
3. Count categories, not scores. The result is whichever category appears most across all answers.
4. Break ties toward the earlier/worse stage. If someone scores equally across two categories, they belong at the earlier one. Better to underdiagnose than overdiagnose — nobody complains about discovering they're further along than expected.

The Scoring Logic

// Count which category each answer maps to
var scores = { category1: 0, category2: 0, category3: 0, category4: 0 };

answers.forEach(function(ansIdx, qIdx) {
    var type = questions[qIdx].options[ansIdx].type;
    scores[type]++;
});

// Highest count wins. Ties break toward earlier stage.
var stages = ['category1', 'category2', 'category3', 'category4'];
var result = stages[0];
var high = scores[stages[0]];
for (var i = 1; i < stages.length; i++) {
    if (scores[stages[i]] > high) {  // strictly greater — ties stay at earlier stage
        result = stages[i];
        high = scores[stages[i]];
    }
}

This is fundamentally different from a revelation tool's scoring. A revelation tool scores across multiple dimensions (specificity: 4, narrative: 3, readiness: 2) and produces a multi-variable profile. A diagnostic produces exactly one result: which bucket you're in.

Category Design

Progression Categories (Recommended)

Categories that form a sequence — each one is a stage that leads to the next. This is the strongest diagnostic pattern because the chain visualization maps naturally.

From the golden example:

Each stage implies you've passed the previous ones. Stage 3 means extraction and documentation happened but deployment didn't. This creates the "you are here" moment.

Type Categories (Alternative)

Categories that are parallel, not sequential — different problem types rather than stages. Use when the person needs to know WHICH problem they have, not how far along they are.

Example: Constraint types (Product / Operations / Sales) — three different problems, no inherent order.

With type categories, the chain visualization becomes a comparison rather than a progression. Each type gets equal visual weight. The "you are here" marker highlights their type rather than their position on a ladder.

Rules for Good Categories

• 3–5 categories. Fewer than 3 means the diagnostic is just a yes/no. More than 5 means the distinctions are too fine to be meaningful.
• Mutually exclusive. A person should clearly belong in one category. If most people could be in two, the categories overlap.
• Each category needs different advice. If the "what to do next" copy is the same for every category, the sort doesn't matter.
• Category names should reframe. "Not Extracted" is better than "Stage 1" because the name itself teaches something. The person learns what extraction means by being told they haven't done it.

Question Design

All Single-Select, All Behavioral

Every question in a diagnostic is single-select (radio buttons, not checkboxes). Each option maps to exactly one category. The person picks the one that sounds most like their situation.

The Pattern

[Behavioral question about what they actually do or experience]

Hint: [Why this question matters — frames the answer, not the category]

A) [Response that maps to Category 1]
B) [Response that maps to Category 2]
C) [Response that maps to Category 3]
D) [Response that maps to Category 4]

Question Design Principles

1. Ask what they DO, not what they THINK. "When a prospect asks about past results, what happens?" not "How good is your proof?"
2. Test the same construct from different angles. All 5 questions should probe the same underlying issue. Q1 asks about prospect conversations. Q2 asks about their website. Q3 asks about specificity. Q4 asks about reach. Q5 asks about their first blocker. Same construct, different lenses.
3. Easiest/least threatening question first. Q1 should feel like conversation. Q5 can be more direct.
4. Each question must differentiate. If everyone picks the same option on Q3, the question isn't sorting. Cut it.
5. Options should feel honest, not flattering. People should recognize themselves, not aspirationally pick the best answer. Frame options as situations, not evaluations.

Hints Are Required

Every question needs a hint beneath it. The hint:

• Contextualizes WHY the question matters
• Tells them what lens to use when answering
• Does NOT reveal which answer maps to which category

Good hint: "Think about your last 2–3 prospect conversations. What actually happened." Bad hint: "The best answer is one where you have specific documentation."

From the Golden Example

Q5 is the sharpest question. It asks them to identify their own first blocker directly — "If you decided today to publish a case study, what's the first thing that would slow you down?" This collapses their mental model into one obstacle. The obstacle they name IS the diagnosis.

Results Page Architecture

The results page has a specific sequence. Every section earns the next.

1. Category Label (Color-Coded)

YOUR RESULT: NOT DOCUMENTED

Styled with the category's color. The label uses the category name, not a generic "Result Type B." The name itself teaches.

2. Diagnostic Title

You can tell the story. You just can't hand it to anyone.

One sentence that reframes their situation. Not a description of the category — a restatement of their problem from their perspective. This should make them think "that's exactly right."

3. Chain Visualization

A vertical progression showing all stages. Their stage is highlighted ("You are here"). Earlier stages show as passed (green checkmarks). Later stages are dimmed.

[✓] Stage 1: Not Extracted — passed
[●] Stage 2: Not Documented — YOU ARE HERE (highlighted, gold)
[ ] Stage 3: Not Deployed — dimmed
[ ] Stage 4: Converting — dimmed

Why this matters: The chain does two things simultaneously. It validates what they've already accomplished (passed stages) and it shows how far they still have to go. Both create motivation. Both create a frame for the offer.

For type categories (non-sequential), replace the chain with a comparison showing their type highlighted among peers.

4. "What This Means" Box

Background uses the category's color at low opacity. Left border uses the category's color at full opacity.

2–3 sentences explaining their situation. Written in second person. Must be specific enough to feel personal but general enough to be accurate for everyone in this category.

Key principle: name what they have, not what they lack. "You have real client outcomes — the kind prospects would pay attention to" before "But none of it has been pulled out of your head."

5. "What to Do Next" Box

Neutral background. Describes the specific action their category requires.

This is NOT a pitch for the service. It's a genuine description of what needs to happen next. If they could do it themselves from this description, the copy is right. The fact that most won't is what makes the offer relevant — but the copy doesn't say that.

6. "What Keeps Practices Stuck Here" Box

This is the sales mechanism. It explains WHY they can't solve this on their own. Not "you need help" — the specific structural reason this stage is hard to pass without intervention.

From the golden example: "You can't extract your own proof for the same reason a surgeon can't operate on themselves." That's not a pitch. It's an insight that makes the offer feel like the obvious solution.

7. Bridge to Companion Tool

Links to the other micro-tool in the campaign. Framed for their specific category: "Not sure which outcome to start with? The Story Finder walks you through five questions to identify which client story would make the strongest first case study."

8. Offer Bridge

Stage-specific copy that connects their blocker (from section 6) to what the service solves. Includes price, deliverables, and CTA.

Critical: Each category gets different offer bridge copy. "Your chain breaks at extraction" vs. "Your chain breaks at documentation" vs. "Your chain breaks at deployment." Same offer, different framing. The framing should feel like it was written for them specifically.

9. Disclaimer

Required for all tools: "This readiness check provides directional guidance based on your responses. Results are illustrative, not an audit of your practice."

10. Retake Button

Always present. Resets all answers and returns to intro screen.

Color System for Categories

Each category needs a unique color for its label, "what this means" background, and chain highlight.

For progression categories (4 stages):

Each color also needs a low-opacity background variant:

--red-light: rgba(196, 90, 74, 0.1);
--amber-light: rgba(196, 154, 74, 0.1);
--blue-light: rgba(74, 106, 138, 0.1);
--green-light: rgba(90, 154, 106, 0.1);

UX Decisions (Non-Negotiable)

These match the revelation tool standard. They're not preferences — they're principles.

Intro Screen Required (with exceptions)

If the tool is standalone or embedded in an article: intro screen. If delivered via DM after a hand-raiser interaction: intro screen can be skipped — they already know what they're getting.

Back Button + Explicit Continue

No auto-advance on option click. Person selects an option, then clicks "Continue." Back button visible on Q2+. This gives them control and means their final answers are more considered.

Disabled State Until Selection

Continue button disabled (opacity: 0.3) until they select an option. No accidental advancement.

"See My Result" on Final Question

Last question changes the Continue button text to "See My Result." This creates a micro-moment of commitment.

Progress Bar

Fixed at top. Gold (#b79d64). Fills proportionally: ((currentQ + 1) / (totalQuestions + 1)) * 100%. The +1 accounts for the results screen.

Dark Theme

Charcoal background, cream text, gold accents. Same as all standalone micro-tools. The dark theme creates a contained, private diagnostic experience.

Visual Spec

Colors (Exact)

--gold: #b79d64;
--gold-light: rgba(183, 157, 100, 0.15);
--gold-dim: rgba(183, 157, 100, 0.08);
--charcoal: #1a1a1a;
--deep-charcoal: #2a2a2a;
--cream: #f5f4f0;
--stone: #8a8680;

Typography

• Headlines: Cormorant Garamond, weight 400
• Body: Inter, weight 300
• Labels/counters: Inter, weight 500, uppercase, letter-spacing 0.2em
• Option text: Inter, 14px, weight 300

Interactive Elements

Options (unselected):

background: rgba(245, 244, 240, 0.03);
border: 1px solid rgba(245, 244, 240, 0.08);
padding: 18px 24px;

Options (hover):

background: rgba(183, 157, 100, 0.08);
border-color: rgba(183, 157, 100, 0.3);

Options (selected):

background: rgba(183, 157, 100, 0.15);
border-color: #b79d64;

Option letters: Gold (#b79d64), weight 500, inline before option text.

Container

Max-width: 640px. Centered. Padding: 0 5%.

Scrollbar

::-webkit-scrollbar { width: 10px; }
::-webkit-scrollbar-track { background: #1a1a1a; }
::-webkit-scrollbar-thumb { background: #b79d64; border-radius: 5px; }

Mobile Breakpoints

• 968px: Reduce chain visualization padding
• 768px: Stack button row vertically (Continue on top, Back below). Reduce padding on all boxes.

Chain Visualization Spec

The chain is the visual centerpiece of diagnostic results. It shows progression and position simultaneously.

<div class="chain-stage [passed|current|dimmed]">
    <div class="chain-number">[1-4]</div>
    <div class="chain-content">
        <h4>[Stage Name] <span class="chain-you-label">You are here</span></h4>
        <p>[One-line description]</p>
    </div>
</div>

Stage States

"You Are Here" Label

font-size: 0.6rem;
font-weight: 500;
letter-spacing: 0.1em;
text-transform: uppercase;
color: #b79d64;
background: rgba(183, 157, 100, 0.15);
padding: 2px 8px;

Result Copy Requirements

Each category needs six pieces of copy:

Plus:

• bridge — one sentence connecting to the companion tool, framed for their category
• Category color and background color

Copy Principles

1. Name what they have before naming what they lack. "You have real client outcomes" before "none of it has been extracted."
2. Blocker copy must explain the structural reason, not just the symptom. "You can't extract your own proof for the same reason a surgeon can't operate on themselves" — not "you haven't gotten around to it."
3. Offer bridge copy must change per category. Same service, different framing. "Your chain breaks at extraction" vs. "Your chain breaks at deployment."
4. Action copy should be genuinely useful. If they followed the action copy perfectly, they'd solve the problem. The blocker copy explains why most people can't.

QC Checklist

Architecture

• [ ] 5 single-select questions (no multi-select)
• [ ] Each option maps to exactly one category
• [ ] Options follow consistent category order (A=worst, D=best for progression)
• [ ] Scoring counts categories, not numeric scores
• [ ] Ties break toward earlier/worse stage
• [ ] 3–5 distinct categories with meaningfully different advice

Scoring Validation

• [ ] All-A through All-D produce expected categories (consistent persona test)
• [ ] 5+ realistic mixed answer patterns produce correct results (predict before running)
• [ ] Tied category counts break toward earlier/worse stage (test adjacent and non-adjacent ties)
• [ ] Every category is reachable by some answer combination
• [ ] Distribution across all combinations isn't pathologically skewed toward one category
• [ ] If tool produces multiple outputs (e.g., stage + constraint type), incoherent pairings identified and handled

Questions

• [ ] All behavioral — asks what they DO, not what they THINK
• [ ] Each question tests the same construct from a different angle
• [ ] Hints contextualize without revealing category mapping
• [ ] Easiest question first, most direct question last
• [ ] No question where everyone would pick the same option

Results

• [ ] Category label is color-coded and uses the category name
• [ ] Title reframes their situation (not a description of the category)
• [ ] Chain visualization shows all stages with "you are here"
• [ ] "What this means" names what they have before what they lack
• [ ] "What to do next" is genuinely actionable
• [ ] "What keeps practices stuck" explains the structural reason
• [ ] Bridge to companion tool is framed for their specific category
• [ ] Offer bridge changes per category (same service, different framing)
• [ ] Disclaimer present
• [ ] Retake button present and functional

UX

• [ ] Intro screen present (unless DM delivery)
• [ ] Back button visible on Q2+
• [ ] Continue disabled until selection made
• [ ] "See My Result" on final question
• [ ] Progress bar fills proportionally
• [ ] Fade-in animation on question transitions
• [ ] Scroll to top on screen transitions

Technical

• [ ] Single HTML file, no external dependencies
• [ ] Works when opened locally
• [ ] Mobile responsive (test at 375px width)
• [ ] All click targets work
• [ ] Every category result renders correctly (render test — does the HTML break, not whether the score is right)
• [ ] Progress bar reaches 100% on results

Copy Quality

• [ ] No AI patterns (parallel constructions, three-beat lists, mirror reversals)
• [ ] Blocker copy explains structural reason, not just "you need help"
• [ ] Offer bridge is stage-specific, not generic
• [ ] Option text sounds like something a person would actually say
• [ ] Hints don't telegraph the "right" answer

What Makes a Diagnostic Different from Other Tool Types

Reference Implementation

Golden example: diagnosticmicrotoolgoldenexample.html (Proof Readiness Check)

• 5 single-select questions
• 4 progression categories (extracted → documented → deployed → converting)
• Chain visualization with "you are here"
• Category-specific result copy for all 6 blocks
• Bridge to Story Finder (revelation tool)
• $497 offer bridge with stage-specific framing

Skill file reverse-engineered from the Proof Readiness Check, February 2026 v2: Scoring Validation section added from recurring QC gap identified during System Readiness Assessment build Companion to: revelation-tool-SKILL.md, calculator-tool-SKILL.md (pending)