Loading...
Loading...
Found 202 Skills
Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.
Brainstorm and validate names for plugins, skills, agents, and commands. Use when naming a new plugin, choosing atom names, validating naming conventions, or when user mentions "name plugin", "name skill", "naming convention", "brainstorm names", "what should I call", "plugin name", "good name for".
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
Turn rough ideas into structured, validated idea documents through collaborative dialogue. Explores context, asks clarifying questions one at a time, proposes alternative approaches with feasibility evaluation, and produces documents ready for requirements definition. Use when: "ideation", "brainstorm", "new idea", "explore an idea", "I want to build", "what if we", "let's think about", "propose approaches", "evaluate this idea", "idea document", "アイデア出し", "案出し", "ブレスト", "アイデアを整理", "検討したい".
Generative ideation engine. Takes a domain, trend, question, or constraint and produces 15-30 novel possibilities — things that might be true, businesses that could exist, futures that could unfold. Spawns a team of 6 specialist agents — Signal Scout, Analogist, Inverter, Combinator, Contrarian, Futurist — who each generate ideas from a distinct creative angle. The lead cross-pollinates across agents, finds unexpected combinations, and ranks the output by novelty × plausibility. Use when the user says "brainstorm", "what could exist", "what's possible", "generate ideas", "what might be true", "possibilities", or presents a domain and wants divergent exploration rather than evaluation of a specific idea.
Explore requirements and approaches through collaborative dialogue before writing a right-sized requirements document and planning implementation. Use for feature ideas, problem framing, when the user says 'let's brainstorm', or when they want to think through options before deciding what to build. Also use when a user describes a vague or ambitious feature request, asks 'what should we build', 'help me think through X', presents a problem with multiple valid solutions, or seems unsure about scope or direction — even if they don't explicitly ask to brainstorm.
Brainstorms ideas and researches projects.
Explore requirements and approaches through collaborative dialogue before planning implementation
Generate, refine, research, and validate startup ideas through an interactive founder-specific idea machine. Use when Codex needs to ask a few focused questions, search current public web signals, rapidly brainstorm startup or SaaS ideas, learn from love/maybe/no reactions, produce additional idea rounds, compare finalists, investigate competitors and existing workarounds, select a promising opportunity, or create an evidence-linked Markdown startup-idea report.
Divergent conversation before any artifact exists — open questions one at a time, alternatives including building nothing, converging on a routing decision and a handoff brief for the next skill. Runs before om-spec-writing and om-prepare-issue. Use when the user says "should we build this", "let's think this through", "I have an idea", "is this worth doing".