agentleFS
afeezadebayoafeezadebayo/thinking-decisions-skills/problem-framing/SKILL.md

problem-framing

Skill0 starsChanged 10 days agoLicence not identifiedView on GitHub

Defines the right problem before anyone solves it. Takes a problem someone has stated (a brief, a goal, a complaint, a 'why is X happening' question, a request to fix or improve something) and tests whether it is framed well, then produces two to four candidate frames, a chosen problem statement and success criteria. Surfaces the stated frame, gathers short written definitions from several people, asks what the description leaves out, checks the objective, analyses cases where the problem did not occur, and treats problems as multicausal rather than finding one root cause. Use whenever someone asks to frame or reframe a problem, write a problem statement, scope a project, run a root-cause or 5 Whys session, work out the real problem, or says a solution is not working and they do not know why. Do NOT use for choosing between options already defined (use decision-frameworks), stress-testing a chosen plan (use premortems), ranking a backlog (use prioritisation) or running desk research (use research-planning).

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

18 rules. 0 are common, 17 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 17

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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.