problem-handling
Skill1 starsChanged 41 days agoNo licenceView on GitHub
Problem handling: one evidence-driven pipeline from a reported symptom to a shipped fix — evidence-first intake, root-cause tracing (5 Whys plus RCA tools, falsifiable experiments), cognitive-bias defenses, dual-channel research, severity grading with a P0/P1 restore-first fast path, classify and scope, workaround-vs-permanent-fix decision, TDD fix, verification, and a blameless close with known-error capture plus a 3-strikes design escalation. Use when a problem, bug, error, UX complaint, or behavior gap is reported, before jumping to a fix. NOT for: a pure code bug whose root cause is all you need — reproduce, isolate, fix; designing the standing configuration of a system that repeatedly calls an external service (provider choice, routing order, quota and budget, the provider-shaped failure classes) — that is configuration work, not incident triage. No skill name implied: the boundary is the task.
In this repository93 other files it gives its agents.
- accessibility-auditorSkill
- agent-dispatchSkill
- api-contract-validatorSkill
- architecture-patternsSkill
- audit-itemSkill
- autonomous-investigationSkill
- battle-card-builderSkill
- cicd-pipelineSkill
- codebase-designSkill
- code-reviewSkill
- company-intelSkill
- competitive-analysis-processSkill
- competitive-intel-watchSkill
- competitive-research-snapshotSkill
- config-scanSkill
- core-rulesSkill
- coverage-matrixSkill
- customer-journey-mapSkill
- ddd-aggregatesSkill
- ddd-context-mapSkill
- ddd-contextsSkill
- ddd-discoverSkill
- ddd-domain-interactionsSkill
- ddd-model-reviewSkill
- ddd-openspec-bridgeSkill
- ddd-qa-chainSkill
- ddd-scopeSkill
- ddd-subdomainsSkill
- ddd-tactical-reviewSkill
- decision-logSkill
- deep-codebase-analysisSkill
- delegated-researchSkill
- dependency-scanSkill
- discovery-interview-prepSkill
- electron-best-practicesSkill
- env-checkSkill
- event-stormingSkill
- executing-plansSkill
- experiment-handoffSkill
- frontend-designSkill
- git-workflowSkill
- grill-meSkill
- intelligence-collection-disciplinesSkill
- jobs-to-be-doneSkill
- k6-performanceSkill
- llm-gateway-opsSkill
- marketing-copywritingSkill
- market-landscape-scanSkill
- perf-checkSkill
- pipeline-0to1Skill
- pixel-perfectSkill
- plan-grillingSkill
- playwright-best-practicesSkill
- positioning-statementSkill
- positioning-workshopSkill
- prd-developmentSkill
- prd-driven-dddSkill
- press-releaseSkill
- problem-statementSkill
- product-doc-auditSkill
- The first 60 shown.
The file
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.