Minto

Codex gpt-5.6-terra на кейсе «Сообщение о техдолге»: с Minto лучше по обеим мерам

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

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

This is the cleanest compact rendering of the gold structure, apart from changing one interview into multiple interviews.

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

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

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

Без Minto С Minto

Без Minto

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

The gold logic is recognizable, though prose obscures the hierarchy slightly and Research is omitted.

Hi Alex,

I recommend we make reducing the defect backlog the next sprint’s priority.

The backlog is growing faster than we can close it and is projected to worsen over the next year. It is already affecting retention: Customer Experience data, churn analysis, and user interviews link defect volume to customer frustration and churn.

It is also creating commercial risk. User posts, a major-account complaint, and Sales feedback show that reliability concerns are damaging our reputation and lowering close rates.

A focused sprint now will reduce both the operational backlog and its customer and revenue impact.

С Minto

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

This is the cleanest compact rendering of the gold structure, apart from changing one interview into multiple interviews.

Hi Alex — we should use the next sprint to reduce the defect backlog before it compounds into higher churn, brand damage, and harder sales.

The backlog is projected to grow over the next year because incoming defects exceed fixes.

Customer Experience and Research link defect volume to churn, supported by customer interviews and the churn trend.

User posts, a major-account complaint, and Sales reports show defects are already damaging trust and reducing close rates.

Please prioritize backlog reduction for the next sprint.

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

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