skills.rest
sicktastic
sicktasticCOMMUNITY
Explore all skills by this author →
Website𝕏@sicktasticGitHub

brainstorming

Transform vague ideas into structured design plans before implementation.

Updated Apr 6, 2026
Search Tags:#design#documentation#brainstorming#requirements#strategy#approval#product-planning
One-click install
npx skills add https://github.com/sicktastic/skill-issue --skill brainstorming-sicktastic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/sicktastic/skill-issue/tree/main/product-management/brainstorming
Command: npx skills add https://github.com/sicktastic/skill-issue --skill brainstorming-sicktastic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming ensures every creative effort begins with shared understanding, preventing wasted work caused by assumptions or skipping the design step before writing code.

Core Features & Use Cases

  • Structured Exploration: Check project context, documentation, and recent changes before diving into design ideas.
  • Clarifying Dialogue: Ask focused questions one at a time to surface purpose, constraints, and success criteria directly from stakeholders.
  • Approach Comparison & Validation: Present 2–3 trade-off-driven approaches, deliver design sections for approval, and document the validated plan before implementation.
  • Use Case: When a product manager wants to expand a feature set, use this Skill to investigate requirements, capture alternatives, and get documented sign-off before handing off to engineers.

Quick Start

Start by exploring the project context, ask one clarifying question, and then outline the intended design approach.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn vague product ideas into structured design plans before implementation?▼

Structured design plans emerge from vague ideas by investigating project context, asking clarifying questions sequentially, comparing approaches, and documenting validated approvals before coding begins.

What is the best way to document requirements and get stakeholder sign-off for a new feature?▼

Documenting requirements and gaining sign-off is achieved by presenting 2–3 trade-off-driven approaches, delivering design sections for approval, and finalizing the validated plan before implementation handoff.

How do I clarify project constraints and success criteria with stakeholders during product planning?▼

Clarifying project constraints and success criteria requires asking focused questions one at a time to surface purpose directly from stakeholders, ensuring shared understanding before design work proceeds.

Does structured brainstorming work for product management projects that require approach comparison?▼

Structured brainstorming suits product management projects by enforcing investigation, evaluating multiple approaches with trade-offs, and documenting finalized design plans prior to transitioning to implementation readiness.

When should I not use a guided brainstorming approach for design documentation?▼

Guided brainstorming should be avoided when implementation must begin immediately without clarifying context, comparing approaches, or securing documented stakeholder approvals, as it enforces sequential questioning and validation steps.

Related Skills

Explore More Product & Management Skills→
ianclearyiancleary
1

brainstorming

Guide structured dialogue to clarify requirements and propose design alternatives.

Community
Intermediate
lv416elv416e
6

writing-plans

Generate implementation plans with file paths, code examples, and TDD tasks.

Community
Basic
edwardmonteiroedwardmonteiro

delivery.roadmap

Translate strategy into a sequenced delivery roadmap with risks and stakeholder communication.

Community
Basic
zinohomezinohome

brainstorming

Guide software ideas through structured brainstorming into approved design specifications.

Community
Advanced