brainstorming

Refines ideas into approved designs through structured dialogue before implementation begins.

1|Updated Jul 18, 2025
One-click install
npx skills add https://github.com/gusgad/service-agent-by-sap --skill brainstorming-gusgad
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/gusgad/service-agent-by-sap/tree/main/.agents/skills/superpowers/brainstorming
Command: npx skills add https://github.com/gusgad/service-agent-by-sap --skill brainstorming-gusgad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Jumping straight into code on ambiguous or creative tasks leads to unexamined assumptions, wasted rework, and misaligned implementations. This Skill enforces a collaborative design phase so requirements, constraints, and approaches are agreed upon before any code is written. ## Core Features & Use Cases - Structured Discovery: Explores current project context (source files, docs, recent commits) and asks clarifying questions one at a time to pin down purpose, constraints, and success criteria. - Approach Comparison: Proposes 2-3 implementation approaches with trade-offs, leading with a recommendation and applying YAGNI to cut unnecessary scope. - Design Approval Gate: Blocks all implementation until a written design is presented, self-reviewed, and explicitly approved. - Use Case: When asked to add a new scheduled job type to the Service Agent platform, the Skill first examines the agent/ and consumer/ code, asks about scheduling requirements, presents design options, and only proceeds to code after approval. ## Quick Start Ask the assistant to brainstorm and design a new feature before writing any code, for example: help me design a retry mechanism for failed HTTP jobs before implementing it.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I design a feature before writing code?▼

Start by reviewing the existing project context, then ask clarifying questions one at a time about purpose, constraints, and success criteria. Propose 2-3 approaches with trade-offs, present the design in sections, and get explicit approval before implementing.

What is the best way to handle ambiguous feature requests?▼

Break bundled requests into separate design cycles, then refine each piece through focused questions. Write the agreed design down in a durable location such as a docs/ markdown note before moving to implementation.

Does brainstorming apply to small or simple code changes?▼

Yes, even simple changes benefit from a brief design statement because unexamined assumptions cause the most wasted work on simple tasks. The design can be two sentences, but it should be stated and confirmed before touching code.

When should I skip the design phase in development?▼

This Skill enforces a hard gate: no implementation happens until a design is presented and approved, regardless of perceived simplicity. It is not appropriate to skip when the task involves new features, components, or behavior changes.

How do I decompose a large feature request into manageable pieces?▼

Flag bundled requests immediately and split them into independent design and implementation cycles. Each piece gets its own round of context exploration, questions, and design approval rather than refining details of one oversized request.