idea
Skill0 starsChanged 2 months agoMITView on GitHub
Turn a hunch, or a list of twenty hunches, into one business idea written in a sentence a stranger understands. Use when someone says they want to start something but cannot yet say what it is, when they have too many ideas to choose between, or when their description of the idea takes more than a minute.
27 other projects use a version of this.
Adopted by
Most recently taken up by
- Acnologia7021/codex-skillstheir own version, first seen Nov 4, 2026
- bas1l/claude-skillstheir own version, first seen Nov 3, 2026
- matiinchauspe/arsenaltheir own version, first seen Nov 1, 2026
- jayden-dang/skillstheir own version, first seen Nov 1, 2026
- szweibel/claude-skillstheir own version, first seen Nov 1, 2026
- 0xUrsanomics/utopia-ostheir own version, first seen Nov 1, 2026
Used with
Projects with it also use weekly-retro, decompose and 7 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Joshua-PalamuttamSkillweekly-retro
End-of-week retrospective. Compares planned vs actual, updates calibration data, and surfaces estimation patterns. Run Friday afternoons.
Also in 3 projects that use this
matt-k-wongSkilldecompose
Learn to decompose complex problems before building real agents. Better answers today. Ready for orchestration tomorrow. Breaks messy tasks into clear DAG structures with explicit dependencies, parallel branches, and synthesis logic. Improves Claude outputs by enforcing topological order and catching contradictions. Teaches the mental model for LangGraph, CrewAI, n8n, and Sub-Agents. Type "decompose: [goal]" or "decompose preview: [goal]" to start. Zero experience required.
Also in 3 projects that use this
seongjaeryuSkillsave
Complete and save your current thinking to Bindly
Also in 3 projects that use this
AWSSkillretro
Conduct a retrospective on a coding session.
Also in 5 projects that use this
GoogleSkillto-issues
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.
Also in 3 projects that use this
GoogleSkillto-prd
Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Also in 3 projects that use this
Other versions27 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 27
- me2resh/apexyard★ 542same name
- serejaris/personal-corp-os★ 243same name
- serejaris/ris-claude-code★ 243same name
- tance-mang/chinese-webnovel-skills★ 97same name
- baekenough/oh-my-customcode★ 42same name
- iamneilroberts/claude-skills★ 26same name
- tercel/spec-forge★ 8same name
- froster02/mini-Brain_skills★ 4same name
- merchsage/workflow-skills★ 4same name
- 0xUrsanomics/utopia-os★ 2same name
17 more not listed
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.
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 11 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 22 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Ask, before anything else:
- Distinctive: line 21
No idea: Do not generate a list of trending businesses.
- Distinctive: line 36
Can you name a specific person who has this problem?: Not a demographic. A person you could describe, or ideally phone.
- Distinctive: line 42
Can you deliver a first version alone, in under a month?: If it needs a team, a licence, or a warehouse, note what it needs and how long it …
- Distinctive: line 44
Would you still find it interesting in two years?: Ask it seriously. Most small businesses fail by being abandoned, not by being beaten.
- Distinctive: line 62
Test it three ways and fix whatever fails:
- Distinctive: line 65
The so-what test: If the answer to "so what" is "it saves time", ask whose time and how much, and put that in the sentence.
- Distinctive: line 86
Do not generate a list of twenty ideas when they already have one.
- Distinctive: line 87
Do not validate the idea here.
- Distinctive: line 88
Do not let "everyone" be the customer, or "it depends" be the price.
- Distinctive: line 89
Do not be encouraging about an idea that failed three of the four criteria.
- Very specific: line 94
When the sentence holds, run validate.
“Common” is measured: kept by at least 6 in 10 of the 22 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
Idea
Your job is to get the person from "I want to start something" to one sentence that a stranger could repeat back correctly. Not a business plan. One sentence.
Most people arrive here with either nothing or too much. Both are fixable in a conversation, and neither is fixed by brainstorming more.
Start by finding out which problem you have
Ask, before anything else:
Do you have no idea, one idea you keep coming back to, or a list you cannot choose between?
No idea. Do not generate a list of trending businesses. Ask what they already know that most people do not — a job they have done, a hobby that took years, a process they have watched go wrong repeatedly. An idea that comes from somewhere survives longer than one that comes from a list. Get five candidates out of their own experience, then continue as if they had a list.
One idea. Skip to Write the sentence. Do not offer alternatives unless they ask. Someone who has come back to the same idea for two years does not want a menu.
A list. Go to Cut the list.
Cut the list
Score each idea out loud against these four, and say the score:
- Can you name a specific person who has this problem? Not a demographic. A person you could describe, or ideally phone. If they cannot, the idea is not ready — it is a category.
- Does that person already spend money on it? Badly, slowly, on a bad alternative — any spending counts. Zero existing spend means you would be creating a market, which is a different and much harder business.
- Can you deliver a first version alone, in under a month? If it needs a team, a licence, or a warehouse, note what it needs and how long it would take.
- Would you still find it interesting in two years? Ask it seriously. Most small businesses fail by being abandoned, not by being beaten.
Then say which one wins and why, in two sentences. Do not present a matrix and leave the choice to them — they came here because choosing is the hard part. If two tie, pick the one where they can name a real person, and say that is why.
Write the sentence
Draft it in this shape and then get it out of this shape:
I help [specific person] who [has this problem] by [doing this thing].
Then rewrite it as something a human would actually say. "I help overwhelmed freelance bookkeepers get their client onboarding down from three hours to twenty minutes" is a sentence. "I provide workflow optimisation solutions for financial professionals" is not a sentence, it is a hiding place.
Test it three ways and fix whatever fails:
- The stranger test. Could someone who has never heard of this repeat it back?
- The so-what test. If the answer to "so what" is "it saves time", ask whose time and how much, and put that in the sentence.
- The nobody test. Who is this explicitly not for? If the answer is "anyone could use it", the sentence is not finished.
What to hand back
A short file, idea.md:
- the sentence
- the specific person, described well enough to go looking for them
- what they do today instead
- what has to be true for this to work, listed as things that could be checked
- what you would need to see to abandon it
That last one matters and people skip it. Ask for it directly: what would have to happen in the next three months for you to say this was not it? Write down the answer while they can still say it honestly.
Do not
- Do not generate a list of twenty ideas when they already have one.
- Do not validate the idea here. That is the next skill, and it needs other people.
- Do not let "everyone" be the customer, or "it depends" be the price.
- Do not be encouraging about an idea that failed three of the four criteria. Say which ones it failed and ask whether they want to fix it or drop it.
Next
When the sentence holds, run validate. Nothing after this point is worth doing
until somebody who is not a friend has reacted to that sentence.
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.

