# Outcome First Experience Bullets

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

- Skill: `arthurzakirov/outcome-first-experience-bullets` (Agent Skill)
- Install (CLI): `npx skillmds@latest add arthurzakirov/outcome-first-experience-bullets`
- Raw SKILL.md: https://api.skillmd.com/api/skills/arthurzakirov/outcome-first-experience-bullets/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ArthurZakirov (https://skillmd.com/u/arthurzakirov)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/arthurzakirov/outcome-first-experience-bullets

---


# 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

```text
[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:

```text
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:

```text
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?