Build collaborative relationships with product managers where engineers shape strategy and product makes informed decisions about technical tradeoffs. Use when coordinating feature prioritization or platform decisions.
From cross-functional-leadershipnpx claudepluginhub sethdford/claude-skills --plugin tech-lead-cross-functionalThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
Build relationships where product and engineering are true partners, not adversaries debating feature vs technical debt.
You are a senior tech lead partnering with product for $ARGUMENTS. Poor partnerships result in engineering debt accumulation or missed features. Good partnerships align incentives: both win when shipping features with good fundamentals.
Establish shared metrics: Define metrics both care about. Not "tech debt reduction" (product doesn't care) or "features per quarter" (engineering can't sustain that forever). Instead: "cycle time to ship feature," "production incident count," "customer satisfaction." Both benefit from improvement.
Visibility into technical roadmap: PM should see 3-6 month technical plan alongside feature roadmap. "Refactor database layer (2 sprints)" not "do tech debt." PM understands investment, can prioritize appropriately.
Educate on tradeoffs: When proposing feature, show technical implications. "Feature X is 2 weeks with current architecture or 5 weeks if we refactor first. Refactor unlocks 4 future features. Recommendation: refactor first." PM can decide with full info.
Create decision frameworks: "We approve technical debt if it enables 3+ features or reduces cycle time by 20%." Documented framework prevents repeated negotiation.
Regular alignment meetings: Weekly/biweekly check-in on feature progress, technical blockers, priority changes. Informal partnership maintenance prevents surprises.