problem-definition

problem-definition is a skill for Claude Code, Codex from cnfeat/top-pm-skills. It costs 49 tokens per session (1,000 once invoked), scanned A, original, MIT.

A skill for clarifying the real problem before choosing a feature or solution. It uses product-planning questions and frameworks to examine the user's situation, need, and priorities.

In plain words
What is it for?
Use it when scoping a feature, testing a product idea, describing where users get stuck, or deciding whether a proposed solution matters.
Why use it?
It helps prevent building an attractive solution to the wrong problem or rushing into technology before the need is clear.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when scoping a feature, testing a product idea, describing where users get stuck, or deciding whether a proposed solution matters.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cnfeat/top-pm-skills/problem-definition
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add cnfeat/top-pm-skills --skill problem-definition
Clone the repo
git clone --depth 1 https://github.com/cnfeat/top-pm-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for problem-definition

README.md
[![agentmods](https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/problem-definition.svg)](https://agentmods.dev/skills/cnfeat/top-pm-skills/problem-definition)
Your own site
<a href="https://agentmods.dev/skills/cnfeat/top-pm-skills/problem-definition"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/problem-definition.svg" alt="Measured on agentmods" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,000 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.01000
Opus 5 $0.00024 $0.00500
Sonnet 5 $0.00010 $0.00200
Haiku 4.5 $0.00005 $0.00100

Measured 8d ago against content hash a3fce7a3a085, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

problem-definition scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

参考skill/lenny-skills-main (2)/lenny-skills-main/skills/problem-definition/SKILL.md · 72 lines

How it starts

The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Problem Definition

Help the user define problems clearly before jumping to solutions using frameworks from 91 product leaders.

How to Help

When the user asks for help with problem definition:

  1. Understand the current framing - Ask how they're currently thinking about the problem
  2. Dig into the struggling moment - Help them articulate the specific context where users feel stuck
  3. Separate problem from solution - Ensure they haven't conflated a desired feature with the underlying need
  4. Validate the problem matters - Help them confirm the problem is urgent and widespread enough to solve

Core Principles

Digitizing analog isn't enough

Bret Taylor: "Why use this instead of the Yellow Pages? It was a digital version of something that had come before." Simply digitizing an analog predecessor often fails because it lacks a native reason to exist on the new platform. Ask "why should a customer give this the time of day?"

Prototype to define the problem

Jake Knapp + John Zeratsky: "This idea of getting unstuck and turning maybe some abstract ideas or some concepts that you've been discussing, turning that into a concrete prototype, something that you can look at and you can click around." Moving from abstract concepts to concrete prototypes is the fastest way to define and solve a problem.

Avoid the shiny object trap

Marily Nika: "There is something called the shiny object trap, and I'm always telling people, 'Hey, don't do AI for the sake of doing AI.' Make sure there is a problem there." Ensure AI (or any new technology) is used to solve a specific, validated user pain point rather than for its own sake.

Struggling moments cause demand

Bob Moesta: "A struggling moment causes demand. And you start to realize that in some cases that struggling moment exists and can exist for a long time and nobody solved it." Demand is created by a specific "struggling moment" in a user's life, not by the product itself. Study the context that makes users' behavior rational.

Read the full file on GitHub · 72 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 72 lines · 49 tokens per session scan A a3fce7a3a085

Subscribe to this mod's changes

problem-definition is a skill published in the GitHub repository cnfeat/top-pm-skills (48 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 1,000 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens