plugins/executive/skills/first-90-days/SKILL.md
Provides a structured framework for new-role transitions — accelerating credibility, avoiding the Savior Trap, and reaching the breakeven point where value contribution exceeds consumption. Use when starting a new job, joining a new team, or taking on expanded responsibilities.
npx skillsauth add joellewis/skill-library first-90-daysInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
The first 90 days is a critical window for building credibility, momentum, and strategic alignment. This skill provides a structured framework to accelerate the transition, avoid common pitfalls like the "Savior Trap," and reach the "Breakeven Point" where value contribution exceeds consumption.
The primary goal of a transition is to reach the point where you have contributed as much value to the organization as you have consumed during your onboarding. Speed to value is the key metric.
Mentally transition out of your old role. Do not rely on the skills and behaviors that made you successful in the past. Identify the specific new capabilities required for this unique context.
Resist the urge to make immediate changes (The Savior Trap). Spend the first 30 days listening, asking questions, and understanding the "oral history" of the team. Changes made without context create second-order friction.
Explicitly communicate how you work. Sharing a "Guide to Working with Me" reduces friction by clarifying your communication preferences, decision-making style, and "unwritten rules" for your team.
Before implementing a new process or policy, ask "And then what?" for the 10-month and 10-year horizons. Consider how the existing ecosystem (other departments, suppliers, long-term employees) will react.
Identify the specific context of the role to determine your strategy. (Source: Watkins, Ch. 3)
Systematically map the knowledge gaps. (Source: Watkins, Ch. 2)
Identify 1-2 small, visible projects that build credibility. (Source: Watkins, Ch. 6)
Define how you and the team will communicate and decide. (Source: Johnson, Ch. 1)
Align expectations and secure resources. (Source: Watkins, Ch. 4)
stakeholder-discovery — To map the "informal" power structure of the new organization.rapport-builder — To build trust in initial 1:1s.influence-architect — To build coalitions for early wins.databases
Use when a deliverable needs structured stakeholder sign-off before finalization—runs the pre-read, feedback-type alignment, and conflict-resolution protocol.
development
Use when you need to map who has power, who will be affected, and what motivates each party — produces a stakeholder map as an analytical artifact. This skill identifies and categorizes stakeholders; it does not persuade or influence them (use influence-architect for that).
testing
Use when beginning analytical or strategic tasks, facing undefined problems, or facing analysis paralysis—requires explicit problem definition before proceeding.
testing
Use when translating a product vision into engineering requirements—enforces the Working Backwards PR/FAQ method, requiring a customer-facing press release before any technical spec.