resume-bullet-writer

name	resume-bullet-writer
description	Rewrites work experience descriptions into achievement-oriented resume bullets using the Action Verb + Task + Metric/Result formula. Produces 3-5 polished bullets per role that quantify impact and highlight transferable skills. Use when the user wants to write resume bullets, improve their experience section, turn job duties into achievements, or create accomplishment statements. Do NOT use for resume summary sections (use resume-summary-writer), ATS keyword optimization (use ats-resume-optimizer), or career change resume rewrites (use career-change-resume).
license	Apache-2.0
metadata	{"author":"foundry-skills","version":"1.0.0","tags":"resume-writing career template","category":"career-development","subcategory":"job-search","depends":"","disclaimer":"none","difficulty":"beginner"}

Resume Bullet Writer

When to Use

Use this skill when any of the following situations apply:

• The user explicitly asks to write, rewrite, improve, or create resume bullets or bullet points for a specific job role they have held
• The user provides a list of job duties, responsibilities, or tasks and wants them transformed into achievement-oriented accomplishment statements
• The user says their resume "reads like a job description" and they want to make it sound more impactful, results-driven, or accomplishment-focused
• The user has metrics, numbers, or wins from their work history and wants help structuring them into polished, paste-ready bullets
• The user is preparing for a specific job application and wants to tailor their existing experience bullets to match the target role's language and priorities
• The user asks what action verbs to use, how to quantify their work, or how to express impact without having hard metrics
• The user has a draft bullet they wrote themselves and wants a critique, rewrite, or improvement

Do NOT use this skill when:

• The user needs a professional summary paragraph at the top of their resume -- use resume-summary-writer instead, which specializes in synthesizing career narrative into 3-5 sentences
• The user's primary goal is to get past Applicant Tracking Systems by embedding specific keywords throughout the resume -- use ats-resume-optimizer, which maps job description keywords to resume sections systematically
• The user is changing careers and needs to reframe an entirely different industry's experience to appear relevant to a new field -- use career-change-resume, which handles narrative repositioning across functional areas
• The user needs a cover letter -- use cover-letter-writer, which structures persuasive prose around fit and motivation rather than terse bullet formatting
• The user is writing a curriculum vitae (CV) for academic, research, or medical positions -- CV bullets follow different conventions (publications, grants, teaching load) that are outside the scope of this skill
• The user wants to write a LinkedIn About section or LinkedIn experience entries -- LinkedIn supports paragraph prose and informal tone that differs from tight resume formatting

---

Process

Step 1: Gather Raw Material Before Writing Anything

Never begin writing bullets until you have enough information to produce real results. Missing one key detail forces a rewrite. Collect all of the following before drafting:

• Job title exactly as it appears (or appeared) on their employment record -- "Marketing Coordinator," not "marketing person." The title affects verb strength and seniority calibration.
• Company type and size if the name cannot be used -- industry, approximate employee count, revenue tier (startup, Series A/B, Fortune 500, public sector), or geography served. This context lets you write accurate scope indicators.
• Exact tenure -- month and year range, because duration affects how much output to claim (1 year vs. 5 years changes the plausibility of volume claims)
• 3 to 7 specific duties, tasks, or projects -- accept bullet-point rough notes, stream-of-consciousness descriptions, or even copied text from an old resume or job posting. Raw and messy is fine; polish comes later.
• Every number the user can recall, no matter how approximate -- team size, budget managed, revenue figures, number of clients, call volume, error rates, time savings, user counts, projects completed, content pieces produced, events organized. Tell the user to estimate if they cannot remember exactly; "roughly 20 clients" is usable.
• The target role or job posting -- even a job title like "Senior Product Manager at a fintech startup" lets you prioritize which bullets to lead with and which verbs to use. If they have the actual job description, ask them to paste the top 5 required qualifications.

If the user provides only vague input like "I managed social media," ask exactly one targeted follow-up question per gap: "How many followers did the account have at the start versus end of your tenure?" or "How many posts per week did you publish?" Do not ask five clarifying questions at once -- it feels like an interrogation and stalls momentum.

Step 2: Map Each Duty to Its Hidden Achievement

