new-idea
Create a new discovery idea folder with standardized input/output structure. Use when the user wants to prepare an idea for discovery.
Best use case
new-idea is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create a new discovery idea folder with standardized input/output structure. Use when the user wants to prepare an idea for discovery.
Teams using new-idea should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/new-idea/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How new-idea Compares
| Feature / Agent | new-idea | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Create a new discovery idea folder with standardized input/output structure. Use when the user wants to prepare an idea for discovery.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 here
```
Create `input/prompt.md` with:
```markdown
# 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:
1. Edit `input/prompt.md` with their idea description
2. Drop any reference files into `input/` (specs, diagrams, existing code, etc.)
3. Run `/vern:discovery {name}` to execute the pipeline
- Or skip prep and just run `/vern:discovery {prompt}` directly
Begin setup for: $ARGUMENTSRelated Skills
yolo
Executes tasks immediately using Gemini sub-agents in --yolo mode with zero confirmation prompts — prioritizes speed and action over caution. Use when the user wants fast execution without guardrails, rapid prototyping, quick-and-dirty solutions, or 'just do it' energy.
vernhole-existing
Run VernHole on existing discovery output. Point the council at a consolidation or master plan and get fresh perspectives.
ux
UX Vern - Cool architecture, but can the user find the button? Empathy-driven design thinking.
startup
Startup Vern - MVP or die trying. Lean, fast, validate assumptions, iterate or pivot.
retro
Retro Vern - We solved this with cron jobs and a CSV in 2004. Grizzled veteran, historical perspective.
rerun-discovery
Rerun a discovery pipeline on an existing project. Cleans previous output and re-runs with fresh config.
paranoid
Paranoid Vern - What could possibly go wrong? Everything. Risk assessment and failure mode specialist.
oracle
Oracle Vern - The ancient seer who reads the council's chaos and finds the signal. Pattern recognition across perspectives.
oracle-consult
Post-hoc Oracle operations - consult the Oracle on existing VernHole output or apply an Oracle vision to rewrite VTS tasks.
optimist
Optimist Vern - Everything will be fine! Sunny-side-up. Encouragement and can-do energy.
nyquil
Nyquil Vern - brilliant as Vernile but the NyQuil is kicking in. Haiku-level brevity.
mighty
Generates comprehensive code and thorough analysis using OpenAI Codex sub-agents — handles large-scale code generation, exhaustive edge case coverage, and detailed boilerplate scaffolding. Use when the user wants comprehensive output, large code generation, thorough analysis, or 'give me everything' solutions.