Stats
Actions
Tags
From cross-functional-leadership
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cross-functional-leadership:technical-product-partnershipThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Build relationships where product and engineering are true partners, not adversaries debating feature vs technical debt.
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.
npx claudepluginhub sethdford/claude-skills --plugin tech-lead-cross-functionalUse this skill when the user asks about "working with engineers as a PM", "how technical should a PM be", "I feel out of my depth with engineers", "how to earn engineering trust", "how to read code as a PM", "should I learn to code", "bridging the gap with engineering", "technical credibility for PMs", or wants to develop the skills to partner more effectively with engineering teams. Do NOT use this skill for general career progression questions — use solo-to-cpo for that.
Guides architecture decisions, build-vs-buy evaluations, tech stack planning, tech debt prioritization, PRD writing, and technical strategy communication.
Build multi-quarter technical roadmaps aligned with business goals, clearly showing strategic investments, trade-offs, and dependencies. Use when planning longer-term technical direction, communicating with stakeholders, or aligning engineering capacity with business priorities.