skills.rest
menkesu
menkesuCOMMUNITY
Explore all skills by this author →
GitHub

strategic-build

Classify product work as Leverage, Neutral, or Overhead using the LNO framework.

389|121|Updated Jan 28, 2026
Search Tags:#product-strategy#pre-mortem#decision-frameworks#lno#empowered-teams#strategic-pm#level-1-3
One-click install
npx skills add https://github.com/menkesu/awesome-pm-skills --skill strategic-build
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: strategic-build
Source: https://github.com/menkesu/awesome-pm-skills/tree/main/strategic-build
Command: npx skills add https://github.com/menkesu/awesome-pm-skills --skill strategic-build

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Distinguishes strategic vs tactical work during development using Shreyas Doshi's frameworks and Marty Cagan's empowered teams principles. Use when making architectural decisions, choosing what to build, preventing "product theater", or applying the LNO framework (Leverage, Neutral, Overhead). Helps avoid feature factory and build work that compounds.

Core Features & Use Cases

  • LNO framework for prioritization: Leverage, Neutral, Overhead with guidance on how to classify work.
  • Three Levels of Product Work: Impact, Execution, optics to ensure you're solving the right problem.
  • Pre-Mortems for strategic decisions to surface risks before building.
  • Empowered vs Feature teams guidance to shift from build-first to outcome-focused delivery.
  • Decision Tree and actionable templates to operationalize strategic thinking.
  • Real-world guidance and examples.

Quick Start

Run an LNO assessment and Level 1–3 checks on your next feature request to determine whether to build and how to approach it.

Frequently Asked Questions about strategic-build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I classify product work as Leverage, Neutral, or Overhead?▼

The LNO framework distinguishes strategic Leverage work that compounds from Neutral execution and necessary Overhead, providing decision criteria and templates to classify tasks by impact, execution, and optics to ensure outcomes-based product management.

What is the difference between empowered teams and feature teams in product strategy?▼

Empowered teams focus on solving customer problems to achieve outcomes, whereas feature teams follow a build-first delivery model, and shifting to empowered teams requires applying strategic product management frameworks to avoid product theater and tactical busy work.

How do I run a pre-mortem for architectural decisions and product roadmaps?▼

Running a strategic pre-mortem involves evaluating architectural decisions and roadmaps against specific risk criteria to surface potential failures before building, using provided decision trees and actionable templates to operationalize strategic thinking and prevent product theater.

What are the three levels of product work for evaluating impact and execution?▼

The three levels of product work are Impact, Execution, and Optics, which provide actionable checks to ensure you are solving the right problem and avoiding strategic missteps when choosing what to build during product development.

When should I use decision frameworks to evaluate a new feature request?▼

You should use decision frameworks to evaluate a new feature request when you need to determine whether to build it and how to approach it, running an LNO assessment and Level 1-3 checks to avoid the feature factory trap and ensure real impact.

Related Skills

Explore More Product & Management Skills→
danfrdndanfrdn

strategic-build

Classifies development tasks as Leverage, Neutral, or Overhead using Shreyas Doshi's LNO framework.

Community
Intermediate
Maitreya04Maitreya04

inspired-product

Organizes empowered product teams around discovery, OKRs, and outcome-based roadmaps.

Community
Advanced
skycruzerskycruzer

Roadmap Builder

Prioritize product roadmap features using an Impact vs Effort matrix.

Community
Basic
nicepkgnicepkg
276

roadmap-prioritization-planning

Prioritize product backlogs with RICE, MoSCoW, and Kano frameworks.

Official
Advanced