new-idea
Skill15 starsChanged yesterdayMITView on GitHub
Create a new discovery idea folder with standardized input/output structure. Use when the user wants to prepare an idea for discovery.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- schub-tech/llm-ideation-wikitheir own version, first seen Oct 15, 2026
- akimisri17/idea-to-app-kittheir own version, first seen Oct 8, 2026
- TechTripAi/techtrip-secondbraintheir own version, first seen Sep 15, 2026
- pengasuzie/claude-skillstheir own version, first seen Mar 2, 2026
- pengasuzie/claude-code-startertheir own version, first seen Feb 27, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- schub-tech/llm-ideation-wiki★ 11same name
- TechTripAi/techtrip-secondbrain★ 2same name
- pengasuzie/claude-code-starter★ 1same name
- akimisri17/idea-to-app-kit★ 0same name
- pengasuzie/claude-skills★ 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 repository23 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
1
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 19
Ask the user using AskUserQuestion:
- Very specific: line 55
Run /vern:discovery {name} to execute the pipeline
“Common” is measured: kept by at least 6 in 10 of the 5 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
Vern New Idea
Set up a standardized discovery folder so the user can prepare input materials before running the pipeline.
Step 1: Get the Idea Name
The idea name comes from $ARGUMENTS. If not provided, ask the user for one.
Slugify the name for the directory: lowercase, replace non-alphanumeric with hyphens, collapse multiple hyphens, truncate to 50 chars.
Step 2: Choose Location
Ask the user using AskUserQuestion:
"Where should I create the discovery folder?"
Options:
- Current directory (Recommended) - creates
./discovery/{name}/ - Choose a path - let them type a custom path
Step 3: Create the Folder Structure
{location}/discovery/{name}/
├── input/
│ └── prompt.md # Created with placeholder
└── output/ # Empty, pipeline writes hereCreate input/prompt.md with:
# Discovery: {name}
## Prompt
<!-- Describe your idea here. This will be fed to the discovery pipeline. -->
## Additional Context
<!-- Add any extra context, constraints, or goals. -->Step 4: Tell the User What to Do Next
Report:
- Folder created at
{location}/discovery/{name}/ - They can now:
- Edit
input/prompt.mdwith their idea description - Drop any reference files into
input/(specs, diagrams, existing code, etc.) - Run
/vern:discovery {name}to execute the pipeline
- Edit
- Or skip prep and just run
/vern:discovery {prompt}directly
Begin setup for: $ARGUMENTS
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.