Every job duty contains a hidden achievement. Your job is to excavate it using a consistent three-part framework:

• Action: What did the person physically do? (built, analyzed, led, negotiated, wrote, trained, designed)
• Scope: How large was the surface area of their work? (number of people, dollar amount, accounts, markets, systems, time period)
• Result: What changed, improved, or was delivered because of their work? (revenue gained, cost saved, time reduced, risk avoided, process improved, headcount scaled)

For each duty the user provides, run it through this mental filter:

• If a duty is "wrote quarterly reports" -- ask: for how many stakeholders, how long was each report, what decisions did those reports influence?
• If a duty is "managed a team" -- ask: how many direct reports, what was the team's output (projects shipped, tickets closed, revenue generated), did team performance metrics improve under their leadership?
• If a duty is "handled customer complaints" -- ask: how many per week/month, what was the resolution rate, was there a CSAT or NPS score improvement, what was the complaint category?
• If a duty is "assisted with onboarding" -- ask: how many new hires per quarter, what was the ramp time, did time-to-productivity change?

When a user genuinely has no metrics -- common in education, nonprofits, early-career roles, or highly operational positions -- shift to scope quantification: team size, geographic reach, system names, budget ranges, frequency of output, or number of stakeholders served. Scope indicators are legitimate replacements for outcome metrics and are preferable to leaving bullets metric-free.

Step 3: Select and Calibrate Action Verbs by Contribution Level

The opening verb of a resume bullet is the first signal of seniority and credibility. Using the wrong verb in either direction (too junior or too senior) damages trust with hiring managers. Calibrate to the user's actual role and actual contribution:

Strategic ownership -- C-suite, VP, Director, or senior individual contributor with org-wide impact:

• Spearheaded, Pioneered, Architected, Championed, Transformed, Overhauled, Established, Formulated, Envisioned, Negotiated (six-figure contracts or above)

Managerial and program-level execution -- Managers, Senior ICs, Program Leads:

• Led, Directed, Managed, Launched, Orchestrated, Oversaw, Scaled, Restructured, Mentored, Championed, Built (a team, system, or program from scratch)

Independent execution -- Mid-level ICs, Specialists, Coordinators with autonomy:

• Developed, Designed, Implemented, Delivered, Optimized, Streamlined, Automated, Produced, Engineered, Analyzed, Authored

Collaborative contribution -- Junior roles, early-career, support functions, interns:

• Contributed, Supported, Facilitated, Coordinated, Assisted, Collaborated, Prepared, Maintained, Monitored, Compiled, Drafted

Absolute prohibitions regardless of seniority:

• Never use "Responsible for" or "Responsibilities included" -- these describe a job description, not a human achievement
• Never use "Helped with" or "Worked on" -- these erase ownership and signal passivity
• Never use "Was tasked with," "Served as," or "Acted as" -- bureaucratic and weak
• Never use gerunds as openers ("Managing," "Developing," "Leading") -- past tense action verbs are the convention and the standard

Step 4: Apply the Formula and Write Draft Bullets

The core formula for resume bullets is: Strong Action Verb + Specific Task/Project + Context/Scope + Quantified Result or Measurable Outcome

Not every bullet will contain all four elements, but every bullet must contain at least three. The result element is the most commonly omitted and the most important to include.

Apply these structural variations depending on what information is available:

Full metric available (ideal):

Reduced customer onboarding time by 35% by redesigning the 6-step intake workflow and eliminating 3 redundant approval checkpoints.

Volume/output metric available (strong):

Produced 48 data quality audit reports annually, ensuring compliance for a portfolio of 320 active client accounts.

Scope indicator only (acceptable when no metrics exist):

Managed IT infrastructure for a 200-person headquarters, including server maintenance, help desk operations, and vendor contract negotiations.

Comparative benchmark available (very strong):

Achieved a 94% customer satisfaction score on a team of 12 agents, exceeding the department average of 87% for three consecutive quarters.

Write all bullets in simple past tense for previous roles. For current roles, use simple present tense only for ongoing responsibilities, past tense for completed projects or achievements.

