Product management
Skill yigityildiz0/universal-ai-skill-library/skills/common/product-management
531 searchable AI Agent Skills for Claude Code, OpenAI Codex, and OpenCode — EN/TR catalog, platform and risk notes, direct ZIPs, and curated bundles.
npx -y skills add yigityildiz0/universal-ai-skill-library --skill product-managementAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 19 days oldThe repository was created 19 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Route product strategy and delivery work to focused workflows for product framing, discovery, competition, metrics, sprint planning, stakeholder communication, and telemetry. Use when a task concerns user problems, scope, prioritization, launch, outcomes, or product decisions.
SKILL.md
1.1 KB, 166 tokens by cl100k_base, as published. Nobody here has run it
Product Management
Clarify the user, problem, metric, decision, owner, and time horizon before selecting a workflow:
product-managerfor prioritization, scope, roadmap, requirements, and tradeoffs;competitive-brieffor source-backed market/competitor comparison;product-metrics-reviewfor metric movement and decision implications;sprint-planningfor a short delivery cycle and capacity-aware scope;stakeholder-updatefor status, asks, and evidence;research-synthesisanduser-researchfor discovery evidence;product-tracking-*for telemetry design and implementation.
Keep strategy distinct from feature lists. Do not treat a roadmap, metric, or research finding as a decision without assumptions, tradeoffs, and a validation path.