smithery/coowoolf

LNO Time Management Framework

Categorize tasks into Leverage (10x), Neutral (1x), and Overhead (<1x) to escape the trap of treating all tasks as equally important. Apply perfectionism only to L tasks.

Installation

$ npx skills add smithery/coowoolf --skill lno-time-management-framework

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/coowoolf · top by installs.

npx skills add smithery/coowoolf

Browse all from smithery/coowoolf

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,502 B
  • docs SUMMARY.md 207 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

The LNO Framework

"The mistake is that we treat all tasks as created equal. They are not." — Shreyas Doshi

What It Is

Categorize tasks into Leverage (L), Neutral (N), and Overhead (O). Strive for perfection only on L tasks (10x-100x impact). For N and O tasks, "good enough" is the goal.

When To Use

  • Daily prioritization decisions
  • When feeling overwhelmed by to-do lists
  • To escape the trap of treating all tasks as equally important
  • When you notice perfectionism is burning time on low-value work

Core Principles

Task Classification Matrix

Type Impact Approach Examples
L (Leverage) 10x-100x Apply perfectionism Strategy docs, key PRDs, hiring decisions
N (Neutral) 1x Good enough Standard code reviews, routine meetings
O (Overhead) <1x Minimum viable Expense reports, calendar scheduling

Key Insights

  1. Identify L Tasks — These are high leverage with 10x impact. Apply all your perfectionism here.
  1. Speed Through N/O Tasks — Neutral and Overhead tasks (1x or <1x impact) should be done strictly "good enough" or delegated.
  1. Placebo Productivity — Use N/O tasks to build momentum before tackling a scary L task.

How To Apply

STEP 1: List Today's Tasks

STEP 2: Tag Each Task
└── L = Will this 10x something important?
└── N = Needs to be done, but standard work
└── O = Administrative / no direct impact

STEP 3: Allocate Time
└── L tasks: Block 2-3 hours of deep work
└── N tasks: Batch into 30-min windows
└── O tasks: Automate, delegate, or do in 5 min

STEP 4: Resist Perfectionism on N/O
└── Set timer limits
└── "What's the minimum acceptable here?"

Common Mistakes

❌ Applying perfectionism to O tasks (spending hours on expense reports)

❌ Defaulting to N/O tasks because they feel productive and safe

❌ Not recognizing that the same task type can shift categories based on context

Real-World Example

Writing a bug report can be an L task (if it's a critical, complex failure) or an O task (standard minor bug), and should be treated differently.


Source: Shreyas Doshi, Lenny's Podcast