promotion-draft

Structure accomplishments into impact themes aligned with level expectations.

3|Updated Nov 19, 2025
One-click install
npx skills add https://github.com/meaganewaller/.dotfiles --skill promotion-draft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: promotion-draft
Source: https://github.com/meaganewaller/.dotfiles/tree/main/home/.claude/skills/common/promotion-draft
Command: npx skills add https://github.com/meaganewaller/.dotfiles --skill promotion-draft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps engineers prepare comprehensive promotion packets by structuring their accomplishments, aligning them with level expectations, and identifying evidence of scope and impact.

Core Features & Use Cases

  • Promotion Packet Structure: Provides a template for summary statements, impact themes, and accomplishment bullets.
  • Level Expectations: Outlines scope and key dimensions for Junior, Mid, Senior, Staff, and Principal levels.
  • Evidence Gathering: Offers guidance on collecting proof from Git history, dev OS events, and documents.
  • Use Case: An engineer aiming for Senior level can use this Skill to organize their project contributions, leadership examples, and cross-team influence into a compelling narrative for their promotion review.

Quick Start

Use the promotion-draft skill to help me write my promotion doc for Senior level.

Frequently Asked Questions about promotion-draft

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a promotion packet for a Senior software engineering role?

Writing a promotion packet involves structuring your project contributions, cross-team influence, and technical leadership into impact themes that align with Senior level scope expectations. This Skill provides templates for summary statements and accomplishment bullets to help you build a compelling career progression narrative.

What should I include in a self-review for career growth and leveling?

A self-review for career growth should include structured accomplishments mapped to level-specific expectations, along with evidence of your scope and influence. You can gather proof from Git history, development OS events, and project documents to identify readiness gaps for your progression.

What is the best way to structure an impact narrative for a performance review?

Structuring an impact narrative for a performance review requires organizing your technical leadership and project contributions into clear impact themes. This Skill aligns your evidence with level expectations to articulate your scope and cross-team influence for the promotion review committee.

Can I use this to identify gaps in my readiness for a Staff engineer promotion?

Yes, you can assess your readiness for a Staff engineer promotion by comparing your current accomplishments against level-specific scope expectations. This Skill helps identify gaps in your technical leadership and cross-team influence by mapping your evidence to required career progression dimensions.

How do I gather evidence for my software engineering promotion doc?

Gathering evidence for your promotion doc involves collecting proof of your scope and impact from your Git history, development OS events, and project documents. This Skill offers guidance on organizing this technical evidence into accomplishment bullets that support your level expectations.

Does this promotion drafting approach work for Junior to Principal leveling?

Yes, this approach outlines scope and key dimensions for Junior, Mid, Senior, Staff, and Principal levels. It structures your accomplishments into impact themes and aligns them with the specific expectations for each engineering level to support your career progression.