Paul.Kim/tst-claude-code-samples
1
0
Fork 0
generated from Paul.Kim/tpl-superclaude
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial commit

Browse Source
This commit is contained in:
Paul.Kim
2025-07-21 14:31:56 +09:00
commit 15b3eaf5cb
89 changed files with 10770 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

215
.claude/commands/planning/2-brainstorm/1-start-brainstorm.md Normal file
View File

@ -0,0 +1,215 @@
---
allowed-tools: [Read, Write, Glob, TodoWrite]
description: Starts a new brainstorming session for creative idea generation and systematic organization.
---
# Start Brainstorming Session
## Context
- **User Request:** $ARGUMENTS
- **Brainstorm Directory:** `.taskmaster/docs/brainstorm/`
- **Existing Sessions:** !`ls -ld .taskmaster/docs/brainstorm/*/ 2>/dev/null || echo "No existing brainstorm sessions found"`
## Goal
To initialize a new brainstorming session, set up the dedicated workspace, and guide the user through a structured creative ideation process that transforms abstract concepts into organized, actionable ideas.
## Process
1. **Determine Session Index:**
- Scan the `.taskmaster/docs/brainstorm/` directory to find the highest existing session index.
- Assign the next sequential number for the new session.
2. **Create Session Directory:**
- Create a new directory named `[index]-[session_name]` inside `.taskmaster/docs/brainstorm/`.
- Example: `.taskmaster/docs/brainstorm/001-product-features/`
3. **Initialize Session State:**
- Create a `_session-state.json` file in the new session directory.
- Initialize it with session details:
```json
{
"index": 1,
"name": "session-name",
"type": "brainstorm",
"status": "initialized",
"created": "2025-01-16T00:00:00Z",
"lastUpdated": "2025-01-16T00:00:00Z",
"currentStep": "ideation_setup",
"completedSteps": [],
"nextAction": "Begin interactive ideation setup",
"brainstormType": "creative|problem-solving|feature-expansion",
"targetDomain": "user-defined",
"ideationResults": {}
}
```
4. **Interactive Brainstorming Setup:**
- Engage the user in a structured conversation to define the brainstorming scope and approach.
- **Ask clarifying questions to build the foundational framework:**
1. **"What type of brainstorming session do you want to conduct?"**
- a) **Creative Ideation** - Generate innovative product concepts, features, or solutions
- b) **Problem-Solving** - Address specific challenges or obstacles
- c) **Feature Expansion** - Explore variations and improvements of existing ideas
- d) **Market Opportunities** - Identify new business or market possibilities
2. **"What is the central topic or challenge you want to explore?"**
- Prompt for a clear, concise problem statement or topic focus
3. **"Who is your target audience or user group?"**
- Define the primary beneficiaries of the ideas being generated
4. **"What constraints or parameters should guide the brainstorming?"**
- Budget limitations, technical constraints, timeline, regulatory requirements, etc.
5. **"What success criteria will you use to evaluate ideas?"**
- Feasibility, impact, innovation level, resource requirements, market potential
6. **"How many ideas are you aiming to generate?"**
- Set a target number to guide the brainstorming intensity (e.g., 20-50 ideas)
5. **Generate Initial Framework Document:**
- Create `01_brainstorm_framework.md` file with the synthesized setup information.
- Include:
- Session objectives and scope
- Target audience and constraints
- Success criteria and evaluation framework
- Ideation methodology to be used
6. **Assign First Ideation Task:**
- Based on the brainstorming type and framework, present the first ideation task.
- Provide structured guidance and creative prompts.
- **Generate a detailed, self-contained ideation prompt:**
**Ideation Prompt Generation Template:**
```
### Ideation Prompt: [Brainstorming Session Name]
**1. Session Context:**
- **Topic/Challenge:** [From framework - e.g., "Improving user onboarding experience"]
- **Target Audience:** [From framework - e.g., "First-time SaaS users aged 25-45"]
- **Brainstorm Type:** [From framework - e.g., "Creative Ideation"]
- **Constraints:** [From framework - e.g., "Mobile-first design, 3-step maximum process"]
**2. Ideation Objective:**
- [Clear goal for this ideation session, e.g., "Generate 30+ innovative ideas for streamlining user onboarding"]
**3. Creative Prompts:**
- [3-5 specific creative triggers, e.g.:]
- "How might we make onboarding feel like a game?"
- "What if users could onboard through storytelling?"
- "How can we reduce cognitive load in the first 60 seconds?"
**4. Ideation Techniques:**
- **Technique 1:** [e.g., "Rapid Fire - Generate 1 idea per minute for 20 minutes"]
- **Technique 2:** [e.g., "SCAMPER Method - Substitute, Combine, Adapt, Modify, Put to other use, Eliminate, Reverse"]
- **Technique 3:** [e.g., "What If Scenarios - Explore extreme possibilities"]
**5. Documentation Format:**
- Record each idea with: Title, Description (2-3 sentences), Potential Impact (1-10), Implementation Difficulty (1-10)
- Group similar ideas into themes as you go
- Note any breakthrough moments or unexpected connections
**6. Success Metrics:**
- [Target number of ideas and quality indicators from framework]
```
7. **Conclude with Clear Next Steps:**
- Instruct the user to document their ideas in `02_idea_generation.md`
- Provide the complete ideation prompt for reference
- **Example conclusion:** "Once you have completed your ideation session and documented your ideas in `02_idea_generation.md`, please run `/planning/brainstorm/2-analyze-ideas --name=[session_name]` to analyze and organize your ideas."
## Templates & Structures
### Brainstorm Framework Template
```markdown
# Brainstorm Framework: [Session Name]
## Session Overview
- **Type:** [Creative Ideation/Problem-Solving/Feature Expansion/Market Opportunities]
- **Central Topic:** [Core challenge or focus area]
- **Target Audience:** [Primary beneficiaries]
- **Session Date:** [Date]
## Constraints & Parameters
- [List of limitations, requirements, or boundaries]
## Success Criteria
- [Evaluation framework for generated ideas]
## Ideation Methodology
- [Specific techniques and approaches to be used]
## Expected Outcomes
- [Target number of ideas and desired quality level]
```
### Session State Structure
```json
{
"index": 1,
"name": "session-name",
"type": "brainstorm",
"status": "initialized|in_progress|completed",
"created": "ISO datetime",
"lastUpdated": "ISO datetime",
"currentStep": "current_step_name",
"completedSteps": ["step1", "step2"],
"nextAction": "specific next action description",
"brainstormType": "creative|problem-solving|feature-expansion|market-opportunities",
"targetDomain": "user-defined domain",
"ideationResults": {
"totalIdeas": 0,
"categorizedIdeas": {},
"topConcepts": []
}
}
```
## Best Practices
### ✅ DO: Encourage Divergent Thinking
- **Create a judgment-free environment** where all ideas are welcomed
- **Use time-boxed sessions** to maintain energy and focus
- **Prompt for quantity over quality** initially - refinement comes later
- **Encourage wild ideas** - they often lead to breakthrough innovations
- **Build on others' ideas** - use "Yes, and..." approach
**Why:** Divergent thinking generates the raw material for innovation. Premature evaluation kills creativity.
### ✅ DO: Provide Structure Within Creativity
- **Use proven ideation techniques** (SCAMPER, Mind Mapping, Six Thinking Hats)
- **Set clear time boundaries** for each ideation round
- **Rotate between different creative approaches** to stimulate varied thinking
- **Document everything** - even "bad" ideas can spark good ones
**Why:** Structure provides a framework that actually enhances creativity rather than constraining it.
### ❌ DON'T: Judge Ideas During Generation
- **No criticism or evaluation** during the ideation phase
- **Don't overthink feasibility** - focus on possibilities
- **Avoid perfectionism** - capture ideas quickly and move on
- **Don't let one person dominate** - ensure equal participation
**Why:** Evaluation and criticism shut down the creative process. Separation of divergent and convergent thinking is crucial.
### ❌ DON'T: Skip the Framework Phase
- **Don't start ideating without clear objectives**
- **Don't ignore constraints** - they actually help focus creativity
- **Don't proceed without success criteria** - how will you know when you're done?
**Why:** A clear framework ensures the brainstorming session produces actionable results rather than random ideas.
## Output
- **Format:** Multiple Markdown files within session directory
- **Location:** `.taskmaster/docs/brainstorm/[index]-[session_name]/`
- **Primary Files:**
- `_session-state.json` - Session tracking and metadata
- `01_brainstorm_framework.md` - Session setup and parameters
- `02_idea_generation.md` - Raw ideation output (user-created)
## Example Usage
- **Start a new creative session:**
`/planning/brainstorm/1-start-brainstorm --name="product-features"`
- **Start a problem-solving session:**
`/planning/brainstorm/1-start-brainstorm --name="user-retention-challenges"`
- **Start a feature expansion session:**
`/planning/brainstorm/1-start-brainstorm --name="dashboard-improvements"`

