Proof promise plan openers

Proof-Promise-Plan Openers Skill

Purpose

Create strong openings for articles, landing pages, README files, LinkedIn posts, videos, and guides.

This skill is based on a simple communication structure:

Proof -> Promise -> Plan

Structure

1. Proof

Show why the reader should listen.

Proof can be:

• "I built X."
• "This was used by Y people."
• "This produced Z result."
• "This came from a high-pressure environment."
• "This is based on public guidance from a credible source."
• "This was tested in production."

2. Promise

Say what the reader will gain.

Good promises:

• "You will learn how to spot the same pattern."
• "You will learn how to build the same system."
• "You will learn how to avoid the failure mode."
• "You will get a reusable checklist."

Avoid vague promises:

• "You will learn about my experience."
• "I will share my thoughts."
• "This is my journey."

3. Plan

Preview the path.

Good plans:

• "First, I'll show the bottleneck. Then, the system. Finally, the reusable framework."
• "We'll cover setup, operating loop, failure modes, and examples."
• "I'll break it into four steps."

Formula

[Proof]. In this guide, you'll learn [promise]. We'll cover [step 1], [step 2], and [step 3].

Example

Weak:

In this article, I want to talk about automation roadmaps.

Better:

A small operational dataset revealed a 770-hour automation opportunity hidden behind a 41-hour roadmap. In this guide, you'll learn how to spot the same pattern in your own backlog. We'll cover the data model, the prioritization trap, and the questions that reveal higher-leverage work.

Checklist

• Is the proof visible in the first 1-2 lines?
• Is the promise about the reader's gain?
• Is the plan concrete enough to reduce ambiguity?
• Is the opener not just biography?