brainstorming-features
Facilitates creative ideation sessions for mobile and web app features, generating structured ideas with user stories, technical considerations, and implementation suggestions. Use when planning new features, exploring product direction, generating app ideas, feature discovery, product brainstorming, or when user mentions 'brainstorm', 'ideate', 'app ideas', or 'feature suggestions'.
下記のコマンドをコピーしてターミナル(Mac/Linux)または PowerShell(Windows)に貼り付けてください。 ダウンロード → 解凍 → 配置まで全自動。
mkdir -p ~/.claude/skills && cd ~/.claude/skills && curl -L -o brainstorming-features.zip https://jpskill.com/download/19034.zip && unzip -o brainstorming-features.zip && rm brainstorming-features.zip
$d = "$env:USERPROFILE\.claude\skills"; ni -Force -ItemType Directory $d | Out-Null; iwr https://jpskill.com/download/19034.zip -OutFile "$d\brainstorming-features.zip"; Expand-Archive "$d\brainstorming-features.zip" -DestinationPath $d -Force; ri "$d\brainstorming-features.zip"
完了後、Claude Code を再起動 → 普通に「動画プロンプト作って」のように話しかけるだけで自動発動します。
💾 手動でダウンロードしたい(コマンドが難しい人向け)
- 1. 下の青いボタンを押して
brainstorming-features.zipをダウンロード - 2. ZIPファイルをダブルクリックで解凍 →
brainstorming-featuresフォルダができる - 3. そのフォルダを
C:\Users\あなたの名前\.claude\skills\(Win)または~/.claude/skills/(Mac)へ移動 - 4. Claude Code を再起動
⚠️ ダウンロード・利用は自己責任でお願いします。当サイトは内容・動作・安全性について責任を負いません。
🎯 このSkillでできること
下記の説明文を読むと、このSkillがあなたに何をしてくれるかが分かります。Claudeにこの分野の依頼をすると、自動で発動します。
📦 インストール方法 (3ステップ)
- 1. 上の「ダウンロード」ボタンを押して .skill ファイルを取得
- 2. ファイル名の拡張子を .skill から .zip に変えて展開(macは自動展開可)
- 3. 展開してできたフォルダを、ホームフォルダの
.claude/skills/に置く- · macOS / Linux:
~/.claude/skills/ - · Windows:
%USERPROFILE%\.claude\skills\
- · macOS / Linux:
Claude Code を再起動すれば完了。「このSkillを使って…」と話しかけなくても、関連する依頼で自動的に呼び出されます。
詳しい使い方ガイドを見る →- 最終更新
- 2026-05-18
- 取得日時
- 2026-05-18
- 同梱ファイル
- 1
📖 Skill本文(日本語訳)
※ 原文(英語/中国語)を Gemini で日本語化したものです。Claude 自身は原文を読みます。誤訳がある場合は原文をご確認ください。
機能のブレインストーミング
概要
このスキルは、体系的なアイデア出しのワークフローを通じて、モバイルおよびウェブアプリケーションの機能アイデアを生成、探索、構造化するのに役立ちます。技術的なコンテキストとユーザー価値を伴う、実用的でよく整理された機能コンセプトを生み出します。
使用する場面
- 新しいアプリの機能や製品の方向性を計画する際
- 既存アプリの機能の可能性を探る際
- MVP (Minimum Viable Product) のアイデアを生成する際
- 機能発見ワークショップ
- 製品ロードマップ計画セッション
- 競合機能分析
- ユーザーの問題解決セッション
ブレインストーミングのワークフロー
1. コンテキストの収集
アイデアを生成する前に、以下を理解します。
プロジェクトのコンテキスト:
- アプリの種類 (モバイル、ウェブ、デスクトップ、PWA)
- 技術スタック (React Native、Next.js など)
- ターゲットユーザーとペルソナ
- 中核となる価値提案
- 既存の機能 (該当する場合)
ブレインストーミングの範囲:
- 特定の機能領域または一般的な探索
- 解決すべき問題または捉えるべき機会
- 制約 (技術的、予算、タイムライン)
- 成功指標
2. アイデア生成方法
方法 A - 問題優先:
- ユーザーのペインポイントを特定します。
- 各ペインポイントに対処するソリューションを生成します。
- 影響度と労力でランク付けします。
- 詳細な探索のために上位3〜5つを選択します。
方法 B - 機会優先:
- 市場の機会やトレンドをリストアップします。
- 機会を活用する機能を生成します。
- 実現可能性と差別化を評価します。
- 有望なコンセプトを選択します。
方法 C - 競合分析:
- 競合他社の機能をレビューします。
- ギャップと改善点を特定します。
- 独自のバリエーションや強化を生成します。
- 競争優位性によって優先順位を付けます。
方法 D - ユーザー体験マッピング:
- 現在のユーザー体験をマッピングします。
- 摩擦点を特定します。
- 体験をスムーズにする機能を生成します。
- ユーザーフローの改善に対してテストします。
3. 機能構造テンプレート
各機能アイデアについて、以下を提供します。
## Feature: [Feature Name]
**One-line description:**
[Brief, compelling description in 10-15 words]
**Problem it solves:**
[User pain point or opportunity addressed]
**Target users:**
[Primary and secondary user personas]
**User story:**
As a [user type], I want to [action] so that [benefit].
**Key capabilities:**
- Capability 1
- Capability 2
- Capability 3
**Technical considerations:**
- Technology/library suggestions
- Integration points
- Data requirements
- Potential challenges
**Implementation complexity:**
[Low / Medium / High] - [Brief justification]
**Expected impact:**
[User value and business value]
**Success metrics:**
- Metric 1 (e.g., engagement increase)
- Metric 2 (e.g., task completion rate)
4. アイデアの洗練
初期生成後、アイデアを以下によって洗練します。
実現可能性チェック:
- 現在のスタックでの技術的達成可能性
- リソース要件 (時間、チーム、インフラストラクチャ)
- 他の機能やシステムへの依存関係
価値評価:
- ユーザー価値スコア (1-10)
- ビジネス価値スコア (1-10)
- 労力見積もり (人日またはストーリーポイント)
優先順位付けマトリックス:
High Value, Low Effort → Do First (Quick Wins)
High Value, High Effort → Strategic Investments
Low Value, Low Effort → Consider Later
Low Value, High Effort → Avoid
5. 出力形式
形式 1 - 機能概要 (詳細): 上位3〜5つの機能に上記の完全なテンプレートを使用します。
形式 2 - 機能リスト (簡潔):
1. **[Feature Name]** - [One-line description] [Complexity: Low/Med/High]
2. **[Feature Name]** - [One-line description] [Complexity: Low/Med/High]
...
形式 3 - 機能ロードマップ: フェーズまたはスプリントごとに整理します。
### Phase 1 - Foundation (Sprint 1-2)
- Feature A (enables core workflow)
- Feature B (critical user need)
### Phase 2 - Enhancement (Sprint 3-4)
- Feature C (improves experience)
- Feature D (adds value)
### Phase 3 - Advanced (Sprint 5+)
- Feature E (differentiator)
- Feature F (scale optimization)
例
例 1 - モバイルノートアプリ
コンテキスト: 看護学生向けのReact Nativeノートアプリ
ブレインストーミングリクエスト: 「学習効率を向上させる5つの機能アイデアを生成してください」
出力:
## Feature: AI-Powered Flashcard Generation
**One-line description:**
Automatically create study flashcards from notes using AI term extraction
**Problem it solves:**
Students spend hours manually creating flashcards instead of studying
**Target users:**
Nursing students preparing for exams and clinical rotations
**User story:**
As a nursing student, I want my notes automatically converted to flashcards so that I can focus on studying instead of card creation.
**Key capabilities:**
- Auto-detect medical terms and concepts
- Generate question-answer pairs from context
- Spaced repetition scheduling
- Manual edit and refinement
**Technical considerations:**
- OpenAI API for term extraction
- IndexedDB/Dexie for local flashcard storage
- Background processing for large notes
- Offline-first sync with Firestore
**Implementation complexity:**
Medium - Requires AI integration and smart parsing logic, but leverages existing note structure
**Expected impact:**
- 70% reduction in flashcard creation time
- Increased study time availability
- Higher exam preparation quality
**Success metrics:**
- Flashcards generated per note
- User edits to auto-generated cards (lower = better accuracy)
- Study session frequency increase
例 2 - Eコマースプラットフォーム
コンテキスト: Next.js Eコマースプラットフォーム、初期段階
ブレインストーミングリクエスト: 「チェックアウトフローの改善についてブレインストーミングしてください」
出力 (簡潔な形式):
1. **One-Click Reorder** - Save previous orders as templates for instant reordering [Complexity: Low]
2. **Smart Address Autocomplete** - Google Places API integration for accurate shipping addresses [Complexity: Low]
3. **Guest Checkout Express** - No account required, optional account creation post-purchase [Complexity: Medium]
4. **Cart Recovery Emails** - Automated emails for abandoned carts with incentives [Complexity: Medium]
5. **Buy 📜 原文 SKILL.md(Claudeが読む英語/中国語)を展開
Brainstorming Features
Overview
This skill helps generate, explore, and structure feature ideas for mobile and web applications through systematic ideation workflows. It produces actionable, well-organized feature concepts with technical context and user value.
When to Use
- Planning new app features or product directions
- Exploring feature possibilities for existing apps
- Generating ideas for MVP (Minimum Viable Product)
- Feature discovery workshops
- Product roadmap planning sessions
- Competitive feature analysis
- User problem-solving sessions
Brainstorming Workflow
1. Context Gathering
Before generating ideas, understand:
Project Context:
- App type (mobile, web, desktop, PWA)
- Tech stack (React Native, Next.js, etc.)
- Target users and personas
- Core value proposition
- Existing features (if applicable)
Brainstorming Scope:
- Specific feature area or general exploration
- Problem to solve or opportunity to capture
- Constraints (technical, budget, timeline)
- Success metrics
2. Idea Generation Methods
Method A - Problem-First:
- Identify user pain points
- Generate solutions addressing each pain point
- Rank by impact vs. effort
- Select top 3-5 for detailed exploration
Method B - Opportunity-First:
- List market opportunities or trends
- Generate features leveraging opportunities
- Assess feasibility and differentiation
- Select promising concepts
Method C - Competitive Analysis:
- Review competitor features
- Identify gaps and improvements
- Generate unique variations or enhancements
- Prioritize by competitive advantage
Method D - User Journey Mapping:
- Map current user journey
- Identify friction points
- Generate features smoothing the journey
- Test against user flow improvements
3. Feature Structure Template
For each feature idea, provide:
## Feature: [Feature Name]
**One-line description:**
[Brief, compelling description in 10-15 words]
**Problem it solves:**
[User pain point or opportunity addressed]
**Target users:**
[Primary and secondary user personas]
**User story:**
As a [user type], I want to [action] so that [benefit].
**Key capabilities:**
- Capability 1
- Capability 2
- Capability 3
**Technical considerations:**
- Technology/library suggestions
- Integration points
- Data requirements
- Potential challenges
**Implementation complexity:**
[Low / Medium / High] - [Brief justification]
**Expected impact:**
[User value and business value]
**Success metrics:**
- Metric 1 (e.g., engagement increase)
- Metric 2 (e.g., task completion rate)
4. Idea Refinement
After initial generation, refine ideas by:
Feasibility Check:
- Technical achievability with current stack
- Resource requirements (time, team, infrastructure)
- Dependencies on other features or systems
Value Assessment:
- User value score (1-10)
- Business value score (1-10)
- Effort estimate (person-days or story points)
Prioritization Matrix:
High Value, Low Effort → Do First (Quick Wins)
High Value, High Effort → Strategic Investments
Low Value, Low Effort → Consider Later
Low Value, High Effort → Avoid
5. Output Formats
Format 1 - Feature Brief (Detailed): Use the full template above for 3-5 top features
Format 2 - Feature List (Concise):
1. **[Feature Name]** - [One-line description] [Complexity: Low/Med/High]
2. **[Feature Name]** - [One-line description] [Complexity: Low/Med/High]
...
Format 3 - Feature Roadmap: Organize by phases or sprints:
### Phase 1 - Foundation (Sprint 1-2)
- Feature A (enables core workflow)
- Feature B (critical user need)
### Phase 2 - Enhancement (Sprint 3-4)
- Feature C (improves experience)
- Feature D (adds value)
### Phase 3 - Advanced (Sprint 5+)
- Feature E (differentiator)
- Feature F (scale optimization)
Examples
Example 1 - Mobile Note-Taking App
Context: React Native note-taking app for nursing students
Brainstorm Request: "Generate 5 feature ideas to improve study efficiency"
Output:
## Feature: AI-Powered Flashcard Generation
**One-line description:**
Automatically create study flashcards from notes using AI term extraction
**Problem it solves:**
Students spend hours manually creating flashcards instead of studying
**Target users:**
Nursing students preparing for exams and clinical rotations
**User story:**
As a nursing student, I want my notes automatically converted to flashcards so that I can focus on studying instead of card creation.
**Key capabilities:**
- Auto-detect medical terms and concepts
- Generate question-answer pairs from context
- Spaced repetition scheduling
- Manual edit and refinement
**Technical considerations:**
- OpenAI API for term extraction
- IndexedDB/Dexie for local flashcard storage
- Background processing for large notes
- Offline-first sync with Firestore
**Implementation complexity:**
Medium - Requires AI integration and smart parsing logic, but leverages existing note structure
**Expected impact:**
- 70% reduction in flashcard creation time
- Increased study time availability
- Higher exam preparation quality
**Success metrics:**
- Flashcards generated per note
- User edits to auto-generated cards (lower = better accuracy)
- Study session frequency increase
Example 2 - E-Commerce Platform
Context: Next.js e-commerce platform, early stage
Brainstorm Request: "Brainstorm checkout flow improvements"
Output (Concise Format):
1. **One-Click Reorder** - Save previous orders as templates for instant reordering [Complexity: Low]
2. **Smart Address Autocomplete** - Google Places API integration for accurate shipping addresses [Complexity: Low]
3. **Guest Checkout Express** - No account required, optional account creation post-purchase [Complexity: Medium]
4. **Cart Recovery Emails** - Automated emails for abandoned carts with incentives [Complexity: Medium]
5. **Buy Now Pay Later Integration** - Klarna/Afterpay integration for flexible payments [Complexity: High]
6. **Multi-Item Gift Options** - Individual gift wrapping and messages per item [Complexity: Medium]
7. **Saved Payment Methods** - Tokenized card storage with Stripe for returning customers [Complexity: Medium]
Example 3 - Fitness Tracking App
Context: Exploring gamification features
Brainstorm Request: "Generate gamification ideas for workout motivation"
Output (Feature Brief):
## Feature: Achievement Streak Tracker
**One-line description:**
Visual streak counter with milestone rewards for consecutive workout days
**Problem it solves:**
Users lack motivation to maintain consistent workout routines
**Target users:**
Casual fitness enthusiasts seeking habit formation
**User story:**
As a user, I want to see my workout streak and earn rewards so that I stay motivated to exercise daily.
**Key capabilities:**
- Daily streak counter with flame icon visualization
- Milestone badges (7-day, 30-day, 100-day streaks)
- Streak freeze option (1 per week)
- Social sharing of achievements
- Push notifications for streak risk
**Technical considerations:**
- Local notification scheduling (Expo Notifications)
- Streak calculation with timezone handling
- Badge icon assets and animations
- Firebase Cloud Functions for streak validation
- Social sharing via React Native Share
**Implementation complexity:**
Low - Simple date tracking logic with notification system
**Expected impact:**
- 40% increase in daily active users
- 25% improvement in 30-day retention
- Higher social engagement and viral growth
**Success metrics:**
- % users with active streaks
- Average streak length
- Notification engagement rate
- Social shares per achievement
Best Practices
Do:
- Start broad, then narrow to specific features
- Consider technical feasibility early
- Include user value in every idea
- Provide clear prioritization rationale
- Use concrete examples over abstract concepts
- Balance innovation with practicality
Don't:
- Generate ideas without context
- Ignore technical constraints
- Overlook existing features or patterns
- Skip impact assessment
- Propose features without user stories
- Forget about implementation complexity
Brainstorming Triggers
Respond to these phrases by activating this skill:
- "Brainstorm features for..."
- "Generate app ideas for..."
- "What features could we add to..."
- "Help me ideate on..."
- "Feature discovery session for..."
- "Explore possibilities for..."
Iteration and Refinement
After initial brainstorming:
- User Feedback: Validate ideas against actual user needs
- Technical Review: Assess implementation details with engineering team
- Design Exploration: Create mockups or wireframes for top ideas
- MVP Scoping: Identify minimum feature set for initial release
- Roadmap Planning: Sequence features based on dependencies and value
Additional Resources
For further refinement, consider:
- references/feature-templates.md - More detailed templates for specific feature types
- references/prioritization-frameworks.md - Advanced prioritization methods (RICE, MoSCoW, Kano)