agentleFS
qingxuantangqingxuantang/Lennys-to-sop-and-skills/skills/goal-setter/SKILL.md

goal-setter

Skill16 starsChanged 10 months agoMITView on GitHub

Helps set effective goals, prioritize work, and manage time. Use when: setting OKRs or goals, quarterly planning, prioritizing work, managing time, or diagnosing why goals aren't being met. Includes: NCT Framework, GEM Prioritization, LNO Time Management frameworks. Sources: Ravi Mehta, Gibson Biddle, Shreyas Doshi.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. yunshu0909/yunshu_skillshub★ 760same name
    2. computerphilosopher/agent-skills★ 4same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No understanding of why things work

    line 45
  2. Distinctive:

    Ask these questions in order.

    line 98
  3. Distinctive:

    Always setting outcome goals (regardless of understanding)

    line 133
  4. Distinctive:

    Not progressing the frontier (stuck at "learning")

    line 134
  5. Distinctive:

    Not communicating frontier position to leadership

    line 136
  6. Distinctive:

    Must be done but doesn't need excellence

    line 223
  7. Distinctive:

    Do tasks they should delegate

    line 239
  8. Distinctive:

    Not protecting Lead task time

    line 288
  9. Distinctive:

    Not actually offloading Offload tasks

    line 290
  10. Distinctive:

    NCT + GEM: Use NCT to set appropriate goal type, then use GEM to prioritize initiatives toward that goal.

    line 312
  11. Distinctive:

    GEM + LNO: Use GEM to prioritize product work, use LNO to protect time for high-GEM initiatives.

    line 314

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Goal Setter Skill

Help users set effective goals and prioritize their work.

When This Skill Activates

  • "Help me set goals"
  • "OKR planning"
  • "How do I prioritize?"
  • "We keep missing our goals"
  • "Quarterly planning"
  • "Time management"
  • "What should I focus on?"

Framework Selection Guide

SituationUse This Framework
Setting quarterly/annual goalsNCT Framework
Prioritizing product initiativesGEM Framework
Managing personal timeLNO Framework

Framework 1: NCT Goal Setting (Frontier of Understanding)

Source: Ravi Mehta - Lenny's Podcast Key Insight: Your goal type should match your "frontier of understanding"—where your knowledge ends and uncertainty begins.

The Problem with Always-Outcome Goals

Standard: "Improve retention by 10%"

What happens:

  • Team brainstorms experiments
  • Throws spaghetti at wall
  • No understanding of why things work
  • Can't repeat success

Better: Match goal type to what you actually know.

The Four Risk Types

1. Understanding Risk You don't know what moves the metric.

Signs:

  • "We can brainstorm 10 experiments"
  • "We don't know why people retain"

Right goal: Learning goal

  • "Identify top 3 retention drivers"
  • "Form validated hypothesis"

2. Dependency Risk You have hypothesis but lack tools/resources.

Signs:

  • "We think X affects retention"
  • "But we can't measure X"

Right goal: Capability goal

  • "Build retention tracking dashboard"
  • "Implement event tracking"

3. Execution Risk You have hypothesis and tools, but haven't proven execution.

Signs:

  • "We know what to build"
  • "We haven't shipped this type of thing before"

Right goal: Output goal

  • "Run 20 experiments this quarter"
  • "Ship three retention features"

4. Strategic Risk You have everything but hypothesis might be wrong.

Signs:

  • "We believe X drives retention"
  • "We can execute on X"
  • "But haven't proven X → retention"

Right goal: Outcome goal

  • "Improve retention 10%"

Finding Your Frontier

Ask these questions in order. Stop at first "No":

QuestionIf No →
Do we know what levers affect this?Understanding risk
Do we have tools to act on levers?Dependency risk
Can we execute experiments/features?Execution risk
Is our hypothesis likely correct?Strategic risk

Goal Progression

Typical quarterly progression:

  • Q1: Understanding goal → Learn levers
  • Q2: Dependency goal → Build tools
  • Q3: Execution goal → Prove capability
  • Q4: Outcome goal → Drive results

Key: This isn't slower—it's more reliable.

The 2x2 for Reflection

Know WhyDon't Know Why
Hit GoalIdeal ✓Lucky (temporary)
Missed GoalLearningLost

Goal: Upper-left (hit AND know why) Warning: Upper-right (hit but don't know why = can't repeat)

Communicating Frontier Position

Template:

"We want to improve [metric]. Currently, we're at [frontier position]. Our goal this quarter is [appropriate goal], which moves us toward outcome goals next quarter."

Pitfalls to Avoid

  • Always setting outcome goals (regardless of understanding)
  • Not progressing the frontier (stuck at "learning")
  • Hiding behind uncertainty (not pushing toward outcomes)
  • Not communicating frontier position to leadership

Framework 2: GEM Prioritization

Source: Gibson Biddle - Lenny's Podcast Key Insight: Score initiatives on Growth, Engagement, and Monetization to prioritize objectively.

