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

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

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

The three reasons are visible, but the order runs backward and user-post evidence is attached to churn.

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

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

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

Без Minto

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

It closely follows the gold hierarchy, though formal presentation and strengthened causal claims make it less disciplined.

Subject: Recommendation: Dedicate Next Sprint to Reducing Defect Backlog

Hi Alex,

I recommend using the next sprint to reduce the defect backlog. This intervention is necessary to address an unsustainable technical trajectory and mitigate immediate risks to retention and revenue.

1. Backlog growth outpaces resolution
Incoming defects now exceed our closure rate. The attached projection indicates the backlog will expand significantly over the next year without dedicated remediation time.

2. Defects are driving churn
Customer experience data shows a direct correlation between defect volume and churn. Recent interviews reinforce that stability issues are causing customers to leave.

3. Revenue and brand impact are accelerating

  • Sales: Close rates are falling as prospects cite reliability concerns.
  • Major Account: We received a formal complaint from a key client regarding these issues.
  • Sentiment: Public user posts reflect growing dissatisfaction.

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

Best,

[Your Name]

С Minto

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

The three reasons are visible, but the order runs backward and user-post evidence is attached to churn.

Subject: Recommendation: Dedicate next sprint to reducing defect backlog

As we plan the next sprint, our incoming defect rate exceeds our fix rate, projecting a widening backlog that is actively harming retention and revenue. Customer data links this backlog directly to increased churn, while a major account complaint and falling sales close rates signal immediate pipeline damage. To arrest this trend, we must dedicate the next sprint to reducing the defect backlog.

Why this is critical:

  • The backlog is driving churn. Churn correlates with defect volume, reinforced by user posts and interview feedback showing severe customer frustration.
  • The backlog is eroding sales velocity. A major account has lodged a formal complaint, and Sales reports falling close rates attributed to these quality concerns.
  • The backlog is accelerating. Incoming defects consistently outpace fixes, projecting a worsening trajectory that compounds the risk daily.

Decision needed: Approve the next sprint focus as defect reduction.

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

qwen3.6-35b-a3b получила одну и ту же задачу дважды. Контрольный промпт — одна вводная строка и задача. Промпт с 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