skills.rest
lucasmiachon-blip
lucasmiachon-blipCOMMUNITY
Explore all skills by this author →
GitHub

brainstorming

Guide teams through structured pre-action brainstorming to define scope and guardrails.

Updated Aug 23, 2026
Search Tags:#planning#scoping#brainstorming#requirements#decision-making#project-management#domain-analysis
One-click install
npx skills add https://github.com/lucasmiachon-blip/OLMO --skill brainstorming-lucasmiachon-blip
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/lucasmiachon-blip/OLMO/tree/main/.claude/skills/brainstorming
Command: npx skills add https://github.com/lucasmiachon-blip/OLMO --skill brainstorming-lucasmiachon-blip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill guides teams through a structured pre-action brainstorming process to define WHAT, WHY, WHO, and HOW before implementation, reducing ambiguity and surfacing clear scope with guardrails.

Core Features & Use Cases

  • A multi-phase framework (SEED, DIVERGE, CONVERGE, EXIT) that surfaces domain signals, clarifies goals, and prevents scope creep.
  • Domain-specific questioning templates and guardrails that align stakeholders and surface risks before any design or coding begins.
  • Use Case: a product team starts a new feature by aligning on the problem, audience, success criteria, and constraints prior to writing specs or code.

Quick Start

Provide a topic or problem and begin with the Seed phase questions to define scope.

Frequently Asked Questions about brainstorming

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scope a project before implementation to prevent scope creep?▼

To prevent scope creep during project scoping, teams must define WHAT, WHY, WHO, and HOW before implementation begins. A structured pre-action brainstorming process uses guardrails and explicit EXIT criteria to surface clear scope and align stakeholders.

What is the best way to align stakeholders during early feature definition?▼

Stakeholder alignment during early feature definition requires a multi-phase brainstorming framework of SEED, DIVERGE, CONVERGE, and EXIT. This structured process surfaces domain signals, clarifies goals, and enforces constraints prior to writing specifications.

How do I start brainstorming requirements for a new feature?▼

Start brainstorming requirements by providing a topic or problem and answering SEED phase questions. This initial phase defines the problem scope, audience, and success criteria before progressing to divergent and convergent analysis.

Can I use this brainstorming framework for research planning across different domains?▼

Yes, this brainstorming framework applies to research planning across domains using domain-specific questioning templates. It adapts its four-phase flow to surface relevant domain signals and risks, ensuring safe, incremental planning regardless of the industry.

When should I use a structured pre-action brainstorming process instead of immediate development?▼

Use a structured pre-action brainstorming process when starting new projects or features to reduce ambiguity. It is necessary before writing specs or code because it surfaces risks, defines success criteria, and establishes explicit NOT/EXIT criteria to prevent scope expansion.

Related Skills

Explore More Product & Management Skills→
soeiroosoeiroo

design-brief

Create structured design briefs with problem statements, audience, constraints, and success criteria.

Community
Intermediate
VidyaBodepudiVidyaBodepudi
2

spec-driven-development

Create formal software specifications with acceptance criteria and scope definitions.

Community
Advanced
woxiangyangzhimaowoxiangyangzhimao
3

goal

Transform user intent into measurable goals with success criteria.

Community
Advanced
viraatdasviraatdas

design-shotgun

Generate multiple AI design variants and present them side-by-side in a browser.

Community
Advanced