Discover Development skills, compare source repositories and read the instructions for each workflow.
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...
A hierarchical framework forcing alignment from top down—Mission, Company Strategy, Product Strategy, Roadmap, Goals. Strategy precedes goals; goals measure progress against a strategy.
Use when managing growth experiments, when a product area faces diminishing returns, or when deciding whether to generalize or specialize in career or product strategy
Use before launching products or signing contracts, when needing to combat sunk cost fallacy, or when standard pre-mortems fail to change behavior
Use when designing onboarding flows, writing marketing copy, or creating the first-mile product experience to capture attention from indifferent users
Use for core product areas defining long-term brand value, when A/B tests are fragmenting product vision, or when short-term optimization threatens architectural integrity
Use before starting a company with co-founders, when bringing on a new co-founder, or annually as a relationship health check to prevent the 65% of startup failures caused by co-founder conflict
Deliberately impose artificial constraints and simplification rules to counteract organizational drift toward complexity. Complexity kills companies—fight it with binary rules.
Use when navigating large organizations where official strategy seems doomed but leadership isn't ready to hear it, when dealing with status updates that feel disconnected from reality, or when feeling burned o...
A feedback approach where the manager acts as a curious investigator rather than an authoritarian expert, using observation and questions to help direct reports self-diagnose issues. Use during 1:1s and perform...
Stop optimizing for positive ROI and start focusing on minimizing opportunity cost—choosing the BEST possible use of time, not just a good one. Use during quarterly planning and roadmap prioritization.
Instead of waiting for a post-mortem after failure, imagine the project has already failed spectacularly and work backward to uncover hidden risks. Use before kicking off any major initiative, product launch, o...
In an era where AI lowers the cost of building software, viability is obsolete. The differentiator is joy and emotional connection. Prioritize "Wow" over "Aha"—brand is product interaction.
High-growth careers are J-Curves, not stairs—you jump off a cliff (take risk), struggle for 6-9 months (bottom of J), then shoot up exponentially. Use when deciding between safe promotion vs stretch role.
Use when exhausted by constant striving, when winning no longer brings joy, or when navigating uncertain life transitions where logic fails
Use when defining long-term product strategy, when needing to pivot from horizontal to vertical focus, or when teams struggle with prioritization due to serving too many use cases
Use when delivering difficult feedback (performance issues, firing, promotion denial), when managers avoid necessary conversations due to fear, or when needing structured scripts for high-stakes communication
Write a future-dated Press Release and FAQ before any coding begins to ensure the product solves a real customer problem. Work backwards from the customer, not forward from capabilities. Amazon's foundational p...
In scaling companies, once you master a role you must hand it off and move to a bigger, messier challenge. Holding on buries you; giving away allows you to tackle bigger challenges.
An organizational model where a single leader is fully accountable for a specific goal and controls all cross-functional resources needed, minimizing external dependencies. Amazon's alternative to matrixed orga...
A behavioral model defining the opposing forces in switching decisions—Push, Pull, Anxiety, Habit. Change happens only when (Push + Pull) > (Anxiety + Habit). Core to Jobs-to-be-Done theory.
Use during quarterly or annual roadmap planning, when Engineering wants tech debt work while PMs want features and Leadership wants moonshots, to force explicit resource allocation
Use when facing a significant decision (career pivot, product direction, technical choice) and feeling stuck or indecisive, when seeking contextual advice rather than generic recommendations
Use when AI agents frequently hit dead ends, when reliability is the main constraint on scaling utility, or when general model improvements don't solve specific blockers
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.