promotion-case-builder
Assemble a promotion packet with scope evidence, stakeholder support, and level-criteria mapping.
- License 许可
- MIT
- 最近更新
- 2026-11-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- promotion-case-builder
- category
- career
- description
- Assemble a promotion packet with scope evidence, stakeholder support, and level-criteria mapping.
03 SKILL.md 正文
Overview
Promotions are not rewards for tenure — they are decisions that you are already operating at the next level. Most promotion cases fail because they argue "I deserve it" instead of proving "I'm already doing it." This skill builds a packet that maps your work to the next level's expectations, with evidence a promotion committee can verify.
When to use
-
Preparing for a promotion cycle (6-12 months out or imminent)
-
Writing a promotion packet or self-nomination document
-
Deciding whether you're ready to go up for promotion
-
Recovering from a denied promotion and planning the next attempt
-
Helping a direct report build their case
Core concepts
-
-
- The level rubric is the exam paper. Get the written expectations for the target level. Your packet is an answer key: every criterion gets 1-2 pieces of evidence. No rubric, no case.
-
-
-
- Scope is the currency. Promotions hinge on expanded scope: larger projects, broader influence, mentoring others, driving decisions beyond your team. Show the delta from your current level, not just good performance at it.
-
-
-
- Sustained, not spiky. One heroic quarter rarely suffices. Committees look for 2-3 quarters of consistent next-level performance. Start building the case early.
-
-
-
- Sponsors, not just supporters. You need people with influence in the room saying your name. Identify 2-3 senior stakeholders whose work you materially improved, and make sure they know your promotion is on the table.
-
-
-
- The "already operating" test. For each next-level expectation, ask: "if I were already at this level, what would I be doing differently?" The gap between that answer and your current work is your project list.
-
-
-
- Denial is data. If denied, get the specific gaps in writing within a week. Vague feedback ("need more visibility") is unactionable — push for the concrete behaviors expected.
-
Practical workflow
-
-
- Read the rubric. Obtain the level definitions for current and target level. Highlight the 4-6 differentiators — these are your packet's section headers.
-
-
-
- Run the gap analysis. For each differentiator: evidence you have, evidence you lack, and a plan to close the gap in the next 1-2 quarters. Be brutally honest; committees will be.
-
-
-
- Build the evidence file. For each criterion: project name, your role, scope indicators (team size, users, revenue, cross-team reach), outcomes with metrics, and stakeholder quotes. Aim for 2+ evidence items per criterion.
-
-
-
- Draft the packet narrative. Executive summary (why now, in 5 lines), then criterion-by-criterion evidence, then growth areas with mitigation. Keep it scannable — committees read dozens.
-
-
-
- Line up sponsors. Share the packet with your manager first, then brief 2-3 senior stakeholders. Ask specifically: "would you be comfortable speaking to my scope on X in the calibration?" Make it easy with a one-pager.
-
-
-
- Pre-mortem with your manager. Ask: "what would make this case fail?" Address every objection before the packet is submitted, not after.
-
-
-
- Plan the timeline. Work backwards from the promotion cycle: packet draft, sponsor briefings, manager sign-off, submission. Build in 2-3 weeks of buffer for revisions.
-
Common pitfalls
-
-
- Arguing tenure. "I've been here 3 years" is not a criterion at any level. Committees promote on demonstrated scope, not patience.
-
-
-
- Confusing performance with level. Exceeding expectations at your current level proves you're great at your level — not that you're operating at the next one. The packet must show next-level behaviors.
-
-
-
- No sponsor in the room. The best packet in the world dies if nobody advocates for it in calibration. Politics is part of the process; engage with it deliberately.
-
-
-
- Surprising your manager. If your manager first hears about your promotion ambitions when the packet lands, you've already lost. Align 2+ quarters ahead.
-
-
-
- Thin evidence on influence. Individual output is table stakes. Next levels require evidence you moved others: mentored, unblocked, aligned, decided.
-
-
-
- Giving up after one denial. Most promotions take 2 cycles. Treat denial as a detailed requirements doc for the next attempt — get the gaps in writing and execute.
-
04 同仓库更多 Skills
web-scrape
Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.
design-taste-frontend
tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).