260
.claude/commands/planning/2-brainstorm/2-analyze-ideas.md Normal file
View 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)

321
.claude/commands/planning/2-brainstorm/3-generate-brainstorm-summary.md Normal file
View File

@ -0,0 +1,321 @@
---
allowed-tools: [Read, Write, Glob]
description: Generates the final brainstorm summary document by consolidating all ideation and analysis from a session.
---
# Generate Brainstorm Summary
## Context
- **User Request:** $ARGUMENTS
- **Session Name/Index:** Passed via `--name` argument.
- **All Session Files:** All `0*_*.md` (user ideation) and `_analysis_*.md` (AI analysis) files within the target brainstorm session directory.
## Goal
To synthesize all ideation activities and analytical insights from a completed brainstorming session into a single, coherent, and actionable Brainstorm Summary Document that can serve as input for product development, PRD creation, or further strategic planning.
## Process
1. **Identify Target Session:**
- Use the `--name` argument to locate the correct brainstorm session directory.
2. **Aggregate All Session Data:**
- Read the content of the brainstorm framework file (`01_brainstorm_framework.md`).
- Read the content of all user ideation files (`02_idea_generation.md`, `03_concept_refinement.md`, etc.).
- Read the content of all AI analysis files (`_analysis_*.md`).
- Read the session state file (`_session-state.json`) for metadata and context.
3. **Synthesize and Structure Content:**
- Comprehensively analyze the aggregated information.
- Identify the most valuable insights and breakthrough concepts.
- Create a coherent narrative that connects the ideation process to actionable outcomes.
- Organize content into a logical structure that supports decision-making.
4. **Generate Executive Summary:**
- Create a high-level overview that captures:
- Session objectives and approach
- Key quantitative results (total ideas, categories, etc.)
- Most significant insights and breakthrough concepts
- Recommended next steps and implementation priorities
5. **Develop Concept Portfolio:**
- **Tier 1 Concepts:** Highest-priority ideas ready for immediate development
- **Tier 2 Concepts:** Promising ideas requiring further validation or refinement
- **Tier 3 Concepts:** Innovative ideas for future consideration
- **Quick Wins:** Low-effort, high-impact ideas for immediate implementation
6. **Create Implementation Roadmap:**
- Prioritize concepts based on impact, feasibility, and strategic alignment
- Suggest logical sequencing for development
- Identify resource requirements and dependencies
- Provide transition guidance to next phase (PRD, development, etc.)
7. **Generate Final Summary Document:**
- Create the final document named `brainstorm-summary_[session_name].md`.
- Structure the content according to the template below.
- Ensure the document is actionable and ready for stakeholder review.
8. **Finalize Session State:**
- Update the `_session-state.json` file by setting the `status` to `completed`.
- Record final metrics and outcomes.
- This marks the brainstorming session as complete.
9. **Notify User and Suggest Next Steps:**
- Inform the user that the brainstorm summary has been successfully generated.
- Provide the file path and key highlights.
- Proactively suggest logical next steps based on the session outcomes.
- **Example suggestions:**
- "Your brainstorm summary is complete. Based on the results, I recommend creating a PRD using `/planning/prd/2-create-from-brainstorm --name=[session_name]`"
- "Consider validating the top 3 concepts with target users before proceeding to development"
- "The technical concepts suggest creating a roadmap with `/planning/roadmap/1-define-roadmap --from-brainstorm=[session_name]`"
## Templates & Structures
### Brainstorm Summary Document Template
```markdown
# Brainstorm Summary: [Session Name]
**Session Date:** [Date]
**Session Type:** [Creative Ideation/Problem-Solving/Feature Expansion/Market Opportunities]
**Facilitator:** AI-Guided Brainstorming System
---
## Executive Summary
### Session Overview
- **Objective:** [Original brainstorming objective]
- **Target Domain:** [Area of focus]
- **Constraints:** [Key limitations and parameters]
- **Duration:** [Time span of session]
### Key Results
- **Total Ideas Generated:** [Number]
- **Major Categories:** [List of main themes]
- **Breakthrough Concepts:** [Number of innovative ideas]
- **Implementation-Ready Ideas:** [Number of actionable concepts]
### Strategic Insights
- **Primary Finding:** [Most significant insight]
- **Market Opportunity:** [Key opportunities identified]
- **Innovation Potential:** [Assessment of creative breakthrough]
---
## Concept Portfolio
### Tier 1: Priority Concepts (Ready for Development)
#### 1. [Concept Name]
- **Description:** [Detailed explanation]
- **Impact Potential:** [High/Medium/Low] - [Reasoning]
- **Feasibility:** [High/Medium/Low] - [Assessment]
- **Resource Requirements:** [Estimated effort]
- **Success Criteria:** [How to measure success]
- **Next Steps:** [Specific actions needed]
#### 2. [Concept Name]
- **Description:** [Detailed explanation]
- **Impact Potential:** [High/Medium/Low] - [Reasoning]
- **Feasibility:** [High/Medium/Low] - [Assessment]
- **Resource Requirements:** [Estimated effort]
- **Success Criteria:** [How to measure success]
- **Next Steps:** [Specific actions needed]
### Tier 2: Promising Concepts (Require Validation)
#### [Concept Name]
- **Description:** [Brief explanation]
- **Why Promising:** [Potential value]
- **Validation Needed:** [What needs to be tested/confirmed]
- **Timeline:** [When to revisit]
### Tier 3: Future Innovations (Long-term Potential)
#### [Concept Name]
- **Description:** [Brief explanation]
- **Innovation Factor:** [What makes it unique]
- **Barriers:** [Current limitations]
- **Future Triggers:** [Conditions that would make it viable]
---
## Implementation Roadmap
### Phase 1: Quick Wins (0-3 months)
- **[Concept Name]:** [Brief description and rationale]
- **[Concept Name]:** [Brief description and rationale]
- **Success Metrics:** [How to measure progress]
### Phase 2: Core Development (3-12 months)
- **[Concept Name]:** [Brief description and rationale]
- **[Concept Name]:** [Brief description and rationale]
- **Dependencies:** [What needs to be in place]
### Phase 3: Innovation Projects (12+ months)
- **[Concept Name]:** [Brief description and rationale]
- **[Concept Name]:** [Brief description and rationale]
- **Research Requirements:** [Additional investigation needed]
---
## Category Analysis
### [Category Name]
- **Theme:** [What this category represents]
- **Ideas Count:** [Number of ideas in this category]
- **Top Concepts:** [Best ideas from this category]
- **Implementation Notes:** [Special considerations]
### [Category Name]
- **Theme:** [What this category represents]
- **Ideas Count:** [Number of ideas in this category]
- **Top Concepts:** [Best ideas from this category]
- **Implementation Notes:** [Special considerations]
---
## Process Insights
### What Worked Well
- [Effective ideation techniques]
- [Productive creative approaches]
- [Successful breakthrough moments]
### Lessons Learned
- [Key insights about the creative process]
- [Unexpected discoveries]
- [Process improvements for future sessions]
### Recommended Improvements
- [Suggestions for future brainstorming sessions]
- [Areas for deeper exploration]
- [Stakeholder input needed]
---
## Next Steps & Recommendations
### Immediate Actions (Next 2 weeks)
1. [Specific action with owner and timeline]
2. [Specific action with owner and timeline]
3. [Specific action with owner and timeline]
### Medium-term Priorities (Next 3 months)
1. [Strategic action with requirements]
2. [Strategic action with requirements]
3. [Strategic action with requirements]
### Long-term Vision (6-12 months)
1. [Vision-level action with success criteria]
2. [Vision-level action with success criteria]
### Suggested Transition
- **If moving to PRD:** [Specific concepts to focus on]
- **If moving to Roadmap:** [Technical considerations identified]
- **If additional brainstorming needed:** [Areas requiring deeper exploration]
---
## Appendices
### A. Full Idea Inventory
[Complete list of all ideas generated, organized by category]
### B. Evaluation Criteria
[Detailed scoring methodology used for concept evaluation]
### C. Session Artifacts
- Original framework document
- Raw ideation outputs
- Analysis summaries
```
### Final Session State Structure
```json
{
"index": 1,
"name": "session-name",
"type": "brainstorm",
"status": "completed",
"created": "ISO datetime",
"lastUpdated": "ISO datetime",
"currentStep": "summary_complete",
"completedSteps": ["ideation_setup", "idea_generation", "idea_analysis", "summary_creation"],
"nextAction": "Session complete - ready for PRD/Roadmap transition",
"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",
"tier": 1
}
],
"analysisDate": "ISO datetime",
"summaryGenerated": "ISO datetime"
}
}
```
## Best Practices
### ✅ DO: Create Actionable Outcomes
- **Focus on implementation-ready concepts** rather than abstract ideas
- **Provide specific next steps** for each priority concept
- **Include success criteria** and measurable outcomes
- **Consider resource requirements** realistically
**Why:** A brainstorm summary should bridge creative thinking with practical execution.
### ✅ DO: Maintain Strategic Perspective
- **Align concepts with original objectives** and constraints
- **Consider business impact** alongside creative merit
- **Evaluate concepts within competitive context** if relevant
- **Think about scalability** and long-term potential
**Why:** Strategic alignment ensures that creative outputs serve business objectives.
### ✅ DO: Preserve Creative Insights
- **Document breakthrough moments** and innovative approaches
- **Capture unexpected connections** between ideas
- **Preserve minority opinions** and unconventional thinking
- **Note process insights** for future brainstorming sessions
**Why:** Creative insights often contain valuable intelligence that extends beyond specific ideas.
### ❌ DON'T: Oversimplify Complex Ideas
- **Don't reduce innovative concepts** to simple feature requests
- **Don't ignore implementation complexity** when it's relevant
- **Don't dismiss ideas** that don't fit current priorities
- **Don't lose nuance** in the synthesis process
**Why:** Oversimplification can destroy the value of creative insights and innovative thinking.
### ❌ DON'T: Skip Prioritization
- **Don't present all ideas as equally important** - provide clear hierarchy
- **Don't ignore feasibility constraints** when prioritizing
- **Don't forget about resource limitations** in implementation planning
- **Don't avoid making recommendations** - stakeholders need guidance
**Why:** Unprioritized outputs create decision paralysis and reduce the value of the brainstorming investment.
## Output
- **Format:** Comprehensive Markdown document
- **Location:** `.taskmaster/docs/brainstorm/[index]-[session_name]/`
- **Primary Files:**
- `brainstorm-summary_[session_name].md` - Final comprehensive summary
- `_session-state.json` - Updated to completed status
## Example Usage
- **Generate summary for a session:**
`/planning/brainstorm/3-generate-brainstorm-summary --name="product-features"`
- **Generate by index:**
`/planning/brainstorm/3-generate-brainstorm-summary --name="1"`