Strategies for working effectively with managers and executives drawn from 35 product leaders.
Works with
Proactively communicate upward with regular updates on priorities, blockers, and progress rather than waiting to be asked, using consistent formats like weekly emails
Bring recommendations and point of view to your manager instead of just problems, reducing their cognitive load and positioning yourself as an ally
Understand your manager's priorities and two levels up to tailor communication
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionmanaging-upExecute the skills CLI command in your project's root directory to begin installation:
Fetches managing-up from refoundai/lenny-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate managing-up. Access via /managing-up in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
612
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
612
stars
Help the user work effectively with their manager and executives using strategies from 35 product leaders.
When the user asks for help managing up:
Boz: "The advice I give more frequently than any other is for people to more directly leverage their leaders." Your primary job is to achieve results. Your manager has tools and authority to clear paths. Ask for help to bulldoze blockers rather than trying to solve everything yourself.
Casey Winters: "People just way under communicate upward. Then they complain that executives are out of touch when they aren't telling executives what they need to know." Send weekly "state of" emails with priorities, blockers, and thoughts. Frame updates as "no response required" to keep leaders informed without creating burden.
Fareed Mosavat: "You should understand your boss's priorities and your boss's boss's priorities. Eventually, that means you have to know what the board is thinking." Build a mental model of how your work creates leverage in the larger system. Tailor communication to address senior leadership's specific concerns.
Wes Kao: "When you ask 'Hey manager, what should we do?' you're putting a lot of cognitive load on them. Instead say 'Hey manager, here's what I think we should do.'" Present a point of view even if it's just an initial hunch. Provide insights and takeaways, not just raw data.
Boz: "We used HPM - Highlight, People, Me. Every manager at Facebook would send this to their manager." Use consistent formats. Ask your manager: "How do you like to get information about me?" Consider weekly emails with priorities, blockers, and general thoughts.
Ethan Evans: "Management can be a lonely job. Having an ally is a huge weight off people's shoulders." Recognize managers are overwhelmed. Move from asking "How can I help?" to suggesting specific solutions. Keep them in the loop by proactively fixing problems before they ask.
Casey Winters: "You have to start with chapter one, which is what part of the company strategy are you working on? What metrics are you trying to improve? What assumptions are you making?" Find the last point that's obvious to the audience and build from there. Don't dive into "Chapter 6" details without the strategic context.
Dylan Field: "The more concrete an artifact is or the more you can debate something, the better. I ask for examples a lot." Present designs and docs rather than abstract ideas. If you lack data for a follow-up question, pause to find the answer rather than guessing.
Itamar Gilad: "If you run a secret experiment and come back with data, either they get extremely mad at you... or more commonly, they're pleasantly surprised." Use evidence to flip a leader's perspective rather than engaging in a battle of opinions.
Jiaona Zhang: "It's understanding the spirit of what they're trying to achieve. Being able to go back with 'I understand the spirit, but here's a better way to achieve it.'" Align on the underlying goal first. Present automated or scalable alternatives rather than just saying no.
Noah Weiss: "High involvement at the start for strategy and at the end for quality, with autonomy in the middle." Involve founders early for strategic buy-in on goals. Bring them back at the end to ensure the product meets quality standards.
Peter Deng: "Say you're going to do the thing, say that you're doing the thing, and then say that you did it." This repetitive communication ensures alignment and provides opportunities for course correction.
For all 50 insights from 35 guests, see references/guest-insights.md
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Registry listing for managing-up matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: managing-up is focused, and the summary matches what you get after install.
managing-up fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in managing-up — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend managing-up for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added managing-up from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: managing-up is the kind of skill you can hand to a new teammate without a long onboarding doc.
managing-up reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: managing-up is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: managing-up is focused, and the summary matches what you get after install.
showing 1-10 of 41