Minto

Claude Haiku 4.5 на кейсе «Сообщение о техдолге»: с Minto без изменений

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

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

Heavy SCQ labels and speculative downstream claims turn a colleague note into an oversized memo while several evidence units disappear.

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

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

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

Без Minto С Minto

Без Minto

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

Backlog growth arrives after the customer-loss argument rather than framing it, and several source units are lost.

Hi Alex,

We should focus the next sprint on defect reduction—it's driving customer churn and brand damage.

Defect volume correlates directly with churn, and customer interviews identify it as a primary pain point. Beyond retention, we're seeing brand damage surface through user posts, a major account escalation, and sales reports of deals stalling over these concerns.

The underlying issue: we're opening defects faster than closing them, and our projection shows the backlog will grow significantly over the next year.

Thoughts?

С Minto

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

Heavy SCQ labels and speculative downstream claims turn a colleague note into an oversized memo while several evidence units disappear.

Subject: Recommend next sprint focus: prioritize defect reduction

Situation:
Our backlog is growing as new defects consistently outpace our closure rate.

Complication:
Projections show the gap will widen across the year. More urgently, the backlog is now creating measurable business impact: CX data links defect volume to customer churn, Sales reports that defect concerns are blocking deals, and a major account has escalated concerns. This is no longer a technical issue—it's a revenue and credibility issue.

Answer:
We should prioritize defect reduction in the next sprint.

Why:

  1. We prevent customer churn. CX research directly ties defect volume to retention loss. Each sprint we delay, we lose more customers and the revenue we'd spend months recovering.
  2. We unblock the sales pipeline. Defect concerns are blocking deals—a major account has escalated, and reps report deal impact. Fixing defects restores credibility and unblocks prospects.
  3. We prevent the backlog from becoming unmanageable. New defects now outpace closures every period. Without intervention, we spiral toward crisis mode where we can only patch emergencies.

What I need now:
Sign-off so we can brief the team and finalize the sprint plan.

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

Claude Haiku 4.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 Haiku 4.5, effort low · навык с коммита f4813ce · прогон v1.7.0-final