Aim for 18 to 25 words per bullet. Bullets under 12 words are too thin to convey impact. Bullets over 30 words become difficult to scan and should be split or trimmed.

Step 5: Test Each Bullet Against the "So What?" Filter

After writing every draft bullet, apply the "So What?" test: read the bullet and ask whether a hiring manager reading it in six seconds would understand why this achievement matters and would want to learn more.

Fail cases and their fixes:

• "Managed social media accounts." -- So what? How many accounts? What growth? Fail. Add platform count, follower growth, and engagement metric.
• "Improved team performance." -- So what? By how much? Compared to what? Fail. Add a percentage, a before/after state, or a specific KPI.
• "Developed new processes." -- So what? Which processes? What outcome? Fail. Name the specific process and the time or cost it saved.
• "Worked closely with stakeholders." -- So what? Who were they? What was accomplished? Fail. Name the stakeholder type (e.g., C-suite, engineering leadership, external clients) and what the collaboration produced.

A bullet passes the "So What?" test when the achievement is self-evident to someone who has never met the user and does not know the company.

Step 6: De-duplicate Verbs, Order by Relevance, and Polish

After writing 3 to 7 draft bullets, apply the following quality checks before delivering the final output:

• No duplicate opening verbs: Scan all bullets for the same first word. If two bullets both start with "Developed," change one to "Built," "Created," "Engineered," or another synonym that accurately reflects the work.
• Order by relevance to target role: The bullet that most directly maps to the top requirement in the job description goes first. Chronological ordering is a beginner mistake -- hiring managers read the first bullet and often stop if it is weak. Lead with the strongest, most relevant achievement.
• Strip filler language: Remove these phrases on sight: "various," "multiple types of," "on a daily basis," "day-to-day," "in order to," "as well as," "various stakeholders," "helped to," "assisted in the process of." Each one adds words and removes signal.
• Verify tense consistency: All bullets for a past role should be past tense. All bullets for a current role's ongoing work should be present tense. Completed projects at a current role should be past tense.
• Read every bullet aloud: Awkward phrasing, passive voice, or run-on structure reveals itself in speech. If it sounds clunky, it reads clunky.
• Check for specificity completeness: Each bullet should name tools, systems, frameworks, or methodologies where relevant, because these serve as implicit ATS keywords without being a separate optimization task. "Built ETL pipelines using Python and Apache Airflow" beats "Built ETL pipelines."

Step 7: Deliver Output with Transparent Reasoning

Always deliver the output in the format defined below. Do not deliver bullets alone -- include the Before/After Comparison and Why These Work sections because they accomplish two things: they help the user understand what changed and why, and they allow the user to validate that the rewrite accurately represents their work before they paste it onto their resume.

If you invented an estimated metric or made an assumption, flag it explicitly with a note like: (Assumed: 40% growth -- confirm this figure before using.) Never let an estimated number pass silently into the output where it could be pasted verbatim as if it were a documented fact.

---

Output Format

Deliver the completed output in the following structure exactly. Every section is required.

## Resume Bullets: [Exact Job Title] at [Company Name or Descriptor]

**Target role:** [Job title and/or company type the user is applying for]
**Tenure:** [Month/Year -- Month/Year or duration in years/months]

---

### Polished Bullets

1. [Action Verb] [specific task or project] [for/within/across scope indicator], [result: reducing / delivering / achieving / resulting in] [quantified outcome or measurable impact].

2. [Action Verb] [specific task or project] [for/within/across scope indicator], [result: reducing / delivering / achieving / resulting in] [quantified outcome or measurable impact].

3. [Action Verb] [specific task or project] [for/within/across scope indicator], [result: reducing / delivering / achieving / resulting in] [quantified outcome or measurable impact].

4. [Action Verb] [specific task or project] [for/within/across scope indicator], [result: reducing / delivering / achieving / resulting in] [quantified outcome or measurable impact].

5. [Action Verb] [specific task or project] [for/within/across scope indicator], [result: reducing / delivering / achieving / resulting in] [quantified outcome or measurable impact].

---

### Why These Work

