Minto

Claude Sonnet 5 на кейсе «Сообщение о техдолге»: с Minto лучше по обеим мерам

Структура 7 → 8 из 8 +1 Качество 9 → 10 из 10 +1

Судья об ответе с Minto

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

Режим write · кейс 08-techdebt · прогон v1.7.0-final

Структура из 8, по 2 балла на ось
Без Minto 7С Minto 8Изменение
Вершина
Состав ключевой линии+1
Уровни
Порядок и род
Качество из 10, по 2 балла на ось
Без Minto 9С Minto 10Изменение
Вершина
Однородные группы
Объяснимый порядок
MECE+1
Видимая соразмерная структура

Ответы моделей и слова судьи приведены в оригинале, по-английски.

Без Minto С Minto

Без Minto

контрольный промпт · слепая метка out-10
  • invented_facts
  • качество со штрафом рубрики 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.

С Minto

промпт с навыком · слепая метка out-08
  • invented_facts
  • качество со штрафом рубрики 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?

Как устроен тест

Claude Sonnet 5 получила одну и ту же задачу дважды. Контрольный промпт — одна вводная строка и задача. Промпт с Minto — та же задача, перед которой стоит полный текст навыка. Судья читал оба ответа среди 16 ответов под слепыми метками и не знал, в каком из них был навык.

Промпт без Minto 1 438 Б 
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.
Промпт с Minto пять частей по порядку · 29 011 Б
  1. Below is a skill written as an instruction. Read it in full and apply it to the task at the end.
  2. ===== SKILL.md ===== SKILL.md на f4813ce 17 235 Б
  3. ===== references/rules.md ===== references/rules.md на f4813ce 6 464 Б
  4. ===== references/templates.md ===== references/templates.md на f4813ce 3 742 Б
  5. ===== TASK ===== вход кейса целиком
  6. Return only the result, with no explanation of how you produced it.
Вход кейса before.md

<!-- 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
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.

Эталон судьи 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:

  1. The backlog is growing faster than the team can reduce it.
  2. Defects are driving customer churn.
  3. 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.

Судья gpt-5.6-sol, effort high · Claude Sonnet 5, effort low · навык с коммита f4813ce · прогон v1.7.0-final