defining-and-exploring-problems

defining-and-exploring-problems is a skill for Claude Code from fatihguner/foreman. It costs 124 tokens per session (4,404 once invoked), scanned A, original, MIT.

A guide to defining problems before choosing solutions. It covers root causes, premortems, follow-on effects, false either-or choices, combined options, and opportunity cost.

In plain words
What is it for?
Use it to frame business or project problems, explore possible approaches, anticipate failures, and compare what each choice gives up.
Why use it?
It reduces the risk of spending time solving the wrong problem or accepting the first proposed solution without examining alternatives.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the foreman plugin — 142 skills, 60 commands, 7 agents shipped together

Good fit Use it to frame business or project problems, explore possible approaches, anticipate failures, and compare what each choice gives up.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fatihguner/foreman/defining-and-exploring-problems
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 fatihguner/foreman --skill defining-and-exploring-problems
Clone the repo
git clone --depth 1 https://github.com/fatihguner/foreman

Made for: Claude Code.

Or install foreman, the plugin that ships this one along with the rest of its 142 skills, 60 commands, 7 agents.

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 defining-and-exploring-problems

README.md
[![agentmods](https://agentmods.dev/badge/skills/fatihguner/foreman/defining-and-exploring-problems.svg)](https://agentmods.dev/skills/fatihguner/foreman/defining-and-exploring-problems)
Your own site
<a href="https://agentmods.dev/skills/fatihguner/foreman/defining-and-exploring-problems"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/defining-and-exploring-problems.svg" alt="Measured on agentmods" height="20"></a>
Per session 124 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,404 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00124 $0.04404
Opus 5 $0.00062 $0.02202
Sonnet 5 $0.00025 $0.00881
Haiku 4.5 $0.00012 $0.00440

Measured yesterday against content hash 398bdb4b3521, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

defining-and-exploring-problems 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 yesterday.

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.

plugins/foreman/skills/defining-and-exploring-problems/SKILL.md · 206 lines

How it starts

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

Read runtime and advisory rules before applying this skill. Other Foreman layers and the catalog are in ../../content/, relative to this SKILL.md.

Defining and Exploring Problems

WRONG PROBLEM. Most failed decisions do not come from wrong answers -- they come from wrong questions. A room of intelligent people converges on a plausible-sounding problem statement within minutes, pivots immediately to solutions, and spends weeks executing against a target that was never the right one. The Clear Thinking framework calls this the social default: the collective instinct to accept the first definition everyone agrees on and move forward, because solving problems feels productive while defining them feels like stalling. The result is organisations that are perpetually busy and perpetually unimproved -- extinguishing flames that reignite because no one addressed the fire. Define the problem correctly and the solution often becomes obvious. Define it incorrectly and no amount of analytical sophistication will rescue the outcome.


The Framework

The process divides into two distinct phases -- defining the real problem, then exploring the full solution space -- and the single most valuable discipline is keeping them apart.

Phase 1: Define the Problem

The Definition Principle. Take responsibility for defining the problem yourself. Do not let someone else's framing become your framing by default. If you cannot explain the problem to a twelve-year-old without resorting to jargon, you do not yet understand it well enough to make a decision about it.

The Root Cause Principle. Distinguish the disease from the symptoms. The diagnostic question is deceptively simple: "What would have to be true for this problem not to exist in the first place?"

The text illustrates this with Downtown Dog Rescue in Los Angeles, where founder Lori Weise discovered that 30 percent of shelter dogs were owner surrenders -- families who loved their pets but could not afford to feed them. The obvious problem ("how do we get more people to adopt?") was the wrong problem. The root cause was economic hardship among existing owners. Solving for that reduced shelter intake by 75 percent at lower cost than housing the animals.

Read the full file on GitHub · 206 lines

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. yesterday First seen · 206 lines · 124 tokens per session scan A 398bdb4b3521

Subscribe to this mod's changes

defining-and-exploring-problems is a skill published in the GitHub repository fatihguner/foreman (47 stars, last pushed 2d ago), licensed MIT. It adds 124 tokens to every session and 4,404 once invoked, about $0.0006 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-09-06.

Related

Other skills, from other repositories

s4h-cognition-metacognition

Applies thinking-about-thinking as a practical tool — monitoring comprehension, calibrating confidence, and knowing what you do not know. Use when asked 'how confident should I be about this', 'am I actually understanding this or just recognising it', 'what do I not know that I should know', 'I think I understand this…

human-avatar/skills-for-humanity · 105 tokens

s4h-economics-coordination

Diagnoses collective action failures, public goods problems, and why individually rational behaviour produces collective irrationality. Triggers: 'collective action problem', 'tragedy of the commons', 'free rider', 'everyone is acting in their own interest but the result is bad for all', 'why won't people contribute'…

human-avatar/skills-for-humanity · 99 tokens

s4h-mindset-growth

Applies Carol Dweck's growth mindset research as a practical methodology — the actual mechanics, not the motivational poster version. Use when you're treating failure as evidence about your identity, avoiding challenges because of what failure would mean, comparing yourself to others in a way that deflates rather than…

human-avatar/skills-for-humanity · 128 tokens

s4h-mindset-positive

Applies positive psychology as a rigorous practice — not pop-psychology positivity. Use when you want to build flourishing, diagnose what dimension of wellbeing is underdeveloped, understand what makes life feel meaningful or hollow, or identify why you're not thriving despite the absence of obvious problems.…

human-avatar/skills-for-humanity · 117 tokens

s4h-mindset-reframe

Applies cognitive reframing as a rigorous methodology — CBT-adjacent but not therapy. Use when you're stuck in a negative thought loop, interpreting a situation in a consistently unhelpful way, catastrophizing, or noticing that your automatic interpretation of events generates disproportionate distress. Triggers…

human-avatar/skills-for-humanity · 122 tokens

s4h-historical-lesson-extraction

Extracts the transferable principle from a specific historical case — separating the contingent surface details from the underlying rule that applies across contexts. TRIGGERS: 'what's the lesson', 'extract the lesson', 'what should we learn from this', 'generalise from this case', 'apply this to our situation'.

human-avatar/skills-for-humanity · 73 tokens