Install any skill in seconds. Free to start, no credit card required.
Get Started Free →refoundai/stakeholder-alignment
Help users master the art of leading without formal authority by identifying stakeholder incentives, neutralizing conflict through connection, and using co-creation to build shared ownership.
Passed 22 of 22 test cases with the skill, and 15 of 22 without it.
and 7 more in the full report
7 fixed15 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our cross-functional teams are constantly arguing during roadmap reviews because everyone has different local priorities. Can you outline a conflict neutralization and decision-making guide? I'd like a structured response that provides: concrete conversational scripts for shifting pushback into curiosity, a breakdown of consensus vs. collaboration decision modes, and a checklist of common mistakes PMs make when trying to secure buy-in.
| Checked | Without skill | With skill |
|---|---|---|
| Incorporates the 'Yes, and...' technique to validate collaborator perspectives before introducing constraints. | Missed | Passed |
| Explains the distinction between consulting, collaboration, and consensus decision-making modes. | Missed | Passed |
| Highlights confusing consensus with collaboration as a mistake to avoid. | Passed | Passed |
| Identifies presenting finished solutions without early stakeholder involvement as a mistake to avoid. | Passed | Passed |
The instructions your model reads when the skill loads.
Drive cross-functional momentum by mapping incentives and co-creating solutions
Help the user with stakeholder alignment using insights from 30 guests and posts across Lenny's Podcast and Newsletter.
Adam Grenier: "If you approach it with that 'Yes, and...', it's often still true. It's like, oh, both of these things can be true at once. You could have a different goal than I have, or you have a system problem local to you that is important to you and it's not important to me."
Use the Yes and technique to validate a collaborator perspective before adding your own constraints. This allows competing priorities to coexist without stalling progress or damaging the rapport between teams.
Ami Vora: "It means that every meeting you walk into, you're probably not going to get bored and I get bored a lot, but if you assume that every person there knows something that you don't know, then it's not just wait to get to the right answer, it's like, discover the thing that they know that you don't know and it becomes just a little bit of uncovering."
Approach disagreements by assuming your colleague possesses unique information that you lack. Transform potential conflict into a discovery process by responding to opposing opinions with curiosity rather than defense.
Dr. Becky Kennedy: "He kind of joins my world where I'm embedded in my own priorities and by doing that forms a bridge, that's what connection is. So I can kind of walk back over to his world with him to do something that's a priority in his world."
Cooperation is built when you acknowledge and join another person reality before asking them to join yours. Establish this connection bridge to ensure partners feel heard before you attempt to redirect their behavior.
Mihika Kapoor: "We lean heavily into designing and prototyping even before a project gets a green light. If you and your team do your job correctly, what does the world look like?"
Secure buy-in for zero-to-one ideas by investing in high-fidelity prototypes and mocks before seeking formal resourcing. Making the vision feel real through visual evidence is more effective than abstract descriptions.
Naomi Gleit: "Of course, I'm sure there's hundreds of docs associated with the project, but there needs to be one canonical doc. Everyone should know exactly where the canonical doc is. That's the one place I can go to get all the information I need about a project and it will link to all the other docs, things on the canonical doc are."
Eliminate conflicting information by creating one central document that serves as the definitive source of truth for the project. This prevents stakeholders from working off different interpretations of the same goal.
test cases passed, vs 15 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.