Agent skill
ideation
Guides structured ideation through Socratic questioning to explore problems, opportunities, and solutions. Use when brainstorming features, exploring use cases, or thinking through new ideas.
Install this agent skill to your Project
npx add-skill https://github.com/nbbaier/agent-skills/tree/main/skills/ideation
SKILL.md
Ideation
A structured questioning approach to help think through new features, use cases, problems, and opportunities.
How This Works
Instead of jumping to solutions, guide the user through layers of understanding:
- Problem/Opportunity Space - What's the real issue or opportunity?
- Context & Constraints - What's the environment and limitations?
- User & Stakeholder Lens - Who's affected and how?
- Solution Exploration - What are the options?
- Validation & Risks - How do we know it works?
Questioning Framework
Layer 1: Surface Understanding
Start here to clarify what they're actually trying to do:
- "What triggered this idea? What happened that made you think of this?"
- "In one sentence, what problem are you trying to solve?"
- "Who would benefit if this existed?"
- "What does success look like?"
Layer 2: Problem Depth
Dig into the mechanics of the problem:
- "Why does this problem exist? What's the root cause?"
- "How are people solving this today? What's wrong with that approach?"
- "What's the cost of not solving this? (time, money, frustration)"
- "Is this a hair-on-fire problem or a nice-to-have?"
Layer 3: Context & Constraints
Understand the boundaries:
- "What technical constraints exist? (stack, integrations, performance)"
- "What resources are available? (time, team, budget)"
- "What's non-negotiable vs. flexible?"
- "What have you tried before that didn't work?"
Layer 4: User Perspective
Get specific about who you're building for:
- "Walk me through the user's current workflow without this solution."
- "What's the most painful step? Where do they give up?"
- "What would they say if you asked them about this problem?"
- "Are there different user segments with different needs?"
Layer 5: Solution Exploration
Now explore options:
- "What's the simplest version that would still be useful?"
- "What would the ideal solution look like with no constraints?"
- "What existing solutions come close? What's missing?"
- "What are 3 completely different approaches to this?"
Layer 6: Validation & Risk
Stress-test the idea:
- "How would we know if this is working?"
- "What could go wrong? What are the biggest risks?"
- "What assumptions are we making that might be wrong?"
- "What's the smallest experiment we could run to learn more?"
Process
- Listen first - Let them explain the idea before questioning
- One question at a time - Don't overwhelm with multiple questions
- Summarize understanding - Reflect back what you heard before moving deeper
- Adapt the layer - Skip layers that aren't relevant; go deeper where needed
- Capture insights - Periodically summarize key discoveries
- End with clarity - Conclude with a clear problem statement + potential next steps
Output Artifacts
After the ideation session, offer to create:
- Problem Statement: One-paragraph summary of the problem/opportunity
- Key Insights: Bullet list of discoveries from the conversation
- Solution Options: 2-3 approaches with tradeoffs
- Next Steps: Concrete actions to move forward
- Open Questions: Things that still need answers
Example Opening
When the skill is triggered, start with:
"Before we dive into solutions, let me understand the problem space first. What triggered this idea? What's the situation or pain point you're seeing?"
Then adapt based on their response - go deeper on problem understanding before exploring solutions.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
logging-best-practices
Use before implementing logs in a medium to large scale production system.
react-effect-patterns
Guidelines for proper React useEffect usage and avoiding unnecessary Effects. Use when writing, reviewing, or refactoring React components that use useEffect, useState, or handle side effects. Triggers on tasks involving React Effects, derived state, event handlers, data fetching, or component synchronization.
implementation-guide
Generate comprehensive implementation guides for coding tasks instead of writing code directly. Use when the user requests detailed implementation documentation, step-by-step development guides, or when they want to implement features themselves using tools like Cursor. Creates exhaustive guides with background context, architecture decisions, milestones with verification points, and rationale for a "build-it-yourself" workflow.
html-tools
Build single-file HTML tools — self-contained HTML+JS+CSS applications that solve a specific problem without a build step. Use this skill whenever the user asks to build a utility, converter, viewer, debugger, or any small interactive web tool. Also trigger when the user says "build me a tool that...", "make a quick app for...", "I need a single-file HTML page that...", or wants to create something that could be hosted as a static file. This skill is specifically for practical, utility-focused tools (not landing pages, portfolios, or marketing sites — use frontend-design for those).
val-town-cli
Manage Val Town projects using the vt CLI. Use when working with Vals (Val Town serverless functions), syncing code to Val Town, creating HTTP endpoints, streaming logs, or managing Val Town branches. Triggers on tasks involving Val Town development, val creation/editing, or when user mentions "vt", "val town", or "vals".
every-style-editor
This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide. It provides a systematic line-by-line review process for grammar, punctuation, mechanics, and style guide compliance.
Didn't find tool you were looking for?