Use this skill when working with designers, product managers, business stakeholders, or non-technical team members. Trigger on keywords: working with PM, designer collaboration, stakeholder, business requirements, cross-team, non-technical, translate requirements, align with product, pushback from business.
SkillScore87Maintained
Automatic
◆Product Management pack
Last verified 8/3/2026
What it changes
Passed 20 of 23 test cases with the skill, and 18 of 23 without it.
Without skill78%
With skill87%
Checks it passed that the model alone missed
Recommends providing honest estimates without padding or optimism.
Compares the time cost of fixing now versus fixing a production failure.
Initiates disagreement by asking to understand the underlying reasoning.
3 fixed17 passed either way2 still failing1 broke
Pass-rate lift
+9 pp
Tokens
+19%
Agent turns
0%
Response time
+5%
Model gemini-3.6-flashMeasured 8/3/2026v120 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
A product director decides to remove mandatory two-factor authentication from the admin panel to simplify onboarding. What is the very first step you should take to voice disagreement?
What was checked, without and with the skill
Checked
Without skill
With skill
Initiates disagreement by asking to understand the underlying reasoning.
Missed
Passed
case-17 · gemini-3.6-flash · 8/3/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md76 linessingle file
Cross-Functional Collaboration
The Translation Problem
Developers think in systems. PMs think in outcomes. Designers think in experiences. Executives think in risk and cost. None of these are wrong — they're just different lenses on the same reality.
Your job: Translate fluently between all of them.
Working with Product Managers
What PMs Need From You
Honest estimates (not optimistic, not padded)
Technical risk flagged early — surprises are worse than bad news
Alternatives when you can't build exactly what they ask
Business impact framing when you need to deprioritize tech debt
What You Need From PMs
Clear acceptance criteria before you start
Priority when scope is too large for the sprint
Access to users when requirements are ambiguous
Decision authority on trade-offs they create
Handling Unrealistic Requests
WRONG: "That's not possible"
RIGHT: "I can build [what they asked] in 3 weeks, or
I can build [simpler version that achieves the same goal]
in 3 days. Which would you prefer given the timeline?"
Always offer an alternative, not just a no.
Working with Designers
Collaboration Principles
Review designs before implementation starts — not after