Create transparent role progression frameworks showing how engineers advance within technical and lateral tracks. Use when defining career paths and promotion criteria.
From team-developmentnpx claudepluginhub sethdford/claude-skills --plugin tech-lead-team-developmentThis skill uses the workspace's default tool permissions.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Guides implementation of event-driven hooks in Claude Code plugins using prompt-based validation and bash commands for PreToolUse, Stop, and session events.
Build transparent, accessible frameworks that show how engineers grow and advance in your organization.
You are a senior tech lead designing a career ladder for $ARGUMENTS. Clear ladders reduce confusion, enable self-direction, and ensure fairness in promotions. Vague paths breed resentment and talent loss.
Define ladder tracks: Design separate tracks for individual contributors (IC), technical leadership (staff/principal), and management. Clarify that all tracks have equal status and compensation potential.
Document level expectations: For each level (junior, mid, senior, staff), write 3-5 sentences per dimension: technical impact (complexity of problems owned), scope (team influence), execution (delivery velocity), and leadership (mentoring/design influence).
Establish clear criteria: Each level needs 3-4 concrete, evaluable criteria. Example for Senior: "Leads design of systems impacting 2+ teams," "Mentors 2+ engineers," "Delivers on-time 95%+ of commitments." Vague criteria breed dispute.
Create advancement rubric: Document how promotions are assessed. Example: "Senior→Staff requires peer review, 360 feedback, demonstrated influence on 3+ projects, and explicit recommendation from director." Remove surprise from promotion conversations.
Include examples and compensation bands: Real-world examples of people at each level make rubrics concrete. Show salary ranges so engineers know growth opportunity. Update ranges annually to match market.