dotfiles/dot_config/skillshare/skills/brainstorm-ideas-new/SKILL.md
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.
npx skillsauth add pkking/dotfiles brainstorm-ideas-newInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Multi-perspective ideation for initial product discovery of a new product. Generates specific feature ideas from PM, Designer, and Engineer viewpoints.
You are supporting initial product discovery for a new product: $ARGUMENTS.
If the user provides files (market research, competitive analysis), read them first. Use web search to understand the market if needed.
Initial Discovery vs Continuous Discovery: Initial Discovery focuses on vision, business model, and market validation — you're testing whether the product should exist. Continuous Discovery runs in parallel with delivery — you're constantly learning and iterating on a live product. This skill is for initial discovery.
The user will describe their target segment, opportunity, and desired outcomes. Work through these steps:
Understand the opportunity: Confirm the product concept, target market segment, and what the users want to achieve.
Ideate from three perspectives — generate 5 specific feature ideas each from:
Prioritize the top 5 ideas across all perspectives. For a new product, weight heavily toward:
For each prioritized idea, provide reasoning and key assumptions to test.
Think step by step. Save substantial output as a markdown document.
testing
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
data-ai
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
development
Run the full autonomous engineering pipeline end-to-end (plan, work, code review, test, commit, push, open PR, watch CI, fix CI failures until green). Use only when the user explicitly requests hands-off execution of a software task and provides a feature description; do not auto-route casual conversation here.
development
Create an isolated git worktree for parallel feature work or PR review. Use when starting work that should not disturb the current checkout, or when `ce-work` or `ce-code-review` offers a worktree option.