FREESKILL v1.2UPDATED 2026-06 · 10 MIN TO ADOPT

The 3Ps Framework

Most team updates fail because they lack focus. Progress, Plans, Problems fixes that by forcing clarity into every update. Run it here, then install it where your team actually writes.

Status updates are the highest-leverage document most teams produce, and the most wasted. They read like activity logs: meetings attended, tickets closed, decks revised. Nobody can act on an activity log.

The 3Ps force a different contract. Progress states what moved, with numbers. Plans commit to what will be true by the next update. Problems name blockers while they are still cheap to fix, each with an owner and an ask. Three headings, under 200 words, same day every week.

The format is the discipline.

SIGNALS YOU NEED THIS

Your leadership reads updates and still asks "so where are we?"

Blockers surface in escalations instead of updates.

Updates take 45 minutes to write and 4 minutes to skim.

REPLACES

Free-form status emails, verbal round-robins, and the 40-slide monthly readout.

PAIRS WITH

Weekly Status Updates, Silent Meetings, and 4 Blocker Business Reviews.

0 of 4 steps complete

STEP 01Progress

State what moved, not what happened. Outcomes with numbers beat activity lists. If nothing moved, say so and say why.

PROGRESS
- Shipped welcome flow v2. CVR +1.8 pts vs holdout.
- Migrated 3 of 5 lifecycle segments to predictive CLV.

STEP 02Plans

Commit to what will be true by the next update. Dated, owned, testable. Plans are promises, not intentions.

PLANS
- Launch win-back test to 20% of lapsed cohort by Friday.
- Draft Q3 experiment calendar. Owner: me.

STEP 03Problems

Name blockers while they are cheap. Every problem gets an owner and a specific ask. A problem without an ask is a complaint.

PROBLEMS
- Deliverability dip on sending domain 2. Root cause unknown.
  Ask: 30 minutes with infra eng this week.

STEP 04Ship it

One update. Three headings. Under 200 words. Same channel, same day, every week. Consistency is what makes the data comparable.

CADENCE
- Sent Fridays, 2pm, #team-lifecycle.
- Skipped weeks are announced, never silent.

The skill is a folder, not a service. It runs where your work runs, invokes only when you ask, and never fetches anything remote.

skills/3ps-framework

3ps-framework/
├── SKILL.md              ← invocation rules + the framework
├── templates/
│   └── 3ps-update.md     ← the 200-word update scaffold
└── examples/
    └── weekly-update.md  ← a real update, annotated

EXPLICIT INVOCATION ONLY

"Use the 3ps-framework skill to draft my weekly update from these notes."

Download skill v1.2 View source on GitHub

WORKS WITHClaude CodeClaude.aiCursorWindsurf