running▌

Frameworks for running more effective meetings drawn from 40 product leaders. \n \n Separates meetings into strategic (open-ended discussion) and operational (structured updates) to prevent mixing incompatible formats \n Emphasizes that meetings should only host discussion; discovery and decision-making belong in async channels \n Provides structured closing questions (what was decided, who does what by when, who else needs to know) to ensure alignment and prevent re-meetings \n Includes guidanc

For production apps requiring reliable, unlimited RPC access.

Framework-based guidance for planning and running productive team offsites. \n \n Draws on five product leader frameworks covering purpose clarification, team readiness assessment, structure design, and logistics \n Emphasizes removing teams from day-to-day routines, using physical collaboration tools like whiteboards, and balancing strategy work with social connection \n Flags common pitfalls including overpacked agendas, soft skills training that masks underlying conflicts, and infrequent in-p

Frameworks for running productive one-on-one meetings drawn from seven product leaders. \n \n Emphasizes coaching over advising: shift to curiosity and empower reports to solve problems rather than providing immediate answers \n Recommends dedicated deep-dive conversations on past (life story), future (dreams), and present (career action plan) to build long-term development \n Includes monitoring for joy and recovery as performance indicators; treat lack of daily joy as a risk requiring interven

Structured decision-making frameworks and processes drawn from 65 product leaders. \n \n Guides users through decision classification (reversible vs. irreversible), blocker identification, and framework selection to move from deliberation to action \n Covers core principles including making implicit assumptions explicit, using curiosity loops for advice gathering, and distinguishing when data-driven analysis ends and conviction takes over \n Flags common pitfalls: analysis paralysis, decision by

Framework for running design reviews using feedback hierarchy and structured critique. \n \n Prioritize feedback by value first (does it solve the problem?), then usability, then delight; defer aesthetic concerns until core value is validated \n Assign senior leaders as project sponsors to oversee quality through live demos and review 100% of shipped screens before launch \n Structure reviews around specific feedback requests; ask presenters exactly what type of input they need rather than openi

Use this skill for the specific workaround where Claude Code keeps its Anthropic-shaped client behavior, but the actual backend traffic is sent to a local LiteLLM proxy and then forwarded to GitHub Copilot.