Minto

qwen3.6-fp8 на кейсе «Сообщение о техдолге»: с Minto хуже по обеим мерам

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

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

Its business-loss branches are plausible, but backlog evidence is misplaced under market sentiment.

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

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

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

Без Minto С Minto

Без Minto

контрольный промпт · слепая метка out-06
  • invented_facts
  • unacknowledged_source_loss
  • качество со штрафом рубрики 7/10

The three reasons are easy to scan, while missing evidence and stronger-than-source wording keep it below the leaders.

Subject: Recommendation: Dedicate Next Sprint to Reducing Defect Backlog

Hi Alex,

I recommend using the next sprint to reduce the defect backlog. This action is necessary to mitigate three urgent risks:

  • Unsustainable Backlog Growth: Incoming defects currently exceed our resolution rate. Projections show the backlog will continue to grow significantly over the next year without intervention.
  • Increasing Customer Churn: Defect volume correlates strongly with churn. Customer experience data and recent interviews confirm that quality issues are actively driving customers away.
  • Revenue and Brand Damage: Quality concerns are harming our reputation and sales pipeline. We have received a complaint from a major account, observed negative user sentiment, and Sales reports that these issues are causing close rates to fall.

Please let me know if you support this focus for the upcoming sprint.

Best regards,

[Your Name]

С Minto

промпт с навыком · слепая метка out-03
  • invented_facts
  • unacknowledged_source_loss
  • качество со штрафом рубрики 6/10

Its business-loss branches are plausible, but backlog evidence is misplaced under market sentiment.

Subject: Dedicate next sprint to reducing the defect backlog

Situation: We have been tracking our defect intake against resolution rates, and customer feedback has consistently highlighted stability issues.
Complication: Our current trajectory projects an unchecked backlog over the next year, which is already correlating with rising churn, blocking new deals, and damaging our brand reputation.
Answer: Yes, we should dedicate the next sprint to reducing the defect backlog.

Why:

  1. Defects are actively driving customer churn
    • CX research links defect volume to attrition
    • Churn-vs-defect chart confirms the correlation
    • Customer interview underscores the experience gap
  2. Stability concerns are blocking new revenue
    • Sales reports confirm falling close rates tied to reliability fears
    • A major account complaint signals deal-breaking risk
  3. Negative sentiment is spreading across the market
    • User posts amplify dissatisfaction beyond direct accounts
    • Current intake outpaces fixes, showing unsustainable growth
    • One-year projection confirms accelerating backlog without intervention

What I need now: Approval to allocate the next sprint to defect reduction.

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

qwen3.6-fp8 получила одну и ту же задачу дважды. Контрольный промпт — одна вводная строка и задача. Промпт с 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 · навык с коммита f4813ce · прогон v1.7.0-final