The GEM Dimensions

G - Growth Does this help acquire new users?

  • New user sign-ups
  • Activation rate
  • Expansion into new segments

E - Engagement Does this increase usage/retention?

  • DAU/MAU
  • Session frequency
  • Feature adoption
  • Retention curves

M - Monetization Does this improve revenue/economics?

  • Conversion rate
  • ARPU
  • LTV
  • Margin

Scoring System

Rate each initiative 0-10 on G, E, M:

InitiativeGrowthEngagementMonetizationTotal
Feature A78318
Feature B29617
Feature C84820

Weighting by Company Stage

StageGrowthEngagementMonetization
Early50%40%10%
Growth30%40%30%
Mature20%30%50%

Using GEM for Trade-offs

When debating priorities:

  1. Score each option on G, E, M
  2. Apply stage-appropriate weights
  3. Compare totals
  4. Discuss surprising scores

Beyond Total Score

Also consider:

  • Strategic alignment (does it fit vision?)
  • Effort required (ROI, not just return)
  • Dependencies and sequencing
  • Learning value

Pitfalls to Avoid

  • Ignoring one dimension entirely
  • Wrong weights for company stage
  • Not considering effort
  • Using scores to avoid hard conversations

Framework 3: LNO Time Management

Source: Shreyas Doshi - Lenny's Podcast Key Insight: Categorize tasks as Lead, Neutral, or Offload—then invest time accordingly.

The Three Categories

L - Lead Tasks (Do Excellently)

  • Highest leverage activities
  • Require your unique skills
  • Failure here = major impact
  • Examples: Key presentations, critical decisions, strategy work

N - Neutral Tasks (Do Adequately)

  • Must be done but doesn't need excellence
  • Good enough is good enough
  • Diminishing returns on extra effort
  • Examples: Routine meetings, standard processes

O - Offload Tasks (Delegate/Eliminate)

  • Someone else can do it
  • Doesn't need to be done at all
  • Low leverage use of your time
  • Examples: Scheduling, routine reports, tasks others can own

The Key Insight

Most PMs treat everything as Lead tasks:

  • Spend hours perfecting routine documents
  • Over-prepare for low-stakes meetings
  • Do tasks they should delegate

Result: No time/energy for actual Lead tasks

Applying LNO

Step 1: List Your Tasks Everything on your plate this week

Step 2: Categorize Each

TaskCategoryWhy
Board deckLHigh visibility, critical narrative
Weekly syncNRoutine, adequate is fine
Expense reportsOSomeone else can do

Step 3: Invest Time Accordingly

  • L tasks: Give them your best hours, full attention
  • N tasks: Time-box, don't over-engineer
  • O tasks: Delegate, automate, or eliminate

Step 4: Protect Lead Task Time

  • Schedule L tasks during peak energy
  • Batch N tasks together
  • Systematically offload O tasks

Common L/N/O Splits

Healthy PM week:

  • Lead: 30-40%
  • Neutral: 40-50%
  • Offload: 10-20%

Unhealthy PM week:

  • Lead: 10%
  • Neutral: 70%
  • Offload: 20% (but you're doing them)

Identifying Lead Tasks

Ask:

  • What would have outsized impact if done excellently?
  • What requires my unique perspective/skills?
  • What, if done poorly, would cause significant problems?
  • What advances my highest priorities?

Pitfalls to Avoid

  • Treating everything as Lead
  • Offload guilt (it's not laziness, it's leverage)
  • Not protecting Lead task time
  • Doing Neutral tasks at Lead quality
  • Not actually offloading Offload tasks

How to Apply This Skill

  1. Identify the goal-setting challenge
    • Setting goals → NCT Framework (match goal to understanding)
    • Prioritizing initiatives → GEM (score systematically)
    • Managing time → LNO (categorize and invest accordingly)
  2. Walk through the relevant framework with specific examples
  3. Help create concrete output
    • NCT: Identify frontier, set appropriate goal type
    • GEM: Score current options, identify winner
    • LNO: Categorize this week's tasks, create plan
  4. Follow up on progress

Combining Frameworks

NCT + GEM: Use NCT to set appropriate goal type, then use GEM to prioritize initiatives toward that goal.

GEM + LNO: Use GEM to prioritize product work, use LNO to protect time for high-GEM initiatives.

Related Skills

  • /strategy-advisor - For strategic direction setting
  • /decision-maker - For specific prioritization decisions
  • /pm-coach - For time management skill development

Full SOPs (Deep Dives)

Goal Setting

  • NCT Goal Setting
  • OKR Setting Framework
  • OKR Cadence Rituals
  • OKR Pitfalls Diagnosis
  • Mission-Strategy OKR Alignment
  • GENIE Career Goal Setting

Prioritization

  • GEM Prioritization
  • LNO Time Management
  • Opportunity Cost Mindset
  • Pre-Mortem Technique
  • Decision Prioritization
  • Three Levels of Work

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.