brainstorming
/brainstorming
Creative exploration and brainstorming; use it when you need to clarify goals/constraints, explore multiple options, and converge on a direction before implementation.
- Author
- aipoch ↗
- Repository
- medical-research-skills ↗
- Licence
- MIT
- Last repository change
- 17.09.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 17.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Creative exploration and brainstorming; use it when you need to clarify goals/constraints, explore multiple options, and converge on a direction before implementation.
Original author description
Creative exploration and brainstorming; use it when you need to clarify goals/constraints, explore multiple options, and converge on a direction before implementation.
How it works
- When to Use
- Key Features
- Dependencies
- Example Usage
- Implementation Details
SKILL.md preview
--- name: brainstorming description: Creative exploration and brainstorming; use it when you need to clarify goals/constraints, explore multiple options, and converge on a direction before implementation. license: MIT author: AIPOCH --- > **Source**: [https://github.com/aipoch/medical-research-skills](https://github.com/aipoch/medical-research-skills) ## When to Use - You have a vague idea and need to clarify goals, scope, and constraints before committing to a plan. - You want to generate multiple solution directions for a problem and compare trade-offs. - You need to break down a complex problem into smaller, actionable parts. - You’re stuck and need alternative approaches, assumptions to challenge, or fresh angles. - You want to converge from many ideas into a prioritized shortlist and define next steps. ## Key Features - Goal and boundary clarification (objectives, constraints, success criteria). - Structured ideation to produce multiple distinct options. - Problem decomposition into components, subproblems, and decision points. - Evaluation and convergence (trade-offs, risks, feasibility, impact). - Actionable next steps (experiments, prototypes, questions to validate). - Reference workflow support via `references/brainstorming-workflow.md`. ## Dependencies - None ## Example Usage ### Prompt ```text I want to build a feature that helps users learn faster in our app, but I’m not sure what exactly to build. Constraints: 2-week implementation, no new backend services, must work on mobile. Goal: increase weekly retention. Please brainstorm options, compare them, and recommend a direction with next steps. ``` ### Expected Output Structure (Runnable Template) ```markdown ## 1) Clarify Goals & Boundaries - Primary goal: increase weekly retention - Constraints: 2-week build, no new backend services, mobile-first - Success metrics: retention uplift, feature adoption, session frequency ## 2) Generate Options (Diverge) 1. **Spaced repetition reminders** - What it is: ... - Why it helps: ... 2. **Daily micro-challenges** - What it is: ... - Why it helps: ... 3. **Progress-based streaks + milestones** - What it is: ... - Why it helps: ... 4. **Personalized review queue (client-side)** - What it is: ... - Why it helps: ... ## 3) Compare & Evaluate | Option | Effort | Risk | Expected impact | Notes | |---|---:|---:|---:|---| | Spaced repetition reminders | Medium | Low | Medium | ... | | Daily micro-challenges | Medium | Medium | High | ... | | Streaks + milestones | Low | Low | Medium | ... | | Client-side review queue | Medium | Medium | Medium | ... | ## 4) Converge on a Recommendation - Recommended direction: **Daily micro-challenges** - Rationale: ... - Key assumptions to validate: ... ## 5) Next Steps - Prototype: ... - Instrumentation: ... - A/B test plan: ... - Open questions: ... ``` ## Implementation Details - **Workflow**: Follow the structured process described in `references/brainstorming-workflow.md`: 1. Clarify goals, constraints, and success criteria. 2. Diverge: generate multiple distinct options (avoid premature convergence). 3. Decompose: break options into components and required decisions. 4. Evaluate: compare trade-offs (impact, effort, risk, feasibility). 5. Converge: select a direction and define concrete next steps. - **Core parameters to capture** - **Goal**: what outcome to optimize (e.g., retention, cost, latency, satisfaction). - **Constraints**: time, budget, platform, compliance, dependencies. - **Evaluation criteria**: impact, effort, risk, reversibility, time-to-value. - **Assumptions**: what must be true for the chosen direction to work. - **Next-step artifacts**: shortlist, decision rationale, experiment plan, open questions.
Files in this package (3)
- SKILL.md 4 KB
- brainstorming_audit_result_v1.json 11 KB
- references/brainstorming-workflow.md 3 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · aipoch/medical-research-skills | 100 | MIT |
| jjuraszek/pi-gauntlet | 100 | MIT |
| GanyuanRan/Aegis | 100 | MIT |
| Montinou/triqual | 100 | MIT |
| guanyang/antigravity-skills | 100 | MIT |
| osmontero/opencode-skills | 100 | MIT |
| Sanit-mann/The-Insectoids | 100 | MIT |
| coco-research/coco | 100 | MIT |
| ILIV007/prime-skill | 100 | MIT |
Database snapshot: 13.11.2026 · package version 2dddaeb6b50f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90sp-brainstorming
Use when a request needs collaborative exploration of intent, constraints, alternatives, or design before the direction is settled. - 100brainstorming-gate
Use when about to implement any feature, build any component, or make any behavioral change — requires design exploration and user approval before implementation - 100oma-brainstorm
Explore goals, constraints, and alternative approaches before choosing a design. Use when the user requests ideation or design exploration. - 100ia-brainstorming
Pre-implementation exploration: deep interview, approach comparison, design doc. Use when exploring a vague feature idea, clarifying ambiguous requirements, or comparing approaches before coding. For the full workflow, use the ia-brainstorm command (Claude Code). - 100loom-brainstorming
Explore 2-3 implementation options with trade-offs when the user describes a new feature or requirement. Use when: the user asks for a new feature design, implementation options, or technical trade-off analysis. - 90sr-brainstorming
Use when starting any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.