agentleFS
Sign inStart free
yogsoth-aiyogsoth-ai/de-anthropocentric-research-engine/skills/assess-problem-wickedness/SKILL.md

assess-problem-wickedness

Skill505 starsChanged 49 days agoApache-2.0View on GitHub

Assess whether the problem is tame, complex, or wicked by examining stakeholder disagreement, moving boundaries, feedback, value conflict, and absence of a stable stopping rule.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Check boundary movement, feedback loops, and value conflicts.

    line 17
  2. Distinctive:

    Do not label a problem wicked solely because it is difficult or interdisciplinary.

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

assess-problem-wickedness

Purpose

Assess whether a problem is tame, complex, or wicked using disagreement, moving boundaries, feedback, value conflict, and stopping-rule evidence.

Input contract

required: [problem_statement, stakeholder_views]
optional: [boundary_history, feedback_observations, candidate_stopping_rule]
constraints: [classification must cite observed disagreement or stability indicators]

Procedure

  1. Compare stakeholder definitions and desired outcomes.
  2. Check boundary movement, feedback loops, and value conflicts.
  3. Assess whether a stable stopping rule and agreed solution test exist.
  4. Assign tame, complex, or wicked with evidence and uncertainty.

Output contract

produces: [wickedness_assessment, evidence_basis, workflow_implications]
delta_fields: [findings, uncertainties, decisions, open_questions]

Quality gates

  • Classification covers all five dimensions; disagreement is distinguished from missing information.

Failure and counterexamples

Do not label a problem wicked solely because it is difficult or interdisciplinary.

Provenance map

  • deep-insight/wickedness-assessment: resolved.

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.

Check your setup, free