菜单
This skill should be used when preparing a promotion packet, writing self-review for leveling, or asking "am I ready for promotion?", "what does senior/staff look like?", or "help me write my promo doc". Generates level-appropriate impact narratives with scope and influence evidence.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
This skill should be used when the user asks "should I extract this?", "is this abstraction worth it?", "am I over-engineering?", "should I DRY this up?", or when evaluating whether to create a helper, utility, base class, or shared module. Use for any "extract vs inline" decision.
This skill should be used when reviewing a design proposal, RFC, technical plan, or before starting implementation. Use when asking "what could go wrong?", "what are we assuming?", "where is this fragile?", or "what happens if X changes?". Surfaces hidden dependencies and untested beliefs.
This skill should be used when the user asks to "review this code", "check this implementation", "what's wrong with this code", "review my changes", "code review", or when examining code for quality issues.
This skill should be used when asking "is this module too complex?", "why is this hard to change?", "what's causing coupling here?", or before refactoring a tangled system. Use to audit for accidental complexity, circular dependencies, god objects, and layering violations.
This skill should be used when the user asks to "help me debug", "why isn't this working", "this is broken", "debug this", "find the bug", or when systematically investigating an issue.
This skill should be used when asking "should we add this library?", "is this dependency safe?", "should we upgrade X?", or when evaluating npm packages, gems, crates, or any third-party code. Assesses maintenance risk, security, and exit strategy.
| name | promotion-draft |
| description | This skill should be used when preparing a promotion packet, writing self-review for leveling, or asking "am I ready for promotion?", "what does senior/staff look like?", or "help me write my promo doc". Generates level-appropriate impact narratives with scope and influence evidence. |
| argument-hint | target level, review period, or accomplishments to include |
| disable-model-invocation | true |
Build a complete promotion case from recent engineering work.
$ARGUMENTS
| Level | Scope | Typical Evidence |
|---|---|---|
| Junior (L3) | Task/Feature | Completes assigned work, learns codebase |
| Mid (L4) | Project | Owns features end-to-end, mentors juniors |
| Senior (L5) | Team | Shapes team direction, influences architecture |
| Staff (L6) | Org/Multi-team | Drives org-wide initiatives, sets standards |
| Principal (L7) | Company | Industry influence, company-wide strategy |
| Dimension | Evidence Needed |
|---|---|
| Independence | Completes work without daily guidance |
| Scope | Owns full features, not just tasks |
| Quality | Writes production-ready code first time |
| Communication | Explains technical decisions clearly |
| Dimension | Evidence Needed |
|---|---|
| Technical leadership | Others seek your opinion, you shape decisions |
| Ambiguity | Navigate unclear requirements, define solutions |
| Multiplier | Make the team more effective, not just yourself |
| Influence | Drive outcomes beyond assigned work |
| Dimension | Evidence Needed |
|---|---|
| Org impact | Work affects multiple teams |
| Strategy | Connect technical work to business goals |
| Standards | Create patterns others adopt |
| Sponsorship | Senior leadership knows your work |
| Dimension | Evidence Needed |
|---|---|
| Industry | External recognition, conference talks, papers |
| Company strategy | Influence product/technical direction |
| Organization building | Grow senior talent, shape culture |
| Innovation | Novel solutions to hard problems |
For each accomplishment, use the impact-narrative skill to translate technical work into business language. It provides frameworks for quantifying impact, framing for different audiences, and the STAR-L narrative structure. This skill focuses on assembling those translated accomplishments into a level-appropriate promotion packet.
One paragraph answering: "Why should this person be promoted now?"
Formula:
[Name] has consistently operated at [target level] by [key evidence].
Their work on [biggest accomplishment] demonstrates [key dimension].
Promoting them formalizes the scope they're already operating at.
Group accomplishments into themes that demonstrate level-appropriate scope.
| Theme Type | Example |
|---|---|
| Technical excellence | "Architected scalable solutions" |
| Leadership | "Elevated team capabilities" |
| Business impact | "Directly enabled revenue growth" |
| Cross-functional | "Partnered across org boundaries" |
| Innovation | "Introduced novel approaches" |
For each theme, 2-4 specific accomplishments.
Bullet Formula:
[Strong verb] + [what] + [scope/scale] + [measurable result] + [so-what]
Level-Appropriate Verbs:
| Level | Verbs |
|---|---|
| Mid | Built, implemented, shipped, fixed, improved |
| Senior | Designed, led, drove, mentored, standardized |
| Staff | Architected, established, influenced, championed, transformed |
| Principal | Pioneered, defined, shaped, evangelized |
Concrete proof of operating at target level scope.
| Scope | Evidence Types |
|---|---|
| Team | Code reviews given, mentoring, team process improvements |
| Multi-team | RFCs reviewed, cross-team projects, shared libraries |
| Org | Standards adopted, architecture decisions, hiring influence |
| Company | Company-wide tools, external visibility, exec presentations |
Who can vouch for this work?
| Stakeholder | What They Can Speak To |
|---|---|
| Manager | Day-to-day performance, growth |
| Skip-level | Strategic impact, leadership |
| Peers | Collaboration, technical respect |
| Cross-functional | Impact outside engineering |
| Reports | Mentorship, leadership style |
# Your commits in review period
git log --author="[you]" --since="[start date]" --oneline
# Files you've touched most
git log --author="[you]" --since="[start date]" --name-only --format="" | sort | uniq -c | sort -rn | head -20
# Your PRs with reviews
gh pr list --author="[you]" --state=merged --limit=100
# Your impact events
grep "tool_write" ~/.claude/dev-os-events.jsonl | jq -r '.payload.files[]' | sort | uniq -c | sort -rn
# Large changes (architecture-level work)
grep "large_change" ~/.claude/dev-os-events.jsonl
# Decisions documented
grep "decision_tradeoff" ~/.claude/dev-os-events.jsonl
| Pitfall | Problem | Fix |
|---|---|---|
| Activity, not impact | Lists tasks done | Connect to outcomes |
| Solo hero | All "I" statements | Show multiplier effect |
| Recency bias | Only recent work | Cover full review period |
| Missing scope | Work without context | Explain why it mattered |
| Vague claims | "Improved performance" | Add numbers, specifics |
| Wrong audience | Too technical | Lead with business impact |
[One paragraph summary statement]
Scope: [Team/Multi-team/Org]
Evidence: [Specific artifacts, links, quotes]
Scope: [Team/Multi-team/Org]
Evidence: [Specific artifacts, links, quotes]
Scope: [Team/Multi-team/Org]
Evidence: [Specific artifacts, links, quotes]
| Dimension | Evidence |
|---|---|
| Technical leadership | [examples] |
| Cross-team influence | [examples] |
| Mentorship/multiplier | [examples] |
| Name | Role | Can Speak To |
|---|---|---|
| [name] | [title] | [topic] |
[Any areas where evidence is thin, with plan to strengthen]
Ready for promotion: [Yes / Not yet / Needs more time]
If not yet: [Specific gaps and timeline to address]