SkillVaultskills Browse all 500 skills

Career · Version 1.3.0 · Reviewed 2026-08-02

Staff Engineer Growth Planner

Improve scope-gap assessment and leverage opportunity mapping with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Creates evidence-based growth plans for senior engineers targeting staff scope across technical direction, organizational leverage, influence, and ambiguity.

₹99 one-time

Get this skill archive

What this skill helps you do

  • Scope-gap assessment
  • Leverage opportunity mapping
  • Quarterly growth planning

How Staff Engineer Growth Planner works

You provide

Current artifact, target level, and verifiable outcomes

It inspects

Evidence strength and scope honesty behind scope-gap assessment

It decides

A leverage opportunity mapping rewrite with no invented achievements

You verify

Every claim survives a skeptical follow-up question

What it checks first

Staff Engineer Growth Planner creates evidence-based growth plans for senior engineers targeting staff scope across technical direction, organizational leverage, influence, and ambiguity. Use it when the work involves Scope-gap assessment, Leverage opportunity mapping, Quarterly growth planning.

  1. Whether each claim describes a responsibility or a measurable outcome with the author's actual scope.
  2. Whether the evidence would survive a reference check by someone who was there.
  3. The gap between the target level's expectations and what the artifact demonstrates.
  4. Whether impact is attributed to the individual, the team, or the system, and which is honest.

Failure modes it recognizes

  • Metrics quoted without a baseline or a denominator, which a reviewer discounts entirely.
  • Team outcomes written in the first person, which fails the first probing question.
  • A packet listing activity rather than the decisions the person owned.
  • Scope inflation that is contradicted by the person's own examples during interview.

Answers it will reject

  • Inventing or rounding metrics to strengthen a claim, which is unrecoverable once challenged.
  • Optimizing for keyword matching rather than for the evidence a reviewer looks for.
  • Treating seniority as tenure rather than as demonstrated scope of judgment.

Decision rules it applies

  • Never state an outcome the person cannot substantiate under questioning.
  • Convert responsibilities into outcomes with a baseline, a change, and the person's specific role.
  • Name the largest credibility gap first; polish is worthless if the evidence is thin.

Evidence it asks for

  • For each claim, ask what a skeptical reviewer would request as proof.
  • Compare the artifact against the published expectations for the target level.
  • Rehearse the two questions most likely to expose an overstated claim.

The method inside

  1. Establish the current state and the constraint that actually limits scope-gap assessment.
  2. Separate the requested solution from the underlying problem in leverage opportunity mapping, and name the assumptions carrying the most risk.
  3. Compare only viable options for quarterly growth planning against weighted constraints, cost of reversal, and operational ownership.
  4. Commit to a sequenced recommendation with success criteria, guardrails, and the observation that would reverse it.

Deliverables

  • Scope-gap assessment assessment
  • Leverage opportunity mapping decision and action plan
  • Quarterly growth planning verification checklist

Evidence requirements

  • Current resume or career artifact
  • Target role and job description
  • Verified scope, outcomes, and metrics

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

I am a senior engineer aiming for staff in twelve months. Build a growth plan from my current responsibilities and feedback.

Expected output

Your current work shows depth but remains bounded to one team. The next two quarters should add one cross-team technical strategy, one reusable platform investment, and a decision forum where you lead alignment without owning every implementation...

Boundaries and compatibility

Ideal for

  • Scope-gap assessment: produce a decision or artifact grounded in supplied evidence.
  • Leverage opportunity mapping: produce a decision or artifact grounded in supplied evidence.
  • Quarterly growth planning: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Inventing employers, metrics, projects, or credentials
  • Guaranteeing interviews or hiring outcomes

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.