원클릭으로
new-idea
Create a new discovery idea folder with standardized input/output structure. Use when the user wants to prepare an idea for discovery.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Create a new discovery idea folder with standardized input/output structure. Use when the user wants to prepare an idea for discovery.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Runs a multi-LLM discovery pipeline (Default 5-step or Expanded 7-step) that chains analysis, refinement, chaos-checking, and consolidation across LLMs, then breaks results into actionable VTS tasks. Use when the user wants to explore, validate, or plan an idea through multiple AI perspectives.
Delivers high-quality, production-grade code using Opus-level reasoning — clean architecture, thorough error handling, tests, and documentation. Use when the user asks for elegant solutions, quality-first code, architectural excellence, or best-practice implementations.
Performs deep, multi-pass exploration of a problem using Claude sub-agents — runs 3+ planning passes from different angles, then synthesizes insights into a holistic solution. Use when the user wants deep thinking, creative exploration, unconventional approaches, or multi-perspective analysis of a complex problem.
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.
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.
Generate a new Vern persona using AI
| name | new-idea |
| description | Create a new discovery idea folder with standardized input/output structure. Use when the user wants to prepare an idea for discovery. |
| argument-hint | <idea-name> |
Set up a standardized discovery folder so the user can prepare input materials before running the pipeline.
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.
Ask the user using AskUserQuestion:
"Where should I create the discovery folder?"
Options:
./discovery/{name}/{location}/discovery/{name}/
├── input/
│ └── prompt.md # Created with placeholder
└── output/ # Empty, pipeline writes here
Create 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. -->
Report:
{location}/discovery/{name}/input/prompt.md with their idea descriptioninput/ (specs, diagrams, existing code, etc.)/vern:discovery {name} to execute the pipeline/vern:discovery {prompt} directlyBegin setup for: $ARGUMENTS