Minto

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

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

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

The external-loss key line is strong, but conspicuous SCQ apparatus, omissions, and fabricated specificity weaken the message.

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

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

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

Без Minto С Minto

Без Minto

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

Reasons and next actions occupy the same first level, producing five mixed elements alongside substantial invention and omission.

Recommendation: Allocate the next sprint to aggressively reduce the defect backlog.

Why this matters now

  • Backlog is exploding: New defects consistently outpace closures; the attached trend line projects the backlog will more than double within 12 months if unchanged.
  • Direct revenue risk: Defects are the top driver of churn (see churn‑vs‑defect chart) and are cited in a recent customer interview as a reason for leaving.
  • Brand & sales impact: Negative user posts, a formal complaint from a key account, and sales data showing a dip in close rates all trace back to defect‑related frustrations.

Next steps

  • Prioritize defect‑fix work in the upcoming sprint.
  • Track weekly closure rates against the projected backlog to ensure the trend reverses.

Charts and supporting data are attached for reference.

С Minto

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

The external-loss key line is strong, but conspicuous SCQ apparatus, omissions, and fabricated specificity weaken the message.

Subject: Prioritize defect backlog reduction in the next sprint

Situation: New defects are consistently outpacing closures, and the backlog is projected to double within a year.

Complication: This growing backlog is driving higher churn, damaging our brand, and hurting sales—customers cite defects as a reason for leaving, user forums are filled with complaints, a major‑account has lodged a formal complaint, and sales teams report lower close rates.

Answer: Allocate the next sprint to aggressively reduce the defect backlog.

Why:

  1. Defects are a leading driver of churn (see churn‑vs‑defect chart).
  2. Ongoing quality issues are eroding brand perception (negative user posts, major‑account complaint).
  3. Sales pipelines are suffering (falling close rates linked to defect concerns).

What I need now: Your approval to prioritize backlog reduction in the upcoming sprint.

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

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