problem-definition
Skill1 starsChanged 22 days agoMITView on GitHub
Frames an engagement problem when the initial request is vague, contested or prematurely solution-led.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- alexandrosandre/agentic-engineeringtheir own version, first seen Nov 8, 2026
- CodeAlive-AI/ceo-ai-ostheir own version, first seen May 18, 2026
- Layneformalized225/ai-cofoundertheir own version, first seen Mar 22, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- CodeAlive-AI/ceo-ai-os★ 9same name
- Layneformalized225/ai-cofounder★ 1same name
- alexandrosandre/agentic-engineering★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository133 other files it gives its agents.
- templates/CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- access-control-auditSkill
- ai-opportunity-scanSkill
- ai-policy-writerSkill
- annual-budget-builderSkill
- application-portfolio-mapSkill
- architecture-fit-checkSkill
- automation-backlogSkill
- benefits-realisationSkill
- board-paperSkill
- bottleneck-removalSkill
- break-even-modelSkill
- budget-variance-analystSkill
- business-continuity-plannerSkill
- business-valuationSkill
- capacity-planningSkill
- case-study-writerSkill
- cash-flow-forecastSkill
- change-adoptionSkill
- change-impactSkill
- channel-profitabilitySkill
- churn-cohort-analysisSkill
- client-handoverSkill
- client-kickoffSkill
- client-profitabilitySkill
- client-relationship-managerSkill
- closeout-packSkill
- compensation-bandsSkill
- competitor-mapperSkill
- contribution-marginSkill
- cost-structure-analystSkill
- crisis-communicationsSkill
- customer-insight-synthesiserSkill
- customer-interview-designerSkill
- customer-journey-mapSkill
- customer-segmenterSkill
- cyber-risk-assessmentSkill
- dashboard-requirements-plannerSkill
- data-lineage-mapperSkill
- data-quality-auditSkill
- decision-logSkill
- decision-memoSkill
- decision-rightsSkill
- delivery-model-selectorSkill
- demand-validatorSkill
- discount-governanceSkill
- discovery-call-facilitationSkill
- discovery-call-prepSkill
- discovery-question-designSkill
- discovery-synthesisSkill
- engagement-outcomesSkill
- evidence-synthesiserSkill
- executive-dashboardSkill
- executive-summarySkill
- fee-settingSkill
- financial-statement-diagnosticSkill
- fundraising-readinessSkill
- funnel-diagnosticSkill
- go-to-marketSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
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
- Distinctive: line 9
Use between discovery and scoping to establish a shared, evidence-based problem statement.
- Distinctive: line 21
Test materiality, urgency, ownership and whether action is feasible.
- Distinctive: line 23
Write a neutral problem statement plus falsifiable assumptions.
“Common” is measured: kept by at least 6 in 10 of the 3 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.
Files
Problem Definition
When to use it
Use between discovery and scoping to establish a shared, evidence-based problem statement.
What Claude needs
client-context.mdfor business background- Discovery synthesis and stakeholder views
- Available baseline evidence
- Constraints, exclusions and decision deadline
Method
- Describe the current state, affected group and observable consequence.
- Separate symptoms, likely causes and proposed solutions using a simple issue tree.
- Bound the problem by process, population, location and time horizon.
- Test materiality, urgency, ownership and whether action is feasible.
- Reconcile competing stakeholder framings and record unresolved differences.
- Write a neutral problem statement plus falsifiable assumptions.
Output format
Provide a problem statement, issue tree, boundary table, assumptions, evidence gaps and stakeholder differences.
Quality checks
- Avoids embedding a preferred solution in the problem
- Makes boundaries and affected groups explicit
- Links claimed consequences to available evidence
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
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.