generated from Paul.Kim/tpl-superclaude
Initial commit
This commit is contained in:
260
.claude/commands/planning/2-brainstorm/2-analyze-ideas.md
Normal file
260
.claude/commands/planning/2-brainstorm/2-analyze-ideas.md
Normal file
@ -0,0 +1,260 @@
|
||||
---
|
||||
allowed-tools: [Read, Write, Glob]
|
||||
description: Analyzes generated ideas from brainstorming session, categorizes them, and suggests next steps for refinement.
|
||||
---
|
||||
|
||||
# Analyze Brainstorming Ideas
|
||||
|
||||
## Context
|
||||
- **User Request:** $ARGUMENTS
|
||||
- **Session Name/Index:** Passed via `--name` argument.
|
||||
- **Session State File:** `_session-state.json` within the specified brainstorm session directory.
|
||||
|
||||
## Goal
|
||||
To analyze the raw ideas generated during the brainstorming session, organize them systematically, identify patterns and themes, evaluate their potential, and provide actionable recommendations for the next phase of development.
|
||||
|
||||
## Process
|
||||
1. **Identify Target Session:**
|
||||
- Use the `--name` argument to locate the correct brainstorm session directory (e.g., `.taskmaster/docs/brainstorm/001-product-features/`).
|
||||
|
||||
2. **Read Session State and Context:**
|
||||
- Read the `_session-state.json` file to understand the session context.
|
||||
- Review the `01_brainstorm_framework.md` file to understand the original objectives and constraints.
|
||||
- Identify the `lastAnalyzedFile` to determine which new files need to be processed.
|
||||
|
||||
3. **Find and Analyze New Ideas:**
|
||||
- Scan the session directory for any `0*_*.md` files created or modified after `lastAnalyzedFile`.
|
||||
- Read the content of the new idea files (typically `02_idea_generation.md`).
|
||||
- Parse and extract individual ideas from the documentation.
|
||||
|
||||
4. **Systematic Idea Analysis:**
|
||||
- **Categorize Ideas:** Group similar ideas into logical themes or categories.
|
||||
- **Evaluate Feasibility:** Assess implementation difficulty and resource requirements.
|
||||
- **Assess Impact Potential:** Evaluate the potential value and significance of each idea.
|
||||
- **Identify Patterns:** Look for recurring themes, innovative approaches, or breakthrough concepts.
|
||||
- **Spot Combinations:** Identify ideas that could be merged or built upon each other.
|
||||
|
||||
5. **Generate Analysis Summary:**
|
||||
- Create a comprehensive analysis file named `_analysis_[topic].md` (e.g., `_analysis_product_features.md`).
|
||||
- Include:
|
||||
- **Executive Summary:** High-level overview of the ideation results
|
||||
- **Idea Categorization:** Organized themes with grouped ideas
|
||||
- **Top Concepts:** Highest-potential ideas based on evaluation criteria
|
||||
- **Feasibility Matrix:** Ideas plotted against impact vs. difficulty
|
||||
- **Pattern Analysis:** Recurring themes and innovative approaches
|
||||
- **Combination Opportunities:** Ideas that could be merged or enhanced
|
||||
- **Quick Wins:** Low-effort, high-impact ideas for immediate implementation
|
||||
- **Moonshot Ideas:** High-risk, high-reward concepts for future consideration
|
||||
|
||||
6. **Update Session State with Intelligent Next Action:**
|
||||
- Update the `_session-state.json` file:
|
||||
- Set `status` to `analysis_complete`.
|
||||
- Update `lastAnalyzedFile` to the name of the file just analyzed.
|
||||
- Update `ideationResults` with quantitative summary.
|
||||
- Formulate the `nextAction` based on the analysis results.
|
||||
|
||||
**Standard Next Actions (contextual selection):**
|
||||
- **If many high-quality ideas generated:** "Create refined concept selection with priority ranking"
|
||||
- **If ideas need validation:** "Conduct concept validation with target users"
|
||||
- **If ideas are too broad:** "Focus and refine top 3-5 concepts"
|
||||
- **If ready for development:** "Generate final brainstorm summary and transition to PRD"
|
||||
|
||||
7. **Report Analysis Results with Actionable Recommendations:**
|
||||
- Present a concise summary of the analysis findings.
|
||||
- Highlight the most promising ideas and their potential impact.
|
||||
- Provide specific recommendations for next steps.
|
||||
- **Generate a refined ideation prompt if additional brainstorming is needed:**
|
||||
|
||||
**Refined Ideation Prompt Template:**
|
||||
```
|
||||
### Refined Ideation Prompt: [Focus Area from Analysis]
|
||||
|
||||
**1. Analysis Context:**
|
||||
- **Total Ideas Generated:** [Number]
|
||||
- **Key Themes Identified:** [List of main categories]
|
||||
- **Top Concepts:** [2-3 highest-potential ideas]
|
||||
- **Gaps Identified:** [Areas needing more exploration]
|
||||
|
||||
**2. Refinement Objective:**
|
||||
- [Specific goal for additional ideation, e.g., "Deepen the top 3 concepts with detailed implementation approaches"]
|
||||
|
||||
**3. Focused Prompts:**
|
||||
- [3-5 specific questions to guide refinement]
|
||||
- [Based on gaps or promising areas from analysis]
|
||||
|
||||
**4. Success Criteria:**
|
||||
- [Updated criteria based on analysis results]
|
||||
```
|
||||
|
||||
8. **Conclude with Clear Next Steps:**
|
||||
- Instruct the user on the recommended next action.
|
||||
- Provide the filename for any additional work needed.
|
||||
- **Example conclusion:** "Based on the analysis, I recommend focusing on the top 5 concepts. Please create `03_concept_refinement.md` with detailed development of these ideas, then run `/planning/brainstorm/2-analyze-ideas --name=[session_name]` again to analyze the refined concepts."
|
||||
|
||||
## Templates & Structures
|
||||
|
||||
### Analysis Summary Template
|
||||
```markdown
|
||||
# Brainstorm Analysis: [Session Name]
|
||||
|
||||
## Executive Summary
|
||||
- **Total Ideas Generated:** [Number]
|
||||
- **Analysis Date:** [Date]
|
||||
- **Key Insight:** [One-sentence summary of main finding]
|
||||
|
||||
## Idea Categorization
|
||||
|
||||
### Category 1: [Theme Name]
|
||||
- **Description:** [What this category represents]
|
||||
- **Ideas:** [List of related ideas]
|
||||
- **Potential Impact:** [Assessment]
|
||||
|
||||
### Category 2: [Theme Name]
|
||||
- **Description:** [What this category represents]
|
||||
- **Ideas:** [List of related ideas]
|
||||
- **Potential Impact:** [Assessment]
|
||||
|
||||
## Top Concepts (Prioritized)
|
||||
|
||||
### 1. [Concept Name]
|
||||
- **Description:** [Detailed explanation]
|
||||
- **Impact Score:** [1-10]
|
||||
- **Feasibility Score:** [1-10]
|
||||
- **Why it's promising:** [Reasoning]
|
||||
|
||||
### 2. [Concept Name]
|
||||
- **Description:** [Detailed explanation]
|
||||
- **Impact Score:** [1-10]
|
||||
- **Feasibility Score:** [1-10]
|
||||
- **Why it's promising:** [Reasoning]
|
||||
|
||||
## Feasibility Matrix
|
||||
|
||||
### Quick Wins (High Impact, Low Effort)
|
||||
- [List of ideas]
|
||||
|
||||
### Major Projects (High Impact, High Effort)
|
||||
- [List of ideas]
|
||||
|
||||
### Fill-ins (Low Impact, Low Effort)
|
||||
- [List of ideas]
|
||||
|
||||
### Questionable (Low Impact, High Effort)
|
||||
- [List of ideas]
|
||||
|
||||
## Pattern Analysis
|
||||
- **Recurring Themes:** [Common patterns across ideas]
|
||||
- **Innovative Approaches:** [Unique or breakthrough concepts]
|
||||
- **User-Centric Focus:** [Ideas that strongly address user needs]
|
||||
|
||||
## Combination Opportunities
|
||||
- **Idea A + Idea B:** [Potential synergies]
|
||||
- **Theme-based Combinations:** [Ways to merge related concepts]
|
||||
|
||||
## Recommendations
|
||||
|
||||
### Immediate Next Steps
|
||||
1. [Specific action recommendation]
|
||||
2. [Specific action recommendation]
|
||||
3. [Specific action recommendation]
|
||||
|
||||
### Future Considerations
|
||||
- [Longer-term opportunities]
|
||||
- [Areas for additional brainstorming]
|
||||
|
||||
## Gaps and Missing Elements
|
||||
- [Areas that need more exploration]
|
||||
- [Stakeholder perspectives not yet considered]
|
||||
```
|
||||
|
||||
### Updated Session State Structure
|
||||
```json
|
||||
{
|
||||
"index": 1,
|
||||
"name": "session-name",
|
||||
"type": "brainstorm",
|
||||
"status": "analysis_complete",
|
||||
"created": "ISO datetime",
|
||||
"lastUpdated": "ISO datetime",
|
||||
"currentStep": "idea_analysis",
|
||||
"completedSteps": ["ideation_setup", "idea_generation"],
|
||||
"nextAction": "specific recommendation based on analysis",
|
||||
"brainstormType": "creative|problem-solving|feature-expansion|market-opportunities",
|
||||
"targetDomain": "user-defined domain",
|
||||
"ideationResults": {
|
||||
"totalIdeas": 42,
|
||||
"categorizedIdeas": {
|
||||
"user-experience": 12,
|
||||
"technical-innovation": 8,
|
||||
"business-model": 6
|
||||
},
|
||||
"topConcepts": [
|
||||
{
|
||||
"name": "concept-name",
|
||||
"impactScore": 9,
|
||||
"feasibilityScore": 7,
|
||||
"category": "user-experience"
|
||||
}
|
||||
],
|
||||
"analysisDate": "ISO datetime"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
## Best Practices
|
||||
|
||||
### ✅ DO: Systematic Categorization
|
||||
- **Use consistent criteria** for grouping ideas into themes
|
||||
- **Look for natural clusters** rather than forcing artificial categories
|
||||
- **Consider multiple perspectives** (user, business, technical) when categorizing
|
||||
- **Document rationale** for categorization decisions
|
||||
|
||||
**Why:** Systematic organization makes patterns visible and helps identify the most promising areas for development.
|
||||
|
||||
### ✅ DO: Balanced Evaluation
|
||||
- **Assess both impact and feasibility** for each idea
|
||||
- **Consider short-term and long-term potential** separately
|
||||
- **Factor in resource constraints** from the original framework
|
||||
- **Use consistent scoring criteria** across all ideas
|
||||
|
||||
**Why:** Balanced evaluation ensures that both ambitious and practical ideas receive appropriate consideration.
|
||||
|
||||
### ✅ DO: Identify Synergies
|
||||
- **Look for complementary ideas** that could be combined
|
||||
- **Consider sequential implementation** where one idea enables another
|
||||
- **Explore theme-based combinations** that address multiple user needs
|
||||
- **Document potential integration points** between related concepts
|
||||
|
||||
**Why:** Combinations often produce more powerful solutions than individual ideas in isolation.
|
||||
|
||||
### ❌ DON'T: Dismiss Ideas Too Quickly
|
||||
- **Don't eliminate ideas based on initial impressions** - analyze them systematically
|
||||
- **Don't ignore "wild" ideas** - they often contain valuable insights
|
||||
- **Don't let feasibility bias** overshadow potentially transformative concepts
|
||||
- **Don't assume resource constraints** are permanent - they may change
|
||||
|
||||
**Why:** Premature dismissal can eliminate breakthrough opportunities that might be valuable with different approaches or timing.
|
||||
|
||||
### ❌ DON'T: Over-Analyze
|
||||
- **Don't spend excessive time** on obviously weak ideas
|
||||
- **Don't get stuck in analysis paralysis** - aim for actionable insights
|
||||
- **Don't perfect the analysis** - focus on identifying clear next steps
|
||||
- **Don't analyze in isolation** - consider the original framework and constraints
|
||||
|
||||
**Why:** Over-analysis can delay progress and obscure the most important insights needed for decision-making.
|
||||
|
||||
## Output
|
||||
- **Format:** Markdown analysis file
|
||||
- **Location:** `.taskmaster/docs/brainstorm/[index]-[session_name]/`
|
||||
- **Primary Files:**
|
||||
- `_analysis_[topic].md` - Comprehensive idea analysis
|
||||
- `_session-state.json` - Updated session state
|
||||
- Optional: `03_concept_refinement.md` - Additional refinement (user-created)
|
||||
|
||||
## Example Usage
|
||||
- **Analyze ideas from a session:**
|
||||
`/planning/brainstorm/2-analyze-ideas --name="product-features"`
|
||||
- **Analyze by index:**
|
||||
`/planning/brainstorm/2-analyze-ideas --name="1"`
|
||||
- **Re-analyze after refinement:**
|
||||
`/planning/brainstorm/2-analyze-ideas --name="product-features"` (automatically detects new files)
|
||||
Reference in New Issue
Block a user