promotion-packet
Build a promotion case that proves you're already operating at the next level. Use when asked to write a promo packet/case, prepare for a promotion committee, or make the case for a level-up or title change. Produces a promotion packet — the level-up thesis, evidence mapped to each next-level competency, scope/impact highlights, peer-quote slots, and the gaps to close before submitting.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/promotion-packet && cp -r /tmp/promotion-packet/plugins/pm-career/skills/promotion-packet ~/.claude/skills/promotion-packetSKILL.md
# Promotion Packet Skill
Promotions reward demonstrated operation at the next level, not potential or tenure. The committee asks
one question: *is the evidence that they're already doing the next-level job?* This skill builds the
packet that answers it — mapping your work to each competency at the **target** level, surfacing the
scope and impact that prove it, and honestly flagging the gaps so you submit when you'll actually win.
## Required Inputs
Ask for these only if they aren't already provided:
- **Current level → target level**, and the **ladder/rubric** for the target level (the competencies it requires).
- **Your evidence** — accomplishments with impact (a [`brag-doc`](../brag-doc/SKILL.md) is ideal input).
- **Scope** — the breadth of your influence (self → team → multi-team → org).
- **Supporters** — peers/stakeholders who can vouch, and for what.
## Output Format
### Promotion Packet — [name], [current] → [target]
**1. Thesis** — 2–3 sentences: you are *already operating* at [target], and here's the through-line of evidence. Promotion = recognition of current reality, framed this way.
**2. Competency evidence** — the core of the packet; one row per target-level competency:
| Target-level competency | Evidence (specific, with impact) | Scope |
|---|---|---|
| e.g. Drives multi-team initiatives | Led the X program across 3 teams → [outcome] | multi-team |
Every competency needs **at least one strong, recent, evidenced example** — gaps here are what sink packets.
**3. Impact highlights** — your 3–4 strongest wins, quantified, framed at the target level's expected scope.
**4. Peer/stakeholder support** — who will vouch and the specific thing each speaks to (leave quote slots).
**5. Gap analysis (private, pre-submit)** — competencies where the evidence is thin or stale, and a plan to close them. Submitting with visible gaps wastes a cycle; this section decides *whether it's time*.
## Quality Checks
- [ ] The case is framed as "already operating at the next level", not "ready for / deserves it"
- [ ] Every target-level competency has at least one strong, recent, evidenced example
- [ ] Impact is quantified and framed at the **target** level's scope, not the current one
- [ ] Named supporters are mapped to specific competencies they can speak to
- [ ] A private gap analysis honestly flags weak spots and whether to submit now or next cycle
## Anti-Patterns
- [ ] Do not argue from tenure or effort ("I've been here 3 years", "I work hard") — committees reward demonstrated scope and impact
- [ ] Do not leave a target competency unevidenced — one unbacked competency is the gap reviewers latch onto
- [ ] Do not frame it as potential — "could do the next level" loses to "is already doing it"
- [ ] Do not pad with low-level wins — they signal you're operating *below* the target level
- [ ] Do not submit with known gaps to "see what happens" — a failed packet is costly; close gaps first
## Based On
Engineering/IC ladder promotion practice — operate-at-level evidence mapped to a competency rubric.Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.
Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.
Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
Plan a trip that actually works with a disability or access need — confirm real accessibility (not just 'accessible' labels), book the assistance in advance, plan for equipment and medication, and build in the contingencies for when access breaks down. Use when someone says 'plan an accessible trip', 'travelling with a wheelchair/disability', 'book assistance for my flight', or 'will this hotel actually work for me'. Produces an access-verified itinerary, an assistance-booking checklist, an equipment/medication plan, and contingency scripts. Verify specifics with providers.
Request a reasonable accommodation at work or in education — frame it around the barrier and the adjustment (not your diagnosis), cite the right process, and navigate the back-and-forth constructively. Use when someone says 'I need a workplace accommodation', 'request reasonable adjustments', 'ADA/Equality Act accommodation', or 'how do I ask for accommodations for my disability/condition'. Produces the request letter, a barriers-and-adjustments map, disclosure guidance, and a plan for the interactive process. Not legal advice — routes to the formal process and to advocacy where needed.
Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.