Claude Sonnet 5 on “A message about technical debt”: better with Minto on both measures

Structure 7 → 8 of 8 +1 Quality 9 → 10 of 10 +1

The judge on the output with Minto

The hierarchy and evidence placement are excellent; the unsupported feature tradeoff and complaint escalation are its only decisive defects.

Mode write · case 08-techdebt · run v1.7.0-final

Structure of 8, 2 points per axis
Structure	Without Minto 7	With Minto 8	Change
Top	2	2
Key-line composition	1	2	+1
Levels	2	2
Order and kind	2	2

Quality of 10, 2 points per axis
Quality	Without Minto 9	With Minto 10	Change
Top	2	2
Same-kind grouping	2	2
Explainable order	2	2
MECE	1	2	+1
Visible, proportionate structure	2	2

Outputs and the judge’s words are quoted as written, in English.

Without Minto With Minto

Without Minto

control prompt · blind label out-10

invented_facts
quality after the rubric’s penalty 8/10

It preserves the evidence well, but merging retention, brand, and revenue into one wide branch leaves only two first-level reasons.

Hi Alex,

We should dedicate next sprint to reducing the defect backlog — it's now driving both churn and lost deals.

Backlog is growing unsustainably. New defects are outpacing fixes, and our one-year projection shows the gap widening if we don't intervene.

This is already costing us customers and revenue. Churn tracks closely with defect volume, CX and Research confirm the link, and a customer interview illustrates the pattern directly. Brand damage is compounding it: user complaints, a major account escalation, and Sales flagging that defects are making deals harder to close.

Let me know if you're aligned so we can lock this into sprint planning.

With Minto

prompt with the skill · blind label out-08

invented_facts
quality after the rubric’s penalty 8/10

The hierarchy and evidence placement are excellent; the unsupported feature tradeoff and complaint escalation are its only decisive defects.

Hi Alex,

We should use the next sprint to pay down the defect backlog, not add new features — the backlog is now costing us customers and revenue, not just engineering time.

The backlog itself is on an unsustainable trajectory: new defects are outpacing what we close, and the one-year projection shows the gap widening if nothing changes.

That gap is already driving churn: Customer Experience and Research both tie defects to churn, the chart plotting churn against defect volume shows the correlation directly, and a customer interview puts a concrete story behind the numbers.

It's also damaging our reputation and pipeline: users are posting complaints, a major account has escalated one directly, and Sales reports that these concerns are making deals harder to close.

Can you confirm the next sprint on backlog reduction?

The judge

Recurring defect	without	with Minto
Unsupported precision, causal strengthening, or new forecaststhe skill has the rule; the model did not follow it · Mode 3 — “Invent nothing”	present	present

Decisive questions

Recommendation
without First
with Minto First
First-level kind
without Business losses
with Minto Business losses
Count
without 2
with Minto 3
All nine correctly placed?
without Yes
with Minto Yes
Backlog as SCQ complication?
without No
with Minto No
Format
without Colleague message
with Minto Colleague message
Invented material
without Lost deals, close tracking, and account escalation
with Minto The feature-work exclusion and escalation of the account complaint
Reader question literal?
without No
with Minto Yes

Judge’s check	without	with Minto
Answer first	yes	yes
First-level elements	2	3
First-level kind matches the gold	yes	yes
Invented facts	yes	yes
Source lost without a note	no	no
Mode respected	yes	yes
Reader’s question stated literally	no	yes
Order type named	no	no
SCQ introduction present	yes	yes

How the test was built

Claude Sonnet 5 received the same task twice. The control prompt is one framing line and the task. The prompt with Minto is the same task preceded by the full text of the skill. The judge read both outputs among 16 under blind labels and did not know which one had the skill.

Prompt without Minto 1 438 B

You are working on a business document using the Minto Pyramid Principle.

<!-- Original paraphrase inspired by Jory MacKay's Planio article,
     "The Pyramid Principle: How to pitch anything (and get a yes)", 2022. -->

# Fixture 08: technical-debt message

**Mode:** `write`
**Language:** `en`

## Context

You are a product manager writing to Alex, who decides the next sprint's focus.
Available evidence includes a time series of incoming and fixed defects, a
one-year projection, customer-experience data, an interview story, churn
plotted against defect volume, user posts, a complaint from a major account,
and Sales reports about falling close rates.

## Before

```text
Hi Alex,

I am increasingly worried about the defect backlog. The attached chart compares
new defects with the number we close and projects the backlog one year ahead.

Customer Experience and Research also report that defects are contributing to
churn. A second chart places churn beside defect volume, and an interview
illustrates the same issue.

There are signs of brand damage too: user posts, a complaint from a major
account, and Sales reports that these concerns are making deals harder to close.

I recommend using the next sprint to reduce the defect backlog. Let me know what
you think.
```

## Task

Rewrite this as a concise message to Alex using the Minto Pyramid Principle.

Return only the result, with no explanation of how you produced it.

Prompt with Minto five parts, in order · 29 011 B

Below is a skill written as an instruction. Read it in full and apply it to the task at the end.
===== SKILL.md ===== SKILL.md at f4813ce 17 235 B
===== references/rules.md ===== references/rules.md at f4813ce 6 464 B
===== references/templates.md ===== references/templates.md at f4813ce 3 742 B
===== TASK ===== the whole case input
Return only the result, with no explanation of how you produced it.

Case input before.md

Fixture 08: technical-debt message

Mode: write
Language: en

Context

You are a product manager writing to Alex, who decides the next sprint's focus.
Available evidence includes a time series of incoming and fixed defects, a
one-year projection, customer-experience data, an interview story, churn
plotted against defect volume, user posts, a complaint from a major account,
and Sales reports about falling close rates.

Before

Hi Alex,
                
                I am increasingly worried about the defect backlog. The attached chart compares
                new defects with the number we close and projects the backlog one year ahead.
                
                Customer Experience and Research also report that defects are contributing to
                churn. A second chart places churn beside defect volume, and an interview
                illustrates the same issue.
                
                There are signs of brand damage too: user posts, a complaint from a major
                account, and Sales reports that these concerns are making deals harder to close.
                
                I recommend using the next sprint to reduce the defect backlog. Let me know what
                you think.

Task

Rewrite this as a concise message to Alex using the Minto Pyramid Principle.

The judge’s gold gold.md

Gold 08: technical-debt message

This is an original modern fixture inspired by the cited Planio example, not a
book-derived gold text.

Expected structure

Top: Use the next sprint to reduce the defect backlog.

First-level reasons:

The backlog is growing faster than the team can reduce it.
Defects are driving customer churn.
Defects are damaging brand perception and sales.

Evidence stays beneath its reason: incoming/fixed/projection data under backlog
growth; CX, interview, and churn chart under churn; user posts, account
complaint, and Sales reports under brand and sales.

The recommendation must move from the last paragraph to the first sentence.
Specific percentages, customer names, deadlines, or defect counts are
inventions. A compact colleague message is preferable to a formal memo.

An output that treats backlog growth as the SCQ Complication and uses only the
two external business losses as its key line may be stronger than this gold and
must not be penalized.

Judge gpt-5.6-sol, effort high · Claude Sonnet 5, effort low · skill from commit f4813ce · run v1.7.0-final