brainstorming
Brainstorming
Explore 2-3 approaches to achieve a defined goal, evaluate trade-offs, and pick a direction with the user.
When to Use
- A goal is defined but the approach is not decided
- Multiple valid solutions exist and trade-offs need evaluation
- The user wants to see options before committing
- The problem can be solved in fundamentally different ways
- You need to stress-test assumptions before investing in a PRD
When NOT to use: The approach is already decided and confirmed, or a brainstorming.md with a chosen direction already exists.
Input
goal-definition.mdfrom the artifact folder (required)context-map.mdfrom the artifact folder (recommended)
More from olamedia/analytics-skills
analyze-project
Use when starting work on any project to produce or update living documentation (TechStack.md, ProjectStructure.md) that bootstraps context for any AI agent session. Run before any feature work, or periodically to keep docs current.
13humanizer
>-
12architect
>-
12goal-definition
Use when you have a raw idea or request and need to define a clear goal with success criteria before exploring solutions. Use when requirements are vague, when "what does done look like" is unclear, or when assumptions need surfacing.
11prd
Use when you have a chosen direction and need to formalize requirements into a Product Requirements Document. Use when user stories, acceptance criteria, and scope boundaries need to be written down before architecture or implementation.
10analyze
Use when you have a raw idea or request and want to run the full analytics pipeline automatically — from research through to an interlinked task list. Best for straightforward problems where the full pipeline can flow with minimal back-and-forth.
10