@botlearn/brainstorm 0.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +21 -0
- package/README.md +35 -0
- package/knowledge/anti-patterns.md +80 -0
- package/knowledge/best-practices.md +105 -0
- package/knowledge/domain.md +152 -0
- package/manifest.json +26 -0
- package/package.json +35 -0
- package/skill.md +44 -0
- package/strategies/main.md +101 -0
- package/tests/benchmark.json +476 -0
- package/tests/smoke.json +54 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2025 BotLearn
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
|
+
SOFTWARE.
|
package/README.md
ADDED
|
@@ -0,0 +1,35 @@
|
|
|
1
|
+
# @botlearn/brainstorm
|
|
2
|
+
|
|
3
|
+
> Multi-dimensional ideation and brainstorming with structured creativity frameworks, feasibility assessment, and idea clustering for OpenClaw Agent
|
|
4
|
+
|
|
5
|
+
## Installation
|
|
6
|
+
|
|
7
|
+
```bash
|
|
8
|
+
# via npm
|
|
9
|
+
npm install @botlearn/brainstorm
|
|
10
|
+
|
|
11
|
+
# via clawhub
|
|
12
|
+
clawhub install @botlearn/brainstorm
|
|
13
|
+
```
|
|
14
|
+
|
|
15
|
+
## Category
|
|
16
|
+
|
|
17
|
+
Creative Generation
|
|
18
|
+
|
|
19
|
+
## Dependencies
|
|
20
|
+
|
|
21
|
+
None
|
|
22
|
+
|
|
23
|
+
## Files
|
|
24
|
+
|
|
25
|
+
| File | Description |
|
|
26
|
+
|------|-------------|
|
|
27
|
+
| `manifest.json` | Skill metadata and configuration |
|
|
28
|
+
| `skill.md` | Role definition and activation rules |
|
|
29
|
+
| `knowledge/` | Domain knowledge documents |
|
|
30
|
+
| `strategies/` | Behavioral strategy definitions |
|
|
31
|
+
| `tests/` | Smoke and benchmark tests |
|
|
32
|
+
|
|
33
|
+
## License
|
|
34
|
+
|
|
35
|
+
MIT
|
|
@@ -0,0 +1,80 @@
|
|
|
1
|
+
---
|
|
2
|
+
domain: brainstorm
|
|
3
|
+
topic: anti-patterns
|
|
4
|
+
priority: medium
|
|
5
|
+
ttl: 90d
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
# Brainstorming — Anti-Patterns
|
|
9
|
+
|
|
10
|
+
## Generation Phase Anti-Patterns
|
|
11
|
+
|
|
12
|
+
### 1. Premature Evaluation
|
|
13
|
+
- **Problem**: Judging ideas during the divergent generation phase kills creative output. Statements like "That won't work because..." or "We tried that before" shut down exploration before ideas can evolve.
|
|
14
|
+
- **Symptoms**: Low idea count (< 10 ideas), all ideas are "safe" and incremental, participants self-censor
|
|
15
|
+
- **Fix**: Enforce strict phase separation. During generation, the only allowed response to any idea is "Yes, and..." (building on it) or silent capture. Defer ALL evaluation to the convergent phase.
|
|
16
|
+
|
|
17
|
+
### 2. Anchoring Bias
|
|
18
|
+
- **Problem**: The first idea mentioned dominates the session. Subsequent ideas cluster tightly around the anchor, producing variations on a theme instead of diverse solutions.
|
|
19
|
+
- **Symptoms**: Most ideas are minor variations of the first 1-2 ideas; lack of category diversity; ideas feel incremental
|
|
20
|
+
- **Fix**:
|
|
21
|
+
- Start with individual silent ideation (2-3 minutes) before any sharing
|
|
22
|
+
- Use multiple creativity frameworks (SCAMPER, Six Hats, TRIZ) sequentially to force different angles
|
|
23
|
+
- Explicitly prompt: "Now generate an idea that has nothing in common with everything so far"
|
|
24
|
+
|
|
25
|
+
### 3. Domain Tunnel Vision
|
|
26
|
+
- **Problem**: All ideas come from the same domain, industry, or disciplinary perspective. The brainstorm produces only "obvious" solutions that anyone in the field would suggest.
|
|
27
|
+
- **Symptoms**: Every idea uses the same technology, follows the same business model, or addresses only the most visible part of the problem
|
|
28
|
+
- **Fix**:
|
|
29
|
+
- Mandate cross-domain analogies: "How would [biology / game design / logistics / healthcare] solve this?"
|
|
30
|
+
- Apply the Random Entry technique from lateral thinking
|
|
31
|
+
- Include at least one "what if the opposite were true?" provocation per session
|
|
32
|
+
|
|
33
|
+
### 4. Groupthink / Convergent Drift
|
|
34
|
+
- **Problem**: The group unconsciously converges on a shared perspective, suppressing dissenting or unusual ideas. Social pressure favors agreement over diversity.
|
|
35
|
+
- **Symptoms**: Ideas are highly similar; no disagreement or tension; ideas feel "committee-approved"
|
|
36
|
+
- **Fix**:
|
|
37
|
+
- Assign a Devil's Advocate role (Red Hat / Black Hat thinker)
|
|
38
|
+
- Use brainwriting: participants write ideas independently before sharing
|
|
39
|
+
- Explicitly ask: "What idea would a critic of this approach suggest?"
|
|
40
|
+
|
|
41
|
+
### 5. Solution Jumping
|
|
42
|
+
- **Problem**: Moving directly to solutions without adequately understanding or reframing the problem. The wrong problem gets solved efficiently.
|
|
43
|
+
- **Symptoms**: Ideas address surface symptoms, not root causes; solutions don't match user needs; "obvious" solutions that ignore underlying complexity
|
|
44
|
+
- **Fix**:
|
|
45
|
+
- Spend 20% of session time on problem reframing BEFORE any solution generation
|
|
46
|
+
- Ask "Why?" five times (5 Whys) to reach root cause
|
|
47
|
+
- Restate the problem from at least 3 different stakeholder perspectives
|
|
48
|
+
|
|
49
|
+
## Evaluation Phase Anti-Patterns
|
|
50
|
+
|
|
51
|
+
### 6. Halo Effect on Ideas
|
|
52
|
+
- **Problem**: Ideas from authoritative sources or ideas presented eloquently receive higher scores regardless of actual merit. Conversely, poorly articulated but strong ideas get dismissed.
|
|
53
|
+
- **Fix**: Evaluate ideas anonymously when possible. Score against defined criteria (feasibility matrix) rather than gut feeling. Rate each dimension separately before computing composite scores.
|
|
54
|
+
|
|
55
|
+
### 7. Survivorship Bias in Clustering
|
|
56
|
+
- **Problem**: Only the loudest or most repeated ideas survive to the clustering phase. Quiet, novel, or singular ideas get lost because they don't fit obvious patterns.
|
|
57
|
+
- **Fix**: Before clustering, explicitly review all "orphan" ideas (those that don't obviously fit any group). Orphans often represent the most innovative directions. Create a dedicated "Wild Cards" cluster.
|
|
58
|
+
|
|
59
|
+
### 8. Feasibility-Only Filtering
|
|
60
|
+
- **Problem**: Filtering ideas solely on feasibility eliminates high-impact, transformative ideas that require more effort but could be game-changing.
|
|
61
|
+
- **Fix**: Use a 2x2 matrix: Impact vs. Feasibility. Preserve "High Impact / Low Feasibility" ideas in a "Moonshot" category for future consideration. Never discard based on a single dimension.
|
|
62
|
+
|
|
63
|
+
## Output Anti-Patterns
|
|
64
|
+
|
|
65
|
+
### 9. Flat List Delivery
|
|
66
|
+
- **Problem**: Presenting brainstorm results as an unstructured, unprioritized list of ideas. The recipient cannot act on 30+ undifferentiated ideas.
|
|
67
|
+
- **Symptoms**: No clustering, no ranking, no feasibility signals; all ideas appear equally important
|
|
68
|
+
- **Fix**: Always deliver ideas in clustered, scored, and ranked format. Lead with the top 3-5 ideas from the highest-priority cluster. Include feasibility ratings and a clear "next steps" recommendation for each top idea.
|
|
69
|
+
|
|
70
|
+
### 10. Missing Actionability
|
|
71
|
+
- **Problem**: Ideas are described at too high a level to be actionable. "Use AI" or "Improve the user experience" are directions, not ideas.
|
|
72
|
+
- **Fix**: Each idea should pass the specificity test: Could someone start working on this within a week? Include: what it is, who it's for, what changes, and a rough first step. Minimum: one concrete sentence beyond the headline.
|
|
73
|
+
|
|
74
|
+
### 11. No Novelty Signal
|
|
75
|
+
- **Problem**: Failing to flag which ideas are genuinely novel versus well-known approaches. The brainstorm output looks creative but actually contains only conventional solutions.
|
|
76
|
+
- **Fix**: Tag each idea as: "Novel" (not commonly applied in this domain), "Adapted" (borrowed from another domain), or "Standard" (well-known in this domain). Aim for at least 30% Novel or Adapted ideas.
|
|
77
|
+
|
|
78
|
+
### 12. Ignoring Constraints
|
|
79
|
+
- **Problem**: Generating ideas that completely disregard the stated constraints (budget, timeline, team size, technology stack). Beautiful ideas that are impossible to execute given the real-world situation.
|
|
80
|
+
- **Fix**: Restate constraints at the start of the convergent phase. During feasibility scoring, explicitly check each idea against the constraint list. Flag ideas that violate hard constraints but may be valuable if constraints change.
|
|
@@ -0,0 +1,105 @@
|
|
|
1
|
+
---
|
|
2
|
+
domain: brainstorm
|
|
3
|
+
topic: ideation-quality-and-process
|
|
4
|
+
priority: high
|
|
5
|
+
ttl: 90d
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
# Brainstorming — Best Practices
|
|
9
|
+
|
|
10
|
+
## Diverge-Converge Discipline
|
|
11
|
+
|
|
12
|
+
### The Double Diamond Model
|
|
13
|
+
Effective brainstorming follows a strict two-phase rhythm:
|
|
14
|
+
|
|
15
|
+
1. **Diverge (Diamond 1 — Explore)**: Generate as many ideas as possible without judgment
|
|
16
|
+
- Quantity over quality — aim for 3x the ideas you think you need
|
|
17
|
+
- Build on others' ideas ("Yes, and..." not "Yes, but...")
|
|
18
|
+
- Welcome wild, impractical, and absurd ideas — they seed practical derivatives
|
|
19
|
+
- No evaluation, no criticism, no feasibility checks during this phase
|
|
20
|
+
|
|
21
|
+
2. **Converge (Diamond 2 — Evaluate)**: Filter, assess, and prioritize
|
|
22
|
+
- Apply feasibility criteria systematically
|
|
23
|
+
- Cluster related ideas into themes
|
|
24
|
+
- Score and rank using defined criteria
|
|
25
|
+
- Kill ideas that fail viability checks — no emotional attachment
|
|
26
|
+
|
|
27
|
+
### Phase Separation Rules
|
|
28
|
+
- NEVER mix divergent and convergent thinking in the same step
|
|
29
|
+
- Signal phase transitions explicitly: "Switching from generation to evaluation mode"
|
|
30
|
+
- If evaluation thoughts arise during divergence, note them separately for later
|
|
31
|
+
- Minimum divergent output: 15+ raw ideas before switching to convergence
|
|
32
|
+
|
|
33
|
+
## Cross-Domain Ideation
|
|
34
|
+
|
|
35
|
+
### Analogical Reasoning Protocol
|
|
36
|
+
1. **Abstract the problem**: Strip domain-specific details to reveal the structural pattern
|
|
37
|
+
- Example: "How do we reduce customer wait times?" → "How do systems manage queue throughput?"
|
|
38
|
+
2. **Identify analog domains**: Find 3+ domains that face structurally similar challenges
|
|
39
|
+
- Queue throughput analogies: airport security, hospital triage, packet routing, restaurant seating
|
|
40
|
+
3. **Extract principles**: What solution pattern does each analog domain use?
|
|
41
|
+
- Airport: parallel processing lanes; Hospital: severity-based prioritization; Networking: load balancing
|
|
42
|
+
4. **Transfer and adapt**: Apply extracted principles back to the original domain
|
|
43
|
+
- Parallel processing → multiple service channels; Severity-based → VIP fast-track; Load balancing → dynamic routing
|
|
44
|
+
|
|
45
|
+
### Cross-Pollination Sources
|
|
46
|
+
| Source Domain | Yields Ideas For |
|
|
47
|
+
|--------------|-----------------|
|
|
48
|
+
| Biology / Nature | Resilience, adaptation, self-organization, swarm behavior |
|
|
49
|
+
| Architecture | Modular design, scalability, user flow, spatial efficiency |
|
|
50
|
+
| Game Design | Engagement, motivation, feedback loops, progressive difficulty |
|
|
51
|
+
| Supply Chain | Efficiency, logistics, just-in-time, bottleneck elimination |
|
|
52
|
+
| Psychology | Behavior change, habit formation, cognitive load, persuasion |
|
|
53
|
+
| Music / Art | Rhythm, composition, contrast, emotional resonance |
|
|
54
|
+
|
|
55
|
+
## Feasibility Matrix
|
|
56
|
+
|
|
57
|
+
### Scoring Dimensions
|
|
58
|
+
|
|
59
|
+
Each idea should be assessed on four axes using a 1-5 scale:
|
|
60
|
+
|
|
61
|
+
| Dimension | 1 (Low) | 3 (Medium) | 5 (High) |
|
|
62
|
+
|-----------|---------|-----------|----------|
|
|
63
|
+
| **Technical Viability** | Requires unproven technology or fundamental research | Needs significant engineering but uses known approaches | Can be built with existing tools and proven patterns |
|
|
64
|
+
| **Resource Requirements** | Massive team, budget, and infrastructure needed | Moderate investment; achievable with dedicated effort | Lean implementation; small team, low cost |
|
|
65
|
+
| **Time-to-Implement** | 12+ months to first viable version | 3-6 months to MVP | Days to weeks for prototype |
|
|
66
|
+
| **Impact Potential** | Marginal improvement over status quo | Meaningful improvement for a segment of users | Transformative change for the target audience |
|
|
67
|
+
|
|
68
|
+
### Composite Feasibility Score
|
|
69
|
+
- **Viable** (score 14-20): Proceed to detailed planning
|
|
70
|
+
- **Promising** (score 9-13): Worth exploring with further research or reduced scope
|
|
71
|
+
- **Speculative** (score 4-8): Park for future consideration or combine with other ideas
|
|
72
|
+
|
|
73
|
+
### Weighted Scoring for Prioritization
|
|
74
|
+
When priorities differ by context, adjust weights:
|
|
75
|
+
- **Startup / MVP context**: Time-to-Implement (35%), Impact (30%), Resources (20%), Technical (15%)
|
|
76
|
+
- **Enterprise / R&D context**: Impact (35%), Technical (30%), Resources (20%), Time (15%)
|
|
77
|
+
- **Innovation lab context**: Impact (40%), Technical (25%), Time (20%), Resources (15%)
|
|
78
|
+
|
|
79
|
+
## Idea Volume & Quality Targets
|
|
80
|
+
|
|
81
|
+
### The 3x Rule
|
|
82
|
+
- Structured brainstorming should produce at least 3x the ideas compared to unstructured free-association
|
|
83
|
+
- Unstructured session on a typical problem: ~8-12 ideas
|
|
84
|
+
- Structured session target: 25-40 ideas minimum
|
|
85
|
+
|
|
86
|
+
### Viability Rate
|
|
87
|
+
- Target: 40%+ of generated ideas should score "Viable" or "Promising" on the feasibility matrix
|
|
88
|
+
- Below 30% viability: generation was too unconstrained — tighten problem framing
|
|
89
|
+
- Above 70% viability: generation was too conservative — push for wilder ideas
|
|
90
|
+
|
|
91
|
+
## Idea Clustering
|
|
92
|
+
|
|
93
|
+
### Affinity Grouping Process
|
|
94
|
+
1. Spread all ideas visually (list or mind-map form)
|
|
95
|
+
2. Identify natural themes or patterns — group related ideas
|
|
96
|
+
3. Name each cluster with a descriptive theme label
|
|
97
|
+
4. Identify "bridge ideas" that connect two or more clusters
|
|
98
|
+
5. Look for underrepresented clusters — gaps may signal unexplored opportunities
|
|
99
|
+
|
|
100
|
+
### Cluster Prioritization
|
|
101
|
+
Rank clusters (not just individual ideas) by:
|
|
102
|
+
- **Cluster density**: More ideas in a cluster = stronger signal of opportunity
|
|
103
|
+
- **Peak idea quality**: Best single idea in the cluster
|
|
104
|
+
- **Strategic alignment**: Fit with stated goals and constraints
|
|
105
|
+
- **Synergy potential**: Can ideas within the cluster reinforce each other?
|
|
@@ -0,0 +1,152 @@
|
|
|
1
|
+
---
|
|
2
|
+
domain: brainstorm
|
|
3
|
+
topic: creativity-frameworks-and-ideation-methods
|
|
4
|
+
priority: high
|
|
5
|
+
ttl: 90d
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
# Brainstorming — Creativity Frameworks & Ideation Methods
|
|
9
|
+
|
|
10
|
+
## SCAMPER Framework
|
|
11
|
+
|
|
12
|
+
SCAMPER is a structured checklist for generating ideas by transforming existing concepts along seven dimensions.
|
|
13
|
+
|
|
14
|
+
### S — Substitute
|
|
15
|
+
- What components, materials, or processes can be replaced?
|
|
16
|
+
- Can you substitute a different person, place, time, or approach?
|
|
17
|
+
- Example: Substitute physical meetings with async video → asynchronous standup tools
|
|
18
|
+
|
|
19
|
+
### C — Combine
|
|
20
|
+
- What ideas, features, or functions can be merged?
|
|
21
|
+
- Can you combine purposes, audiences, or technologies?
|
|
22
|
+
- Example: Combine fitness tracking + social media → Strava's activity feed
|
|
23
|
+
|
|
24
|
+
### A — Adapt
|
|
25
|
+
- What can be borrowed from another domain or context?
|
|
26
|
+
- How can an existing solution be adapted to this problem?
|
|
27
|
+
- Example: Adapt assembly-line thinking to software → CI/CD pipelines
|
|
28
|
+
|
|
29
|
+
### M — Modify (Magnify / Minimize)
|
|
30
|
+
- What can be made larger, stronger, more frequent, or exaggerated?
|
|
31
|
+
- What can be made smaller, lighter, simpler, or less frequent?
|
|
32
|
+
- Example: Magnify personalization → hyper-personalized learning paths
|
|
33
|
+
|
|
34
|
+
### P — Put to Another Use
|
|
35
|
+
- Can the existing product/process serve a different purpose?
|
|
36
|
+
- Can waste or by-products be repurposed?
|
|
37
|
+
- Example: Put shipping containers to another use → modular housing
|
|
38
|
+
|
|
39
|
+
### E — Eliminate
|
|
40
|
+
- What can be removed without losing core value?
|
|
41
|
+
- What steps, features, or constraints are unnecessary?
|
|
42
|
+
- Example: Eliminate the middleman → direct-to-consumer brands
|
|
43
|
+
|
|
44
|
+
### R — Reverse / Rearrange
|
|
45
|
+
- What happens if you reverse the process or sequence?
|
|
46
|
+
- Can components be rearranged for a different outcome?
|
|
47
|
+
- Example: Reverse the sales model → customer sets the price (Priceline)
|
|
48
|
+
|
|
49
|
+
## Six Thinking Hats (de Bono)
|
|
50
|
+
|
|
51
|
+
Each hat represents a distinct thinking mode. Cycling through all six ensures comprehensive idea exploration.
|
|
52
|
+
|
|
53
|
+
### White Hat — Facts & Data
|
|
54
|
+
- What information do we have? What is missing?
|
|
55
|
+
- Focus on objective data, numbers, and known constraints
|
|
56
|
+
- Use to establish the factual foundation before ideation
|
|
57
|
+
|
|
58
|
+
### Red Hat — Emotions & Intuition
|
|
59
|
+
- What does your gut feeling say? What feels right or wrong?
|
|
60
|
+
- Capture emotional reactions without needing justification
|
|
61
|
+
- Use to surface hunches, excitement, or discomfort about ideas
|
|
62
|
+
|
|
63
|
+
### Black Hat — Caution & Risk
|
|
64
|
+
- What could go wrong? What are the risks and downsides?
|
|
65
|
+
- Critical judgment, devil's advocate perspective
|
|
66
|
+
- Use ONLY in convergent phase — never during idea generation
|
|
67
|
+
|
|
68
|
+
### Yellow Hat — Optimism & Value
|
|
69
|
+
- What are the benefits? Why could this work?
|
|
70
|
+
- Focus on best-case scenarios and value propositions
|
|
71
|
+
- Use to build on nascent ideas and find hidden strengths
|
|
72
|
+
|
|
73
|
+
### Green Hat — Creativity & Alternatives
|
|
74
|
+
- What new ideas are possible? What if we tried something different?
|
|
75
|
+
- Provocative thinking, lateral connections, wild ideas welcome
|
|
76
|
+
- Use as the primary hat during divergent generation
|
|
77
|
+
|
|
78
|
+
### Blue Hat — Process & Meta-thinking
|
|
79
|
+
- Where are we in the process? What hat should we use next?
|
|
80
|
+
- Controls the thinking process, sets agenda, summarizes
|
|
81
|
+
- Use to orchestrate transitions between divergent and convergent phases
|
|
82
|
+
|
|
83
|
+
## TRIZ (Theory of Inventive Problem Solving)
|
|
84
|
+
|
|
85
|
+
TRIZ provides systematic patterns for resolving contradictions in problem-solving.
|
|
86
|
+
|
|
87
|
+
### 40 Inventive Principles (Key Subset)
|
|
88
|
+
|
|
89
|
+
| # | Principle | Description | Ideation Prompt |
|
|
90
|
+
|---|-----------|-------------|-----------------|
|
|
91
|
+
| 1 | Segmentation | Divide an object or system into parts | "What if we break this into independent modules?" |
|
|
92
|
+
| 2 | Taking Out / Extraction | Remove a problematic part or property | "What if we isolate the essential function from the rest?" |
|
|
93
|
+
| 5 | Merging | Combine identical or similar objects/operations | "What if we merge these parallel processes?" |
|
|
94
|
+
| 10 | Preliminary Action | Perform required changes in advance | "What if we pre-process or pre-position resources?" |
|
|
95
|
+
| 13 | The Other Way Round | Invert the action or process | "What if we reverse who does what, or the sequence?" |
|
|
96
|
+
| 15 | Dynamization | Make a rigid system flexible or adaptive | "What if this adjusted in real-time based on context?" |
|
|
97
|
+
| 17 | Another Dimension | Move to a different dimension (1D→2D→3D, or add a layer) | "What if we add a new axis or layer to this?" |
|
|
98
|
+
| 22 | Blessing in Disguise | Turn a harmful factor into a benefit | "What if this problem is actually an opportunity?" |
|
|
99
|
+
| 25 | Self-Service | Make the object serve or maintain itself | "What if users contribute to the solution automatically?" |
|
|
100
|
+
| 35 | Parameter Change | Change physical or logical state/parameters | "What if we change the frequency, format, or medium?" |
|
|
101
|
+
|
|
102
|
+
### Contradiction Matrix
|
|
103
|
+
- Identify the **improving parameter** (what you want to enhance)
|
|
104
|
+
- Identify the **worsening parameter** (what degrades when you improve)
|
|
105
|
+
- Look up suggested inventive principles from the matrix
|
|
106
|
+
- Example: Improving speed (parameter 9) worsens reliability (parameter 27) → Apply principles #10 (Preliminary Action), #28 (Mechanical Substitution), #35 (Parameter Change)
|
|
107
|
+
|
|
108
|
+
## Lateral Thinking Techniques
|
|
109
|
+
|
|
110
|
+
### Random Entry
|
|
111
|
+
- Pick a random word, image, or concept and force connections to the problem
|
|
112
|
+
- The randomness breaks established thinking patterns
|
|
113
|
+
- Process: Random stimulus → extract attributes → force-fit to problem → generate ideas
|
|
114
|
+
|
|
115
|
+
### Challenge Assumptions
|
|
116
|
+
- List all assumptions about the problem (explicit and implicit)
|
|
117
|
+
- Systematically challenge each: "What if this assumption were false?"
|
|
118
|
+
- Generate ideas that operate in the assumption-free space
|
|
119
|
+
- Example: "What if customers don't need to own the product?" → subscription/rental models
|
|
120
|
+
|
|
121
|
+
### Analogy Transfer
|
|
122
|
+
- Find a domain that has solved a structurally similar problem
|
|
123
|
+
- Extract the solution principle (abstracted from domain specifics)
|
|
124
|
+
- Apply the principle to the target domain
|
|
125
|
+
- Example: How does nature handle load balancing? → ant colony optimization → distributed computing algorithms
|
|
126
|
+
|
|
127
|
+
### Provocation (PO)
|
|
128
|
+
- Make a deliberately provocative, impossible, or absurd statement
|
|
129
|
+
- Use the provocation as a stepping stone to practical ideas
|
|
130
|
+
- Format: "PO: [provocative statement]" → "Movement: [what's interesting about this?]" → "Idea: [practical derivative]"
|
|
131
|
+
- Example: "PO: The product repairs itself" → Movement: self-diagnosing systems → Idea: automated error detection and self-healing code
|
|
132
|
+
|
|
133
|
+
## Innovation Patterns
|
|
134
|
+
|
|
135
|
+
### Technology Transfer Patterns
|
|
136
|
+
- **Digital twin**: Create a virtual replica of a physical process
|
|
137
|
+
- **Platform shift**: Move from product to platform, enabling ecosystem effects
|
|
138
|
+
- **Automation cascade**: Automate one step, revealing the next bottleneck to automate
|
|
139
|
+
- **Unbundling/rebundling**: Break a monolithic offering into components, then recombine differently
|
|
140
|
+
|
|
141
|
+
### Business Model Innovation Patterns
|
|
142
|
+
- **Freemium**: Free basic tier funded by premium conversions
|
|
143
|
+
- **Marketplace**: Connect supply and demand, take a transaction fee
|
|
144
|
+
- **Subscription**: Recurring revenue from ongoing access
|
|
145
|
+
- **Razor-and-blades**: Low-cost entry product, high-margin consumables
|
|
146
|
+
- **Data monetization**: Generate value from data produced by the core product
|
|
147
|
+
|
|
148
|
+
### User Experience Innovation Patterns
|
|
149
|
+
- **Reduce friction**: Remove steps between intent and outcome
|
|
150
|
+
- **Progressive disclosure**: Show complexity only when the user is ready
|
|
151
|
+
- **Anticipatory design**: Predict and pre-fill user needs
|
|
152
|
+
- **Social proof integration**: Use community behavior to guide individual decisions
|
package/manifest.json
ADDED
|
@@ -0,0 +1,26 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "@botlearn/brainstorm",
|
|
3
|
+
"version": "0.1.0",
|
|
4
|
+
"description": "Multi-dimensional ideation and brainstorming with structured creativity frameworks, feasibility assessment, and idea clustering for OpenClaw Agent",
|
|
5
|
+
"category": "creative-generation",
|
|
6
|
+
"author": "BotLearn",
|
|
7
|
+
"benchmarkDimension": "creative-generation",
|
|
8
|
+
"expectedImprovement": 40,
|
|
9
|
+
"dependencies": {},
|
|
10
|
+
"compatibility": {
|
|
11
|
+
"openclaw": ">=0.5.0"
|
|
12
|
+
},
|
|
13
|
+
"files": {
|
|
14
|
+
"skill": "skill.md",
|
|
15
|
+
"knowledge": [
|
|
16
|
+
"knowledge/domain.md",
|
|
17
|
+
"knowledge/best-practices.md",
|
|
18
|
+
"knowledge/anti-patterns.md"
|
|
19
|
+
],
|
|
20
|
+
"strategies": [
|
|
21
|
+
"strategies/main.md"
|
|
22
|
+
],
|
|
23
|
+
"smokeTest": "tests/smoke.json",
|
|
24
|
+
"benchmark": "tests/benchmark.json"
|
|
25
|
+
}
|
|
26
|
+
}
|
package/package.json
ADDED
|
@@ -0,0 +1,35 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "@botlearn/brainstorm",
|
|
3
|
+
"version": "0.1.0",
|
|
4
|
+
"description": "Multi-dimensional ideation and brainstorming with structured creativity frameworks, feasibility assessment, and idea clustering for OpenClaw Agent",
|
|
5
|
+
"type": "module",
|
|
6
|
+
"main": "manifest.json",
|
|
7
|
+
"files": [
|
|
8
|
+
"manifest.json",
|
|
9
|
+
"skill.md",
|
|
10
|
+
"knowledge/",
|
|
11
|
+
"strategies/",
|
|
12
|
+
"tests/",
|
|
13
|
+
"README.md"
|
|
14
|
+
],
|
|
15
|
+
"keywords": [
|
|
16
|
+
"botlearn",
|
|
17
|
+
"openclaw",
|
|
18
|
+
"skill",
|
|
19
|
+
"creative-generation"
|
|
20
|
+
],
|
|
21
|
+
"author": "BotLearn",
|
|
22
|
+
"license": "MIT",
|
|
23
|
+
"repository": {
|
|
24
|
+
"type": "git",
|
|
25
|
+
"url": "https://github.com/readai-team/botlearn-awesome-skills.git",
|
|
26
|
+
"directory": "packages/skills/brainstorm"
|
|
27
|
+
},
|
|
28
|
+
"homepage": "https://github.com/readai-team/botlearn-awesome-skills/tree/main/packages/skills/brainstorm",
|
|
29
|
+
"bugs": {
|
|
30
|
+
"url": "https://github.com/readai-team/botlearn-awesome-skills/issues"
|
|
31
|
+
},
|
|
32
|
+
"publishConfig": {
|
|
33
|
+
"access": "public"
|
|
34
|
+
}
|
|
35
|
+
}
|
package/skill.md
ADDED
|
@@ -0,0 +1,44 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: brainstorm
|
|
3
|
+
role: Creative Ideation Specialist
|
|
4
|
+
version: 1.0.0
|
|
5
|
+
triggers:
|
|
6
|
+
- "brainstorm"
|
|
7
|
+
- "generate ideas"
|
|
8
|
+
- "ideation"
|
|
9
|
+
- "think of ways"
|
|
10
|
+
- "creative solutions"
|
|
11
|
+
- "come up with ideas"
|
|
12
|
+
- "brainstorming session"
|
|
13
|
+
---
|
|
14
|
+
|
|
15
|
+
# Role
|
|
16
|
+
|
|
17
|
+
You are a Creative Ideation Specialist. When activated, you facilitate structured brainstorming sessions that produce multi-dimensional ideas across diverse categories, assess each idea for feasibility, and deliver clustered, prioritized output. Your goal is to triple the number of ideas generated compared to unstructured ideation while ensuring 40%+ of ideas are viable.
|
|
18
|
+
|
|
19
|
+
# Capabilities
|
|
20
|
+
|
|
21
|
+
1. Reframe problems using multiple lenses (user-centric, systemic, contrarian, analogical) to unlock non-obvious solution spaces
|
|
22
|
+
2. Apply structured creativity frameworks (SCAMPER, Six Thinking Hats, TRIZ, lateral thinking) to generate ideas across multiple dimensions
|
|
23
|
+
3. Produce cross-domain idea transfer by mapping patterns from unrelated industries and disciplines onto the target problem
|
|
24
|
+
4. Assess each idea along a feasibility matrix covering technical viability, resource requirements, time-to-implement, and impact potential
|
|
25
|
+
5. Cluster related ideas into coherent themes and prioritize clusters using weighted scoring across novelty, feasibility, and strategic fit
|
|
26
|
+
|
|
27
|
+
# Constraints
|
|
28
|
+
|
|
29
|
+
1. Never evaluate ideas during the divergent generation phase — defer all judgment to the convergent assessment phase
|
|
30
|
+
2. Never anchor the session on a single framework — always apply at least two complementary creativity methods
|
|
31
|
+
3. Never limit ideas to the obvious domain — always include at least one cross-domain or analogical transfer perspective
|
|
32
|
+
4. Never present ideas as a flat list — always cluster, score, and rank for actionability
|
|
33
|
+
5. Never skip feasibility assessment — every idea must carry at least a high/medium/low viability signal
|
|
34
|
+
6. Always separate divergent (generation) from convergent (evaluation) thinking phases
|
|
35
|
+
|
|
36
|
+
# Activation
|
|
37
|
+
|
|
38
|
+
WHEN the user requests brainstorming, ideation, or creative solution generation:
|
|
39
|
+
1. Analyze the problem space and identify scope, constraints, and desired outcomes
|
|
40
|
+
2. Reframe the problem through multiple lenses following strategies/main.md Step 1
|
|
41
|
+
3. Apply creativity frameworks from knowledge/domain.md to generate ideas across dimensions
|
|
42
|
+
4. Follow diverge-then-converge discipline from knowledge/best-practices.md
|
|
43
|
+
5. Avoid anti-patterns identified in knowledge/anti-patterns.md (premature evaluation, anchoring, domain tunnel vision)
|
|
44
|
+
6. Assess feasibility, cluster ideas, and output a prioritized, actionable idea portfolio
|
|
@@ -0,0 +1,101 @@
|
|
|
1
|
+
---
|
|
2
|
+
strategy: brainstorm
|
|
3
|
+
version: 1.0.0
|
|
4
|
+
steps: 6
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Brainstorming Strategy
|
|
8
|
+
|
|
9
|
+
## Step 1: Problem Reframing
|
|
10
|
+
- Parse the user's request to identify: **problem statement**, **scope**, **constraints**, **desired outcomes**, **target audience**
|
|
11
|
+
- Reframe the problem through at least 3 lenses:
|
|
12
|
+
- **User-centric**: What is the core user pain or unmet need?
|
|
13
|
+
- **Systemic**: What are the upstream causes and downstream effects?
|
|
14
|
+
- **Contrarian**: What if the opposite of the obvious approach were tried?
|
|
15
|
+
- **Analogical**: What does this problem resemble in a completely different domain?
|
|
16
|
+
- IF the problem is vague THEN ask one clarifying question about scope or constraints before proceeding
|
|
17
|
+
- IF the problem is well-defined THEN note any implicit assumptions and flag them for challenge
|
|
18
|
+
- OUTPUT: 2-4 reframed problem statements that open different solution spaces
|
|
19
|
+
|
|
20
|
+
## Step 2: Multi-Dimensional Divergence
|
|
21
|
+
- SELECT at least 2 creativity frameworks based on problem type:
|
|
22
|
+
- Incremental improvement → SCAMPER (systematic transformation of existing solution)
|
|
23
|
+
- Complex trade-offs → TRIZ (contradiction resolution via inventive principles)
|
|
24
|
+
- Exploratory / open-ended → Six Thinking Hats (rotating perspective lenses)
|
|
25
|
+
- Stuck / obvious solutions only → Lateral Thinking (random entry, provocation, assumption challenge)
|
|
26
|
+
- FOR EACH selected framework:
|
|
27
|
+
- Apply the framework systematically to each reframed problem statement from Step 1
|
|
28
|
+
- Generate 5-10 raw ideas per framework application
|
|
29
|
+
- Capture ALL ideas without filtering — no evaluation in this step
|
|
30
|
+
- APPLY cross-domain transfer from knowledge/best-practices.md:
|
|
31
|
+
- Identify 2-3 analog domains using analogical reasoning protocol
|
|
32
|
+
- Extract solution principles from each analog domain
|
|
33
|
+
- Force-fit at least 3 cross-domain ideas onto the target problem
|
|
34
|
+
- TARGET: Minimum 20 raw ideas across all frameworks and dimensions
|
|
35
|
+
|
|
36
|
+
## Step 3: Idea Generation & Expansion
|
|
37
|
+
- Review the raw idea pool from Step 2
|
|
38
|
+
- FOR EACH promising direction, expand with specificity:
|
|
39
|
+
- What exactly would this look like in practice?
|
|
40
|
+
- Who specifically would it serve and how?
|
|
41
|
+
- What would the first concrete step be?
|
|
42
|
+
- APPLY idea building techniques:
|
|
43
|
+
- **Combination**: Merge 2-3 complementary ideas into hybrid concepts
|
|
44
|
+
- **Escalation**: Take a modest idea and push it to its extreme — what's the "10x version"?
|
|
45
|
+
- **Inversion**: For each strong idea, generate its opposite — does the inverse also work?
|
|
46
|
+
- VERIFY against anti-patterns from knowledge/anti-patterns.md:
|
|
47
|
+
- Are ideas diverse across categories (not anchored)?
|
|
48
|
+
- Are there cross-domain ideas present (no tunnel vision)?
|
|
49
|
+
- Are ideas specific enough to be actionable (no vague directions)?
|
|
50
|
+
- TARGET: 25-40 expanded, specific ideas
|
|
51
|
+
|
|
52
|
+
## Step 4: Feasibility Assessment
|
|
53
|
+
- SWITCH to convergent thinking mode — signal the transition explicitly
|
|
54
|
+
- FOR EACH idea, score on 4 dimensions (1-5 scale) from knowledge/best-practices.md:
|
|
55
|
+
- **Technical Viability** (1-5): Can this be built with known approaches?
|
|
56
|
+
- **Resource Requirements** (1-5): What investment of people, money, and infrastructure?
|
|
57
|
+
- **Time-to-Implement** (1-5): How long to a working prototype or MVP?
|
|
58
|
+
- **Impact Potential** (1-5): How significant is the change for the target audience?
|
|
59
|
+
- COMPUTE composite feasibility score (sum of 4 dimensions, max 20):
|
|
60
|
+
- Viable (14-20): Ready for detailed planning
|
|
61
|
+
- Promising (9-13): Worth exploring further or with reduced scope
|
|
62
|
+
- Speculative (4-8): Park for future or combine with stronger ideas
|
|
63
|
+
- TAG novelty level: "Novel", "Adapted", or "Standard"
|
|
64
|
+
- IF user provided specific constraints THEN check each idea against constraint list
|
|
65
|
+
- TARGET: 40%+ of ideas scoring "Viable" or "Promising"
|
|
66
|
+
|
|
67
|
+
## Step 5: Clustering & Theme Identification
|
|
68
|
+
- GROUP ideas by natural affinity:
|
|
69
|
+
- Same target audience or user segment
|
|
70
|
+
- Same underlying mechanism or technology
|
|
71
|
+
- Same strategic direction or business model
|
|
72
|
+
- Same type of innovation (incremental / adjacent / transformative)
|
|
73
|
+
- NAME each cluster with a descriptive theme label
|
|
74
|
+
- IDENTIFY "bridge ideas" that connect multiple clusters
|
|
75
|
+
- IDENTIFY "orphan ideas" that don't fit any cluster — create a "Wild Cards" group
|
|
76
|
+
- Review orphans specifically: these often contain the most novel insights
|
|
77
|
+
- RANK clusters by:
|
|
78
|
+
- **Cluster density**: Number of ideas (more = stronger signal)
|
|
79
|
+
- **Peak quality**: Highest-scoring individual idea in the cluster
|
|
80
|
+
- **Strategic alignment**: Fit with the user's stated goals and constraints
|
|
81
|
+
- **Synergy potential**: Can ideas within the cluster reinforce each other?
|
|
82
|
+
|
|
83
|
+
## Step 6: Prioritization & Output
|
|
84
|
+
- Present results in structured format:
|
|
85
|
+
- **Executive Summary**: Top 3-5 recommended ideas with one-sentence descriptions
|
|
86
|
+
- **Cluster Map**: All clusters ranked by priority, with theme labels and idea counts
|
|
87
|
+
- **Top Ideas Detail**: For each top idea, provide:
|
|
88
|
+
- **Idea name** and one-paragraph description
|
|
89
|
+
- **Feasibility scores** (Technical / Resources / Time / Impact)
|
|
90
|
+
- **Novelty tag** (Novel / Adapted / Standard)
|
|
91
|
+
- **First concrete step** to explore or prototype
|
|
92
|
+
- **Key risk** and mitigation approach
|
|
93
|
+
- **Full Idea Portfolio**: Complete list organized by cluster, with scores
|
|
94
|
+
- **Wild Cards**: Unconventional ideas worth monitoring
|
|
95
|
+
- SELF-CHECK:
|
|
96
|
+
- Did we generate 3x more ideas than a naive list would produce?
|
|
97
|
+
- Are 40%+ of ideas rated Viable or Promising?
|
|
98
|
+
- Are ideas spread across 3+ distinct clusters (not anchored to one theme)?
|
|
99
|
+
- Does every top idea have a concrete first step?
|
|
100
|
+
- Are cross-domain and novel ideas represented in the top recommendations?
|
|
101
|
+
- IF any check fails THEN loop back to Step 2 with additional frameworks or cross-domain prompts
|
|
@@ -0,0 +1,476 @@
|
|
|
1
|
+
{
|
|
2
|
+
"version": "0.0.1",
|
|
3
|
+
"dimension": "creative-generation",
|
|
4
|
+
"tasks": [
|
|
5
|
+
{
|
|
6
|
+
"id": "bench-easy-01",
|
|
7
|
+
"difficulty": "easy",
|
|
8
|
+
"description": "Generate ideas for a simple product improvement",
|
|
9
|
+
"input": "Brainstorm ways to make a coffee shop's ordering process faster and more enjoyable for customers.",
|
|
10
|
+
"rubric": [
|
|
11
|
+
{
|
|
12
|
+
"criterion": "Idea Volume",
|
|
13
|
+
"weight": 0.3,
|
|
14
|
+
"scoring": {
|
|
15
|
+
"5": "15+ ideas generated across technology, service design, layout, and customer experience dimensions",
|
|
16
|
+
"3": "8-14 ideas mostly focused on one or two dimensions",
|
|
17
|
+
"1": "Fewer than 8 ideas",
|
|
18
|
+
"0": "Fewer than 3 ideas"
|
|
19
|
+
}
|
|
20
|
+
},
|
|
21
|
+
{
|
|
22
|
+
"criterion": "Framework Usage",
|
|
23
|
+
"weight": 0.3,
|
|
24
|
+
"scoring": {
|
|
25
|
+
"5": "Applies at least 2 creativity frameworks visibly; ideas clearly derive from structured methods",
|
|
26
|
+
"3": "One framework applied; some structure visible",
|
|
27
|
+
"1": "No framework; free association only",
|
|
28
|
+
"0": "No structured approach"
|
|
29
|
+
}
|
|
30
|
+
},
|
|
31
|
+
{
|
|
32
|
+
"criterion": "Actionability",
|
|
33
|
+
"weight": 0.4,
|
|
34
|
+
"scoring": {
|
|
35
|
+
"5": "Each idea includes what it is, who benefits, and a first step; feasibility rated; ideas are clustered",
|
|
36
|
+
"3": "Ideas described at headline level with some feasibility notes",
|
|
37
|
+
"1": "Vague one-line ideas without detail",
|
|
38
|
+
"0": "Unusable output"
|
|
39
|
+
}
|
|
40
|
+
}
|
|
41
|
+
],
|
|
42
|
+
"expectedScoreWithout": 35,
|
|
43
|
+
"expectedScoreWith": 75
|
|
44
|
+
},
|
|
45
|
+
{
|
|
46
|
+
"id": "bench-easy-02",
|
|
47
|
+
"difficulty": "easy",
|
|
48
|
+
"description": "Brainstorm names and concepts for a new product",
|
|
49
|
+
"input": "Generate creative ideas for a mobile app that helps people build better daily habits. I need both feature ideas and unique selling points.",
|
|
50
|
+
"rubric": [
|
|
51
|
+
{
|
|
52
|
+
"criterion": "Idea Diversity",
|
|
53
|
+
"weight": 0.35,
|
|
54
|
+
"scoring": {
|
|
55
|
+
"5": "Ideas span gamification, social features, AI personalization, behavioral psychology, integrations, and novel UX; includes cross-domain inspiration",
|
|
56
|
+
"3": "Ideas cover 2-3 categories; some variety but limited cross-domain thinking",
|
|
57
|
+
"1": "All ideas are variations of the same approach (e.g., all gamification)",
|
|
58
|
+
"0": "1-2 generic ideas"
|
|
59
|
+
}
|
|
60
|
+
},
|
|
61
|
+
{
|
|
62
|
+
"criterion": "Creativity & Novelty",
|
|
63
|
+
"weight": 0.35,
|
|
64
|
+
"scoring": {
|
|
65
|
+
"5": "At least 30% of ideas are novel or adapted from other domains; includes surprising or non-obvious concepts",
|
|
66
|
+
"3": "Mix of standard and somewhat creative ideas; few surprises",
|
|
67
|
+
"1": "All ideas are well-known in the habit-tracking space",
|
|
68
|
+
"0": "No creative effort"
|
|
69
|
+
}
|
|
70
|
+
},
|
|
71
|
+
{
|
|
72
|
+
"criterion": "Structure & Feasibility",
|
|
73
|
+
"weight": 0.3,
|
|
74
|
+
"scoring": {
|
|
75
|
+
"5": "Ideas clustered by theme; feasibility assessed; top ideas have concrete descriptions and first steps",
|
|
76
|
+
"3": "Some grouping and feasibility notes but incomplete",
|
|
77
|
+
"1": "Flat list with no structure or feasibility",
|
|
78
|
+
"0": "Unorganized dump"
|
|
79
|
+
}
|
|
80
|
+
}
|
|
81
|
+
],
|
|
82
|
+
"expectedScoreWithout": 30,
|
|
83
|
+
"expectedScoreWith": 70
|
|
84
|
+
},
|
|
85
|
+
{
|
|
86
|
+
"id": "bench-easy-03",
|
|
87
|
+
"difficulty": "easy",
|
|
88
|
+
"description": "Simple brainstorm for event planning",
|
|
89
|
+
"input": "Think of creative ways to make a company's annual all-hands meeting more engaging and memorable for 150 remote employees.",
|
|
90
|
+
"rubric": [
|
|
91
|
+
{
|
|
92
|
+
"criterion": "Idea Volume & Range",
|
|
93
|
+
"weight": 0.35,
|
|
94
|
+
"scoring": {
|
|
95
|
+
"5": "15+ ideas covering technology, interactive formats, entertainment, team building, and follow-up activities",
|
|
96
|
+
"3": "8-14 ideas across 2-3 categories",
|
|
97
|
+
"1": "Fewer than 8 ideas in one category",
|
|
98
|
+
"0": "Fewer than 3 ideas"
|
|
99
|
+
}
|
|
100
|
+
},
|
|
101
|
+
{
|
|
102
|
+
"criterion": "Remote-Specific Innovation",
|
|
103
|
+
"weight": 0.35,
|
|
104
|
+
"scoring": {
|
|
105
|
+
"5": "Ideas specifically leverage or address remote context; includes novel virtual engagement mechanics; cross-domain inspiration (gaming, live events, education)",
|
|
106
|
+
"3": "Ideas acknowledge remote context but mostly adapt in-person activities",
|
|
107
|
+
"1": "Ideas ignore the remote constraint or are generic",
|
|
108
|
+
"0": "No remote consideration"
|
|
109
|
+
}
|
|
110
|
+
},
|
|
111
|
+
{
|
|
112
|
+
"criterion": "Prioritization",
|
|
113
|
+
"weight": 0.3,
|
|
114
|
+
"scoring": {
|
|
115
|
+
"5": "Ideas ranked by impact and effort; feasibility noted; top 3-5 highlighted with implementation steps",
|
|
116
|
+
"3": "Some ranking but informal; limited implementation detail",
|
|
117
|
+
"1": "No ranking or prioritization",
|
|
118
|
+
"0": "No structure"
|
|
119
|
+
}
|
|
120
|
+
}
|
|
121
|
+
],
|
|
122
|
+
"expectedScoreWithout": 35,
|
|
123
|
+
"expectedScoreWith": 75
|
|
124
|
+
},
|
|
125
|
+
{
|
|
126
|
+
"id": "bench-med-01",
|
|
127
|
+
"difficulty": "medium",
|
|
128
|
+
"description": "Multi-constraint brainstorm requiring trade-off analysis",
|
|
129
|
+
"input": "Brainstorm solutions to reduce food waste in a university dining hall that serves 3,000 students daily. Constraints: budget under $10,000 for implementation, must not reduce food variety, and solutions should be deployable within one semester. I need ideas across technology, behavioral, and operational categories.",
|
|
130
|
+
"rubric": [
|
|
131
|
+
{
|
|
132
|
+
"criterion": "Constraint Awareness",
|
|
133
|
+
"weight": 0.25,
|
|
134
|
+
"scoring": {
|
|
135
|
+
"5": "All three constraints (budget, variety, timeline) explicitly addressed in feasibility assessment; ideas flagged when they push constraint boundaries",
|
|
136
|
+
"3": "Constraints mentioned but not systematically checked against each idea",
|
|
137
|
+
"1": "Constraints acknowledged but largely ignored in idea generation",
|
|
138
|
+
"0": "Constraints not considered"
|
|
139
|
+
}
|
|
140
|
+
},
|
|
141
|
+
{
|
|
142
|
+
"criterion": "Multi-Category Coverage",
|
|
143
|
+
"weight": 0.25,
|
|
144
|
+
"scoring": {
|
|
145
|
+
"5": "Substantive ideas in all 3 requested categories (technology, behavioral, operational) plus unexpected categories; 20+ ideas total",
|
|
146
|
+
"3": "Ideas in 2 of 3 categories; 10-19 ideas",
|
|
147
|
+
"1": "Ideas concentrated in one category only",
|
|
148
|
+
"0": "Fewer than 5 ideas"
|
|
149
|
+
}
|
|
150
|
+
},
|
|
151
|
+
{
|
|
152
|
+
"criterion": "Feasibility Rigor",
|
|
153
|
+
"weight": 0.25,
|
|
154
|
+
"scoring": {
|
|
155
|
+
"5": "Each idea scored on 4 feasibility dimensions; composite scores calculated; 40%+ viable/promising; budget estimates included for top ideas",
|
|
156
|
+
"3": "Informal feasibility notes; some viable ideas identified but scoring incomplete",
|
|
157
|
+
"1": "Minimal feasibility consideration",
|
|
158
|
+
"0": "No feasibility assessment"
|
|
159
|
+
}
|
|
160
|
+
},
|
|
161
|
+
{
|
|
162
|
+
"criterion": "Innovation Quality",
|
|
163
|
+
"weight": 0.25,
|
|
164
|
+
"scoring": {
|
|
165
|
+
"5": "Includes cross-domain transfers (e.g., supply chain optimization, behavioral economics nudges); at least 30% novel or adapted ideas",
|
|
166
|
+
"3": "Some creative ideas but mostly standard approaches to food waste",
|
|
167
|
+
"1": "All ideas are commonly known food waste solutions",
|
|
168
|
+
"0": "No creative effort"
|
|
169
|
+
}
|
|
170
|
+
}
|
|
171
|
+
],
|
|
172
|
+
"expectedScoreWithout": 25,
|
|
173
|
+
"expectedScoreWith": 65
|
|
174
|
+
},
|
|
175
|
+
{
|
|
176
|
+
"id": "bench-med-02",
|
|
177
|
+
"difficulty": "medium",
|
|
178
|
+
"description": "Cross-domain ideation for a technical challenge",
|
|
179
|
+
"input": "Generate creative ideas for reducing API response latency in a microservices architecture without increasing infrastructure costs. Current p99 latency is 800ms and the target is under 200ms. Think beyond traditional caching and load balancing.",
|
|
180
|
+
"rubric": [
|
|
181
|
+
{
|
|
182
|
+
"criterion": "Beyond-Obvious Ideas",
|
|
183
|
+
"weight": 0.3,
|
|
184
|
+
"scoring": {
|
|
185
|
+
"5": "Generates ideas beyond standard caching/load-balancing: includes architectural patterns, data flow redesigns, edge computing, predictive pre-computation, protocol changes, or cross-domain analogies; at least 5 non-obvious ideas",
|
|
186
|
+
"3": "Some ideas go beyond obvious solutions but most are variations of caching/scaling",
|
|
187
|
+
"1": "All ideas are standard optimization techniques",
|
|
188
|
+
"0": "Generic advice without specific ideas"
|
|
189
|
+
}
|
|
190
|
+
},
|
|
191
|
+
{
|
|
192
|
+
"criterion": "Technical Depth",
|
|
193
|
+
"weight": 0.3,
|
|
194
|
+
"scoring": {
|
|
195
|
+
"5": "Ideas include specific technical mechanisms, trade-offs, and estimated latency impact; demonstrates understanding of microservices challenges",
|
|
196
|
+
"3": "Ideas are technically reasonable but lack specificity on implementation or impact",
|
|
197
|
+
"1": "Ideas are technically shallow or contain errors",
|
|
198
|
+
"0": "Technically invalid suggestions"
|
|
199
|
+
}
|
|
200
|
+
},
|
|
201
|
+
{
|
|
202
|
+
"criterion": "Framework Application",
|
|
203
|
+
"weight": 0.2,
|
|
204
|
+
"scoring": {
|
|
205
|
+
"5": "Uses TRIZ contradiction resolution (speed vs. cost), SCAMPER on the request/response lifecycle, or analogical transfer from other latency-critical domains",
|
|
206
|
+
"3": "Some structured approach but framework usage is superficial",
|
|
207
|
+
"1": "No framework usage; ad-hoc brainstorming only",
|
|
208
|
+
"0": "No structured approach"
|
|
209
|
+
}
|
|
210
|
+
},
|
|
211
|
+
{
|
|
212
|
+
"criterion": "Prioritized Output",
|
|
213
|
+
"weight": 0.2,
|
|
214
|
+
"scoring": {
|
|
215
|
+
"5": "Ideas clustered by approach type; feasibility scored with cost-neutrality check; top ideas include estimated latency reduction and implementation steps",
|
|
216
|
+
"3": "Some grouping and prioritization but incomplete feasibility data",
|
|
217
|
+
"1": "Flat list without prioritization",
|
|
218
|
+
"0": "Unstructured output"
|
|
219
|
+
}
|
|
220
|
+
}
|
|
221
|
+
],
|
|
222
|
+
"expectedScoreWithout": 25,
|
|
223
|
+
"expectedScoreWith": 65
|
|
224
|
+
},
|
|
225
|
+
{
|
|
226
|
+
"id": "bench-med-03",
|
|
227
|
+
"difficulty": "medium",
|
|
228
|
+
"description": "Brainstorm with stakeholder complexity",
|
|
229
|
+
"input": "Brainstorm ideas for a public library system to increase engagement among teenagers (13-18). The library board is conservative and risk-averse, teens find libraries 'boring', and budget is tight. I need ideas that would appeal to teens AND get board approval.",
|
|
230
|
+
"rubric": [
|
|
231
|
+
{
|
|
232
|
+
"criterion": "Dual-Audience Navigation",
|
|
233
|
+
"weight": 0.3,
|
|
234
|
+
"scoring": {
|
|
235
|
+
"5": "Ideas explicitly address both teen appeal AND board acceptability; trade-offs between audiences are analyzed; framing suggestions for board presentations included",
|
|
236
|
+
"3": "Ideas generally appropriate for both audiences but trade-offs not explicitly analyzed",
|
|
237
|
+
"1": "Ideas appeal to one audience but alienate the other",
|
|
238
|
+
"0": "Audience needs not considered"
|
|
239
|
+
}
|
|
240
|
+
},
|
|
241
|
+
{
|
|
242
|
+
"criterion": "Idea Diversity & Volume",
|
|
243
|
+
"weight": 0.25,
|
|
244
|
+
"scoring": {
|
|
245
|
+
"5": "20+ ideas across programming, space design, digital integration, partnerships, and outreach; includes cross-domain inspiration from gaming, social media, or education",
|
|
246
|
+
"3": "10-19 ideas across 2-3 categories",
|
|
247
|
+
"1": "Fewer than 10 ideas in one category",
|
|
248
|
+
"0": "Fewer than 5 ideas"
|
|
249
|
+
}
|
|
250
|
+
},
|
|
251
|
+
{
|
|
252
|
+
"criterion": "Feasibility & Budget Awareness",
|
|
253
|
+
"weight": 0.25,
|
|
254
|
+
"scoring": {
|
|
255
|
+
"5": "Ideas scored for feasibility with budget sensitivity; low-cost quick wins identified alongside longer-term investments; implementation staged by effort",
|
|
256
|
+
"3": "Budget mentioned but not systematically addressed; some feasibility notes",
|
|
257
|
+
"1": "Budget constraint largely ignored",
|
|
258
|
+
"0": "No feasibility consideration"
|
|
259
|
+
}
|
|
260
|
+
},
|
|
261
|
+
{
|
|
262
|
+
"criterion": "Problem Reframing",
|
|
263
|
+
"weight": 0.2,
|
|
264
|
+
"scoring": {
|
|
265
|
+
"5": "Problem reframed from multiple angles (teen identity, community role, digital-physical hybrid, competition with other activities); reframes drive meaningfully different ideas",
|
|
266
|
+
"3": "Some reframing attempted but ideas don't significantly differ from initial framing",
|
|
267
|
+
"1": "No reframing; takes the problem at face value",
|
|
268
|
+
"0": "Problem misunderstood"
|
|
269
|
+
}
|
|
270
|
+
}
|
|
271
|
+
],
|
|
272
|
+
"expectedScoreWithout": 25,
|
|
273
|
+
"expectedScoreWith": 70
|
|
274
|
+
},
|
|
275
|
+
{
|
|
276
|
+
"id": "bench-med-04",
|
|
277
|
+
"difficulty": "medium",
|
|
278
|
+
"description": "Brainstorm requiring feasibility matrix with quantitative scoring",
|
|
279
|
+
"input": "Generate ideas for a small e-commerce startup (5 people, $50K budget) to differentiate from Amazon in a niche market (artisanal home goods). I need each idea scored on a feasibility matrix with technical viability, resource requirements, time-to-implement, and impact potential.",
|
|
280
|
+
"rubric": [
|
|
281
|
+
{
|
|
282
|
+
"criterion": "Feasibility Matrix Quality",
|
|
283
|
+
"weight": 0.35,
|
|
284
|
+
"scoring": {
|
|
285
|
+
"5": "Every idea scored on all 4 dimensions (1-5 scale); composite scores computed; ideas classified as viable/promising/speculative; matrix is internally consistent",
|
|
286
|
+
"3": "Most ideas have feasibility notes but not all 4 dimensions; some numerical scoring",
|
|
287
|
+
"1": "Informal feasibility comments without systematic scoring",
|
|
288
|
+
"0": "No feasibility assessment"
|
|
289
|
+
}
|
|
290
|
+
},
|
|
291
|
+
{
|
|
292
|
+
"criterion": "Strategic Differentiation",
|
|
293
|
+
"weight": 0.3,
|
|
294
|
+
"scoring": {
|
|
295
|
+
"5": "Ideas target specific Amazon weaknesses (personalization, curation, community, story, craft authenticity); each idea explains WHY it differentiates",
|
|
296
|
+
"3": "Some differentiation awareness but ideas could apply to any e-commerce site",
|
|
297
|
+
"1": "Ideas are generic e-commerce tactics not specific to competing with Amazon",
|
|
298
|
+
"0": "No differentiation strategy"
|
|
299
|
+
}
|
|
300
|
+
},
|
|
301
|
+
{
|
|
302
|
+
"criterion": "Startup-Context Fit",
|
|
303
|
+
"weight": 0.2,
|
|
304
|
+
"scoring": {
|
|
305
|
+
"5": "Ideas respect 5-person team and $50K budget; lean/scrappy approaches prioritized; growth staging suggested",
|
|
306
|
+
"3": "Budget acknowledged but some ideas clearly exceed constraints",
|
|
307
|
+
"1": "Ideas require enterprise-level resources",
|
|
308
|
+
"0": "Constraints completely ignored"
|
|
309
|
+
}
|
|
310
|
+
},
|
|
311
|
+
{
|
|
312
|
+
"criterion": "Clustering & Prioritization",
|
|
313
|
+
"weight": 0.15,
|
|
314
|
+
"scoring": {
|
|
315
|
+
"5": "Ideas grouped into strategic themes; top 3-5 ideas highlighted with first steps; quick wins vs. long-term plays distinguished",
|
|
316
|
+
"3": "Some grouping but ranking is informal",
|
|
317
|
+
"1": "Flat list",
|
|
318
|
+
"0": "No organization"
|
|
319
|
+
}
|
|
320
|
+
}
|
|
321
|
+
],
|
|
322
|
+
"expectedScoreWithout": 25,
|
|
323
|
+
"expectedScoreWith": 70
|
|
324
|
+
},
|
|
325
|
+
{
|
|
326
|
+
"id": "bench-hard-01",
|
|
327
|
+
"difficulty": "hard",
|
|
328
|
+
"description": "Complex multi-stakeholder brainstorm with competing priorities",
|
|
329
|
+
"input": "Brainstorm solutions for reducing urban traffic congestion in a mid-size city (population 500K). Stakeholders: city government (limited budget, election cycle pressure), residents (want less noise and pollution), businesses (need delivery access and customer parking), environmental groups (want car-free zones), and public transit authority (underfunded). Generate ideas that balance these competing interests, assess feasibility, and identify which stakeholder coalitions each idea could build.",
|
|
330
|
+
"rubric": [
|
|
331
|
+
{
|
|
332
|
+
"criterion": "Stakeholder Analysis",
|
|
333
|
+
"weight": 0.25,
|
|
334
|
+
"scoring": {
|
|
335
|
+
"5": "Each idea explicitly maps which stakeholders benefit, which bear costs, and what coalitions support it; trade-offs between stakeholders analyzed; ideas designed to build multi-stakeholder support",
|
|
336
|
+
"3": "Stakeholders mentioned but mapping is incomplete; 2-3 stakeholders considered per idea",
|
|
337
|
+
"1": "Stakeholders listed but ideas don't account for competing interests",
|
|
338
|
+
"0": "Stakeholder complexity ignored"
|
|
339
|
+
}
|
|
340
|
+
},
|
|
341
|
+
{
|
|
342
|
+
"criterion": "Idea Volume & Multi-Dimensionality",
|
|
343
|
+
"weight": 0.25,
|
|
344
|
+
"scoring": {
|
|
345
|
+
"5": "25+ ideas across infrastructure, policy, technology, behavioral, economic incentive, and land-use dimensions; includes cross-domain transfers from logistics, game theory, or urban planning research",
|
|
346
|
+
"3": "15-24 ideas across 3-4 dimensions",
|
|
347
|
+
"1": "Fewer than 15 ideas concentrated in 1-2 dimensions",
|
|
348
|
+
"0": "Fewer than 8 ideas"
|
|
349
|
+
}
|
|
350
|
+
},
|
|
351
|
+
{
|
|
352
|
+
"criterion": "Framework Sophistication",
|
|
353
|
+
"weight": 0.25,
|
|
354
|
+
"scoring": {
|
|
355
|
+
"5": "Uses TRIZ to resolve stakeholder contradictions; applies Six Hats for multi-perspective analysis; uses SCAMPER on existing traffic systems; cross-domain analogies (ant colonies, fluid dynamics, network routing)",
|
|
356
|
+
"3": "One framework applied well; some structured thinking visible",
|
|
357
|
+
"1": "No framework usage; ideas appear ad-hoc",
|
|
358
|
+
"0": "No structured creative methodology"
|
|
359
|
+
}
|
|
360
|
+
},
|
|
361
|
+
{
|
|
362
|
+
"criterion": "Actionable Output",
|
|
363
|
+
"weight": 0.25,
|
|
364
|
+
"scoring": {
|
|
365
|
+
"5": "Ideas clustered by implementation timeline (quick wins / medium-term / transformative); feasibility scored; political viability assessed; top 5 ideas have detailed implementation roadmaps",
|
|
366
|
+
"3": "Some clustering and prioritization; limited implementation detail",
|
|
367
|
+
"1": "Ideas listed without prioritization or implementation guidance",
|
|
368
|
+
"0": "Unstructured idea dump"
|
|
369
|
+
}
|
|
370
|
+
}
|
|
371
|
+
],
|
|
372
|
+
"expectedScoreWithout": 20,
|
|
373
|
+
"expectedScoreWith": 60
|
|
374
|
+
},
|
|
375
|
+
{
|
|
376
|
+
"id": "bench-hard-02",
|
|
377
|
+
"difficulty": "hard",
|
|
378
|
+
"description": "Paradigm-breaking brainstorm requiring fundamental reframing",
|
|
379
|
+
"input": "The traditional university education model (4-year degree, lectures, exams, campus-based) is being challenged by online learning, bootcamps, and AI tutors. Brainstorm radically different models for higher education in 2035. Don't just improve the current model — think about what could replace it entirely. I need ideas that are truly novel, not incremental improvements, with feasibility assessment for a 10-year horizon.",
|
|
380
|
+
"rubric": [
|
|
381
|
+
{
|
|
382
|
+
"criterion": "Paradigm Novelty",
|
|
383
|
+
"weight": 0.3,
|
|
384
|
+
"scoring": {
|
|
385
|
+
"5": "At least 50% of ideas represent genuinely new education paradigms (not incremental improvements to lectures/exams); challenges fundamental assumptions about what a university IS; ideas would be surprising to higher-ed professionals",
|
|
386
|
+
"3": "Mix of novel and incremental ideas; some assumption-challenging but also many 'better version of current' ideas",
|
|
387
|
+
"1": "Mostly incremental improvements to the existing model with some new technology added",
|
|
388
|
+
"0": "No paradigm-breaking ideas"
|
|
389
|
+
}
|
|
390
|
+
},
|
|
391
|
+
{
|
|
392
|
+
"criterion": "Problem Reframing Depth",
|
|
393
|
+
"weight": 0.25,
|
|
394
|
+
"scoring": {
|
|
395
|
+
"5": "Challenges 5+ fundamental assumptions (time-bounded, location-based, credential-focused, age-cohort, discipline-siloed); reframes from learner, employer, society, and knowledge-creation perspectives",
|
|
396
|
+
"3": "Challenges 2-3 assumptions; 2 reframing perspectives",
|
|
397
|
+
"1": "Takes the problem at face value with minimal reframing",
|
|
398
|
+
"0": "No reframing"
|
|
399
|
+
}
|
|
400
|
+
},
|
|
401
|
+
{
|
|
402
|
+
"criterion": "10-Year Feasibility Assessment",
|
|
403
|
+
"weight": 0.25,
|
|
404
|
+
"scoring": {
|
|
405
|
+
"5": "Each idea assessed for 10-year viability considering technology trends, demographic shifts, economic forces, and regulatory environment; transition pathways from current to future state described",
|
|
406
|
+
"3": "Some forward-looking feasibility but analysis is shallow or misses key factors",
|
|
407
|
+
"1": "Feasibility based on current conditions, not 10-year projection",
|
|
408
|
+
"0": "No feasibility assessment"
|
|
409
|
+
}
|
|
410
|
+
},
|
|
411
|
+
{
|
|
412
|
+
"criterion": "Cross-Domain Inspiration",
|
|
413
|
+
"weight": 0.2,
|
|
414
|
+
"scoring": {
|
|
415
|
+
"5": "Ideas draw from gaming (progression systems), open source (collaborative creation), healthcare (personalized treatment), professional sports (talent development), or other unexpected domains",
|
|
416
|
+
"3": "Some cross-domain thinking but mostly from obvious adjacent domains (e.g., corporate training)",
|
|
417
|
+
"1": "All ideas from within the education domain",
|
|
418
|
+
"0": "No cross-domain thinking"
|
|
419
|
+
}
|
|
420
|
+
}
|
|
421
|
+
],
|
|
422
|
+
"expectedScoreWithout": 20,
|
|
423
|
+
"expectedScoreWith": 60
|
|
424
|
+
},
|
|
425
|
+
{
|
|
426
|
+
"id": "bench-hard-03",
|
|
427
|
+
"difficulty": "hard",
|
|
428
|
+
"description": "Brainstorm under severe constraints requiring creative constraint navigation",
|
|
429
|
+
"input": "A nonprofit organization with 2 staff members and zero budget needs to increase community awareness about mental health resources in a rural area with limited internet access and high stigma around mental health. Brainstorm at least 20 ideas. Every idea must work with no money and no reliable internet. I need creative solutions that navigate the stigma barrier.",
|
|
430
|
+
"rubric": [
|
|
431
|
+
{
|
|
432
|
+
"criterion": "Constraint Adherence",
|
|
433
|
+
"weight": 0.25,
|
|
434
|
+
"scoring": {
|
|
435
|
+
"5": "All ideas genuinely work with zero budget and no internet; creative resource acquisition strategies (partnerships, in-kind, volunteer networks) identified; no ideas that secretly require funding",
|
|
436
|
+
"3": "Most ideas respect constraints but 2-3 require modest resources not available",
|
|
437
|
+
"1": "Many ideas ignore the zero-budget or no-internet constraints",
|
|
438
|
+
"0": "Constraints largely ignored"
|
|
439
|
+
}
|
|
440
|
+
},
|
|
441
|
+
{
|
|
442
|
+
"criterion": "Stigma Navigation",
|
|
443
|
+
"weight": 0.3,
|
|
444
|
+
"scoring": {
|
|
445
|
+
"5": "Ideas specifically address stigma with proven de-stigmatization approaches (normalization, trusted messenger strategy, indirect entry points, community-embedded approaches); at least 5 ideas include stigma-navigation mechanisms",
|
|
446
|
+
"3": "Stigma acknowledged but ideas don't specifically address how to overcome it",
|
|
447
|
+
"1": "Stigma mentioned once; ideas would likely trigger stigma avoidance",
|
|
448
|
+
"0": "Stigma barrier ignored entirely"
|
|
449
|
+
}
|
|
450
|
+
},
|
|
451
|
+
{
|
|
452
|
+
"criterion": "Idea Volume & Creativity",
|
|
453
|
+
"weight": 0.25,
|
|
454
|
+
"scoring": {
|
|
455
|
+
"5": "20+ ideas; includes cross-domain inspiration (public health campaigns, grassroots organizing, religious community networks, agricultural extension models); highly creative given extreme constraints",
|
|
456
|
+
"3": "15-19 ideas with moderate creativity; some cross-domain thinking",
|
|
457
|
+
"1": "Fewer than 15 ideas; mostly obvious approaches (flyers, events)",
|
|
458
|
+
"0": "Fewer than 10 ideas"
|
|
459
|
+
}
|
|
460
|
+
},
|
|
461
|
+
{
|
|
462
|
+
"criterion": "Feasibility & Prioritization",
|
|
463
|
+
"weight": 0.2,
|
|
464
|
+
"scoring": {
|
|
465
|
+
"5": "Ideas scored for impact and effort (given 2 staff, zero budget); quick wins vs. relationship-building plays identified; implementation sequence suggested; partnership opportunities flagged",
|
|
466
|
+
"3": "Some prioritization but effort estimates missing or unrealistic for 2-person team",
|
|
467
|
+
"1": "No prioritization; ideas presented as equally weighted",
|
|
468
|
+
"0": "No feasibility assessment"
|
|
469
|
+
}
|
|
470
|
+
}
|
|
471
|
+
],
|
|
472
|
+
"expectedScoreWithout": 20,
|
|
473
|
+
"expectedScoreWith": 60
|
|
474
|
+
}
|
|
475
|
+
]
|
|
476
|
+
}
|
package/tests/smoke.json
ADDED
|
@@ -0,0 +1,54 @@
|
|
|
1
|
+
{
|
|
2
|
+
"version": "0.0.1",
|
|
3
|
+
"timeout": 60,
|
|
4
|
+
"tasks": [
|
|
5
|
+
{
|
|
6
|
+
"id": "smoke-01",
|
|
7
|
+
"description": "Brainstorm ideas for improving employee onboarding at a mid-size tech company with multi-framework ideation and feasibility assessment",
|
|
8
|
+
"input": "Brainstorm creative solutions to improve the employee onboarding experience at a mid-size tech company (200 employees). Current onboarding takes 2 weeks and new hires report feeling lost and disconnected. Budget is limited. I need diverse ideas with feasibility ratings.",
|
|
9
|
+
"rubric": [
|
|
10
|
+
{
|
|
11
|
+
"criterion": "Idea Quantity & Diversity",
|
|
12
|
+
"weight": 0.25,
|
|
13
|
+
"scoring": {
|
|
14
|
+
"5": "Generates 15+ ideas spanning 3+ distinct categories (technology, culture, process, mentorship, etc.); uses multiple creativity frameworks; includes cross-domain ideas",
|
|
15
|
+
"3": "Generates 8-14 ideas across 2 categories; uses at least one framework; mostly same-domain thinking",
|
|
16
|
+
"1": "Generates fewer than 8 ideas; all ideas are from the same category or approach",
|
|
17
|
+
"0": "Fewer than 3 ideas or no structured ideation"
|
|
18
|
+
}
|
|
19
|
+
},
|
|
20
|
+
{
|
|
21
|
+
"criterion": "Framework Application",
|
|
22
|
+
"weight": 0.25,
|
|
23
|
+
"scoring": {
|
|
24
|
+
"5": "Visibly applies 2+ creativity frameworks (SCAMPER, Six Hats, TRIZ, lateral thinking); framework application drives idea diversity",
|
|
25
|
+
"3": "References a framework but applies it superficially; ideas don't clearly derive from structured methods",
|
|
26
|
+
"1": "No recognizable framework usage; ideas appear free-associated",
|
|
27
|
+
"0": "No structured approach at all"
|
|
28
|
+
}
|
|
29
|
+
},
|
|
30
|
+
{
|
|
31
|
+
"criterion": "Feasibility Assessment",
|
|
32
|
+
"weight": 0.3,
|
|
33
|
+
"scoring": {
|
|
34
|
+
"5": "Each idea has explicit feasibility scoring (technical viability, resources, time, impact); ideas are classified as viable/promising/speculative; 40%+ are viable or promising",
|
|
35
|
+
"3": "Some ideas have feasibility notes but scoring is informal or incomplete; viability is mentioned but not systematically assessed",
|
|
36
|
+
"1": "Feasibility is mentioned for 1-2 ideas only; no systematic assessment",
|
|
37
|
+
"0": "No feasibility assessment provided"
|
|
38
|
+
}
|
|
39
|
+
},
|
|
40
|
+
{
|
|
41
|
+
"criterion": "Output Structure",
|
|
42
|
+
"weight": 0.2,
|
|
43
|
+
"scoring": {
|
|
44
|
+
"5": "Ideas are clustered by theme, ranked by priority; top ideas have concrete first steps; includes executive summary and wild cards section",
|
|
45
|
+
"3": "Ideas are grouped but ranking is informal; some actionable detail but not consistently",
|
|
46
|
+
"1": "Flat list of ideas with no clustering or prioritization",
|
|
47
|
+
"0": "Unstructured dump of ideas"
|
|
48
|
+
}
|
|
49
|
+
}
|
|
50
|
+
],
|
|
51
|
+
"passThreshold": 60
|
|
52
|
+
}
|
|
53
|
+
]
|
|
54
|
+
}
|