Individual skill
assess-problem-wickedness
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.
skills/assess-problem-wickedness/SKILL.md
Source commit 41f752b8444ed9030dd9dc223c302ce874e51f83
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 10, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 511
- Repository last updated
- Oct 23, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-research Repository topic
- deep-research Repository topic
- literature-review Repository topic
- mcp Repository topic
- skill Repository topic
- ai-scientist Repository topic
- auto-research Repository topic
- claude-code Repository topic
- research-agent Repository topic
- scientific-discovery Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,406 bytes
Read excerpt
# 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
```yaml
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.