| # | Bullet Strength | Key Technique Applied |
|---|----------------|-----------------------|
| 1 | [What makes this bullet strong -- specific metric, verb choice, or framing decision] | [Formula element: scope / outcome / benchmark / volume] |
| 2 | [What makes this bullet strong] | [Formula element] |
| 3 | [What makes this bullet strong] | [Formula element] |
| 4 | [What makes this bullet strong] | [Formula element] |
| 5 | [What makes this bullet strong] | [Formula element] |

---

### Before/After Comparison

| Original Duty (User's Phrasing) | Polished Bullet |
|--------------------------------|-----------------|
| [User's exact original wording] | [Transformed bullet -- full text] |
| [User's exact original wording] | [Transformed bullet -- full text] |
| [User's exact original wording] | [Transformed bullet -- full text] |
| [User's exact original wording] | [Transformed bullet -- full text] |
| [User's exact original wording] | [Transformed bullet -- full text] |

---

### Assumptions and Flags

> ⚠ [List every metric, number, or scope indicator that was estimated rather than user-confirmed. If none, write "None -- all figures confirmed by user."]

---

Rules

1. Deliver paste-ready bullets, never advice. The output of this skill is complete, formatted resume bullets the user can copy directly onto their resume. Never deliver commentary like "You should try to quantify your achievements" without also demonstrating the transformation on the user's actual content.

2. Every bullet must open with a strong action verb in the past tense (or present tense for current-role ongoing work). Constructions like "Responsible for managing," "Was involved in," "Helped coordinate," or gerund openers like "Managing" are banned without exception.

3. Every bullet must include at least one quantity, scope indicator, or benchmark. Acceptable forms include: dollar amounts, percentages, headcount, number of projects, geographic reach, frequency of output, system scale (e.g., "serving 50,000 monthly active users"), or competitive benchmark ("exceeding the industry average of X"). Bullets with zero quantification are incomplete and must be revised or the user must be asked for a number.

4. Never fabricate specific metrics. If the user cannot recall a number, either ask them to estimate (most people can get within 20-30% of the truth) or use the best available scope language. If you write an estimated number, you must flag it in the Assumptions section. Invented precision -- writing "23%" when the user said "it improved" -- is a resume integrity failure.

5. Limit output to 3-5 bullets per role. A sixth bullet signals inability to prioritize. If the user has genuinely important achievements beyond five, help them identify which five are most relevant to the target role and note the others as secondary. On the rare occasion a role had 6 distinct impact areas that directly match the job description, a sixth is permissible -- but never a seventh.

6. No two bullets within the same role may begin with the same action verb. This is a structural quality rule that signals sophisticated writing and prevents the monotonous repetition pattern common in low-quality resumes.

7. Calibrate verb seniority to actual contribution level. An analyst who ran a report should not have a bullet that says "Spearheaded enterprise analytics transformation." A VP who restructured an entire division should not have a bullet that says "Helped with organizational changes." Inflation and deflation are both errors.

8. Target bullet length is 18 to 25 words. Bullets under 12 words are too sparse to convey meaningful impact. Bullets over 30 words become prose and should be condensed or split. Count words if the bullet feels long.

9. Order bullets by relevance to the target role, not chronologically. The first bullet is prime real estate. It receives the most attention from hiring managers performing six-second resume scans. The most relevant, strongest achievement goes first regardless of when it occurred in the role.

---

Edge Cases

The User Has No Metrics and Cannot Estimate Any

Some roles -- executive assistants, elementary school teachers, internal trainers, nonprofit coordinators -- produce work that is not measured in traditional KPIs. Do not pressure the user to invent numbers. Instead:

• Shift entirely to scope and volume indicators: number of people supported, size of budget administered, frequency of deliverables, number of events organized, geographic reach, number of systems managed
• Use qualitative outcome language when appropriate: "streamlining a 14-step onboarding process" communicates improvement without requiring a percentage
• Use comparative framing if available: "the only coordinator across 3 regional offices" signals scope without a hard metric
• Ask one more targeted question before giving up on quantification: "How many people attended the events you organized?" or "How many employees did you support at once?" Often a number emerges that the user did not realize was a metric.

The User Is Entry-Level or a Recent Graduate

Entry-level users often feel their experience is "not impressive enough" for bullet points. Counter this with accurate framing:

• Academic capstone projects are legitimate resume bullets. Frame them with project scope: team size, dataset size, system complexity, outcome (grade, publication, client deliverable).
• Internship contributions are real work. Quantify by intern cohort size, projects completed, or outputs delivered.
• Part-time jobs and campus jobs contain more metrics than users realize: "Served 80+ customers per shift while maintaining a 4.8/5 satisfaction rating" is a strong bullet for a retail associate.
• Campus leadership roles (club officer, RA, team captain) have clear scope: "Led a 45-member student organization with a $12,000 annual operating budget."
• Use contribution-level verbs (Contributed, Supported, Assisted, Coordinated) honestly -- do not inflate to avoid misrepresentation, which creates interview problems when the user cannot back up the claim.

The User Provides More Than 7 Duties

Excess inputs scatter focus and produce bloated bullet sets. Handle this by:

• Asking the user to identify the 3 accomplishments they are most proud of in the role (not the most common duties -- the actual wins)
• Cross-referencing the full list against the target job description to identify which duties overlap with required skills -- keep only the overlapping ones
• Grouping related duties into a single bullet where appropriate: "Developed and maintained 3 internal reporting dashboards (sales, operations, customer success), reducing manual reporting time by 5 hours per week" consolidates three separate duties into one strong bullet
• Noting which remaining duties you are not converting and why, so the user understands the selection logic

The User's Role Was Primarily Maintenance or Operational (No "Improvements" to Claim)

Many legitimate, skilled roles are about consistency, reliability, and quality -- not transformation. System administrators, quality control inspectors, customer service representatives, and operations staff do not always "improve" things. They maintain them.

Reframe maintenance as reliability achievement:

• "Maintained 99.97% network uptime for a 500-endpoint corporate infrastructure across 3 office locations" is a strong bullet
• "Processed 200+ daily customer transactions with a 0.2% error rate over a 2-year tenure" is a strong bullet
• "Sustained a 4.9/5 average customer satisfaction score across 1,200+ monthly service interactions" is a strong bullet
• Operational roles have metrics in volume (transactions, tickets, units), accuracy (error rate, defect rate, compliance rate), and consistency (uptime, on-time delivery, response time). Ask for these specifically.

The User Cannot Name the Company Due to NDA or Confidentiality

This is common in consulting, defense contracting, financial services, and healthcare. Handle it by:

• Using industry descriptor + size tier: "a Fortune 500 pharmaceutical company," "a Series C B2B SaaS startup," "a federal defense contractor," "a mid-size regional hospital network"
• The metric, achievement, and scope language in the bullet remain unchanged -- only the company name is replaced with the descriptor
• If even the industry is sensitive, use "a confidential client" or "a major enterprise client" -- this is accepted and recognized in consulting resumes specifically

The User Wants to Rewrite All Bullets Across Multiple Roles in One Session

A full resume rewrite session covering 3 or more roles should be sequenced carefully to avoid fatigue and confusion:

• Process one role at a time, delivering the full output format for each before moving to the next
• Ask the user to confirm each set is accurate before proceeding -- this is the quality checkpoint that prevents cascading errors
• Note when bullet themes overlap across roles (e.g., "project management" appears in every role) and flag that diversity of themes across the resume is better than repeating the same accomplishment type across every role
• Suggest that the user use different skill themes for different roles to tell a complete story: technical depth in one role, cross-functional collaboration in another, leadership in a third

The User Provides a Bullet They Already Wrote and Asks for Feedback Only

When the user wants critique rather than a full rewrite:

• Identify which of the three formula elements (Action, Scope, Result) is missing or weak
• Diagnose the specific verb problem if present (passive, gerund, inflated, deflated)
• Point out filler words or length issues with precise line counts
• Offer one complete rewrite demonstrating the improvement -- never give only critique without a demonstration. A concrete example always teaches more than abstract feedback.

---

Example

User Input:

"I was a Customer Success Manager at a B2B software company for 3 years. My responsibilities were: managed a portfolio of enterprise clients, onboarded new customers, ran quarterly business reviews, handled escalations and churn risk, worked with the product team to pass along customer feedback, and tracked usage data in Salesforce and Gainsight. I'm applying for a Director of Customer Success role."

---

Resume Bullets: Customer Success Manager at [B2B Software Company]

Target role: Director of Customer Success Tenure: 3 years

---

Polished Bullets

1. Managed a portfolio of 45 enterprise accounts totaling $3.2M in annual recurring revenue (ARR), maintaining a 94% net revenue retention rate over 3 consecutive years.

2. Designed and delivered structured quarterly business reviews (QBRs) for 20+ accounts per quarter, reducing at-risk account flags by 30% and contributing to 12 upsells totaling $480K in expansion revenue.

3. Onboarded 60+ new enterprise customers across a 3-year tenure by building a standardized 30-60-90 day success playbook, reducing average time-to-value from 11 weeks to 7 weeks.

4. Identified and resolved 18 high-severity churn-risk escalations annually by coordinating cross-functional response teams (Sales, Engineering, Product), retaining an estimated $900K in at-risk ARR per year.

5. Synthesized and submitted 140+ product feedback items from the customer portfolio into Gainsight and Jira, influencing 6 feature releases prioritized by the Product team within 12 months.

---

Why These Work

#	Bullet Strength	Key Technique Applied
1	Opens with portfolio scale ($3.2M ARR) and the retention KPI that Directors live and die by (94% NRR) -- directly maps to the top success metric for the target role	Scope + Primary outcome benchmark
2	QBRs are a core Director competency; quantifying both the volume (20+ per quarter) and the downstream churn reduction (30%) shows strategic as well as operational impact	Volume + Downstream outcome
3	Demonstrates the process-building skill required at Director level ("standardized playbook") and provides a concrete before/after improvement (11 weeks → 7 weeks)	Process improvement with before/after metric
4	"Coordinating cross-functional response teams" signals Director-level influence without direct authority -- a critical competency called out in most Director-level CS job descriptions	Scope + Cross-functional indicator + Dollar retention
5	Product partnership is a differentiator for senior CS candidates; tracking the feedback loop to 6 feature releases quantifies influence in a domain where impact is typically invisible	Volume + Influence outcome

---

Before/After Comparison

Original Duty (User's Phrasing)	Polished Bullet
Managed a portfolio of enterprise clients	Managed a portfolio of 45 enterprise accounts totaling $3.2M in ARR, maintaining a 94% net revenue retention rate over 3 consecutive years
Ran quarterly business reviews	Designed and delivered structured QBRs for 20+ accounts per quarter, reducing at-risk account flags by 30% and contributing to 12 upsells totaling $480K in expansion revenue
Onboarded new customers	Onboarded 60+ new enterprise customers by building a standardized 30-60-90 day success playbook, reducing average time-to-value from 11 weeks to 7 weeks
Handled escalations and churn risk	Identified and resolved 18 high-severity churn-risk escalations annually by coordinating cross-functional response teams, retaining an estimated $900K in at-risk ARR per year
Worked with the product team to pass along customer feedback	Synthesized 140+ product feedback items into Gainsight and Jira, influencing 6 feature releases prioritized by the Product team within 12 months

---

Assumptions and Flags

⚠ Bullet 1: Portfolio of "45 accounts" and "$3.2M ARR" were estimated based on a typical enterprise CSM book of business at a mid-market B2B SaaS company. Confirm your actual account count and ARR figure before using.

⚠ Bullet 2: "30% reduction in at-risk flags" and "12 upsells / $480K expansion" are illustrative estimates. Replace with your Gainsight or Salesforce actuals.

⚠ Bullet 3: "11 weeks to 7 weeks" time-to-value figures are estimated. If you have onboarding milestone data in your CRM, confirm the actual pre- and post-playbook benchmarks.

⚠ Bullet 4: "18 escalations annually" and "$900K retained ARR" are estimates. Cross-check against your Gainsight health score history or Salesforce opportunity data.

⚠ Bullet 5: "140+ feedback items" and "6 feature releases" are estimates. Verify against your Jira submission history or product roadmap records.