mcpField
O
outcome-first-experience-bullets

outcome-first-experience-bullets

github.com/arthurzakirovMarketing & growth0162 installsUpdated 4w ago
Repository

About outcome-first-experience-bullets

A writing skill for turning resume, LinkedIn, portfolio, and case-study bullets into outcome-focused statements. It emphasizes visible results, accurate scope, and separating context from the mechanisms behind an outcome.

Key features

  1. 01Outcome-led bullet formula
  2. 02Strong-verb guidance
  3. 03Umbrella outcome pattern
  4. 04Context before results
  5. 05Precision and ownership checks

Use cases

  1. 01Reworking resume experience bullets
  2. 02Editing LinkedIn profile entries
  3. 03Describing portfolio project results
  4. 04Writing case-study outcome bullets

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/arthurzakirov/proofstack --skill outcome-first-experience-bullets

After installing, type/outcome-first-experience-bulletsin Claude Code to confirm it loaded.

Details

From the project README

Outcome-First Experience Bullets Skill

Purpose

Rewrite resume, LinkedIn, portfolio, and case-study bullets so they show outcomes, not just activities.

Rule

Context paragraph explains the environment. Bullets explain the results.

Do not use bullets for generic responsibilities unless they are necessary for understanding the result.

Bullet Formula

[Strong verb] + [outcome] + [scope/scale] + [mechanism if useful] + [constraint if impressive]

Examples of strong verbs:

  • Built
  • Deployed
  • Surfaced
  • Reframed
  • Enabled
  • Reduced
  • Automated
  • Unblocked
  • Migrated
  • Diagnosed
  • Consolidated
  • Scaled
  • Standardized

Avoid Weak Verbs

Avoid:

  • Contributed to
  • Worked on
  • Helped with
  • Supported
  • Participated in
  • Was responsible for

Use "helped" only when ownership is genuinely shared or when avoiding overclaiming.

Umbrella Outcome Pattern

When one outcome is achieved through several other bullets, do not overload a single bullet with all mechanisms.

Example:

Helped maintain team velocity after the team shrank from 10 to 8 people while taking over responsibilities from 3 additional engineers.

Then the following bullets can show the mechanisms:

  • Built automation.
  • Created onboarding material.
  • Ran knowledge transfers.
  • Shipped tooling.
  • Surfaced leverage opportunities.

Context Before Bullets

Use short context text for organization authority and operating environment:

Example:

At a high-growth procurement software company, I worked in a multi-stakeholder technical environment where data quality, customer onboarding, and internal tooling directly affected product delivery.

Then bullets:

  • Migrated customer data pipelines...
  • Diagnosed production data issues...
  • Built internal tooling...

Precision Rules

  • Use numbers when accurate.
  • Avoid simplified numbers if they distort reality.
  • Explain ratios carefully.
    • Good: "surfaced 770 addressable hours behind a 41-hour roadmap"
    • Risky: "created 19x more savings" if savings were only addressable potential

Checklist

  • Does the bullet say what changed?
  • Is the result more visible than the task?
  • Is the scope quantified where possible?
  • Is shared ownership represented honestly?
  • Are mechanisms omitted when they would make the bullet too crowded?

Comments

Markdown supported