- .git-commit-template.txt: 커밋 메시지 템플릿 추가 - .gitignore: OS 및 데이터베이스 관련 파일 무시 설정 추가 - .mcp.json: MCP 서버 설정 추가 - CLAUDE.md: SuperClaude 엔트리 포인트 문서 추가 - README.md: 프로젝트 템플릿 설명 추가 - .claude/COMMANDS.md: 명령어 실행 프레임워크 문서 추가 - .claude/FLAGS.md: 플래그 시스템 문서 추가 - .claude/MCP.md: MCP 서버 통합 문서 추가 - .claude/MODES.md: 운영 모드 문서 추가 - .claude/ORCHESTRATOR.md: 지능형 라우팅 시스템 문서 추가 - .claude/PERSONAS.md: 페르소나 시스템 문서 추가 - .claude/PRINCIPLES.md: 핵심 원칙 문서 추가 - .claude/RULES.md: 실행 가능한 규칙 문서 추가 - .claude/settings.json: 권한 설정 추가 - .claude/commands 디렉토리: 다양한 명령어 문서 추가 - .taskmaster/config.json: 기본 설정 파일 추가 - .taskmaster/docs 디렉토리: 문서 파일 추가 - .taskmaster/tasks/tasks.json: 기본 작업 파일 추가
321 lines
12 KiB
Markdown
321 lines
12 KiB
Markdown
---
|
|
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"` |