The problems axis of the broad pass — sweep a domain wide for the problems people voice, each in the speakers' own words with where it was voiced, one line per entry. TRIGGER when a thread needs the domain's voiced problems enumerated before any one is mined. DO NOT TRIGGER to mine one group's language deep (research-audience) or to find where a group talks (discover-audience).
Scanned 9/5/2026
Install to Claude Code
npx -y skills add heyJordanParker/dotfiles --skill discover-problems --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Discover Problems?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/heyjordanparker-discover-problems)More formats (shields.io, HTML) on the badges page.
---
name: discover-problems
description: The problems axis of the broad pass — sweep a domain wide for the problems people voice, each in the speakers' own words with where it was voiced, one line per entry. TRIGGER when a thread needs the domain's voiced problems enumerated before any one is mined. DO NOT TRIGGER to mine one group's language deep (research-audience) or to find where a group talks (discover-audience).
---
# Discover Problems
Run /discover; this adds only the problems axis. /discover owns the sweep, the page gate, the fetched-page-only content law, and the write to `research/<subject>/discovery/` — hold to it and add only what follows.
Inputs: the one domain, named by its question, from the research `Brief.md` — nothing else. Excluded: owner facts, product facts, any persona or target buyer, and any solution shape — the problems are what the sweep finds, never a guess confirmed. A product shape handed in biases the sweep toward solution-shaped problems.
## The entry is a voiced problem
Sweep the domain for the problems people state in the open, and enumerate them long — one line per problem: the problem in the speaker's own words, the speaker as shown on the page, where it was voiced (the URL), and the page's date where shown. "We were drowning in spreadsheets" is the entry; "manual-process inefficiency" destroys it. Reach for breadth — many voiced problems with a line each, never a few studied deep; the deep mine is research-audience's, afterward.
### A problem is a problem regardless of who voices it or how many
Enumerate every voiced problem the domain holds. One person voicing it once is an entry, the same as one voiced a thousand times — frequency is the judged-files step's to weigh, never a filter here. Dropping a problem because it seems rare is a judgment you do not make.
### Never convert a complaint into a market
A voiced complaint is a record that one speaker said it, never proof of a buyer, a segment, or a demand. Enumerate the complaint in the speaker's words; never label it a market, size it, or pair it with who would pay. Whether it is a real market is settled later, by the judged-files step, from these entries.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!