nominal-group-meeting
Use when meetings are dominated by the loudest voices, when seeking diverse perspectives on roadmaps or forecasts, or when groupthink is hindering decision quality
Discover Testing & security skills, compare source repositories and read the instructions for each workflow.
Use when meetings are dominated by the loudest voices, when seeking diverse perspectives on roadmaps or forecasts, or when groupthink is hindering decision quality
Treat company culture as a product you build for employees. Iterate on it using feedback loops (NPS), identify bugs, and evolve it—don't try to preserve a static version.
Restructure organizations by eliminating divisions and GMs, organizing strictly by function to reduce politics and ensure experts lead experts. Use when sensing slowdown, bureaucracy, or fracturing user experie...
Use when designing retention mechanisms, habit loops, or auditing why users drop off despite engaging with core features, to structure gamification beyond superficial badges
Use when defining new product lines or major pivots, when single PR/FAQ leads to tunnel vision, or when giving leadership real strategic choices instead of yes/no decisions
Use when decisions seem to require years to evaluate, when hiding behind long-term vision to avoid accountability, or when struggling to learn from venture/product bets in real-time
Use data to establish business observability (diagnosing problems) but use creative design thinking to solve them (treatment). Resolves the conflict between data-driven and intuition-driven product development.
To replicate startup speed in large companies, launch new products as separate legal entities (C-Corps) with distinct brands, reporting directly to the CEO, bypassing standard chains of command.
A metaphor for managing change—remain rooted in core purpose while being extremely flexible in tactics, absorbing storms of change without breaking. Use during pivots, restructures, or industry upheavals.
When firing someone, separate the business decision from humane implementation. Act as their talent agent—actively use your network to help them find their next role.
Use when hiring for early-stage high-growth companies, when filtering out comfort-seekers, or when building teams tackling unsolved technical challenges
Use when joining a new company, taking over legacy products, or proposing strategies that were previously attempted to avoid repeating past mistakes
Understand that product work happens at three levels (Impact, Execution, Optics) and conflicts arise when people argue from different levels. Use to diagnose team misalignment.
Treat product usage costs (even high LLM costs) as marketing expenses. Remove all friction to access, let users create social proof. COGS becomes CAC. Ship to create noise.
Use when building AI-native products where user data can fine-tune performance, when static software fails to improve with usage, or when designing products that learn from interaction
A three-level framework to gauge growth quality. Level 1: Core Action completion. Level 2: Retention via accruing benefits and mounting loss. Level 3: Self-perpetuating loops. Don't optimize for MAU—optimize fo...
View yourself as an entity with infinite dimensions rather than a single good/bad identity. Strengths and weaknesses are often the same trait in different contexts. Use during performance reviews or when receiv...
Use when designing AI agents or chatbots, when raw model outputs feel like a black box, or when building natural language interfaces that need structure and trust
Use when building zero-to-one products, when the solution shape is undefined, or when teams are applying growth metrics too early
Use in rapidly evolving industries like AI where 6-month plans become obsolete, when needing to balance direction with agility, or when traditional annual roadmaps fail
A technique to translate harsh internal thoughts into constructive external dialogue. Say the thing you think you cannot say—but detoxify it first. Use when sensing tension or unspoken issues in meetings.
Categorize tasks into Leverage (10x), Neutral (1x), and Overhead (
Use when facing conversion plateaus, expanding to new markets, or when aggregate data fails to reveal growth bottlenecks, to identify high-leverage improvements by focusing on worst-case users
Shift from rigid roles (PM, Designer, Engineer) towards a model where individuals use AI to bridge skill gaps, enabling smaller and flatter teams. Use in early-stage startups or innovation units where speed is...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.