brainstorming

Collect context, goals, and constraints to propose design approaches with trade-offs.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/Sanali209/BCor --skill brainstorming-sanali209
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/Sanali209/BCor/tree/main/.agents/skills/brainstorming
Command: npx skills add https://github.com/Sanali209/BCor --skill brainstorming-sanali209

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Brainstorming and design alignment are essential before implementation; this skill provides a structured process to elicit user intent, capture requirements, and create a concrete design path before coding.

Core Features & Use Cases

  • Explore project context, goals, constraints, and success criteria before any implementation.
  • Propose 2-3 design approaches with trade-offs and a recommended path for faster alignment.
  • Document decisions in a design spec and transition to implementation planning with an approval gate.

Quick Start

Begin a brainstorming session by summarizing the project goals and constraints, then outline the design approach and seek user approval before any concrete work.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn product ideas into actionable design specifications?▼

To turn product ideas into actionable design specifications, you must collect context, goals, constraints, and success criteria to identify scope. A structured decision process then presents 2-3 design approaches with trade-offs and a recommended path for alignment.

What is the best way to scope project requirements before implementation?▼

The best way to scope project requirements before implementation is through a structured brainstorming process that explores project context, goals, and constraints. This ensures you capture user intent and create a concrete design path before coding begins.

How do I compare design approaches and trade-offs during project planning?▼

To compare design approaches and trade-offs during project planning, apply a structured decision process that proposes 2-3 distinct options. Each approach includes specific trade-offs and a recommended path to facilitate faster team alignment.

Can I generate an implementation plan directly from a design spec?▼

Yes, you can generate an implementation plan directly from a design spec after user approval. Documenting decisions in the design specification creates a transition gate that authorizes moving from design alignment into concrete implementation planning.

Does brainstorming project architecture require any specific dependencies?▼

Brainstorming project architecture requires no specific dependencies to function. You can begin a session by summarizing project goals and constraints, then outlining the design approach to seek user approval before any concrete work starts.

When do I need to document decisions in a design spec?▼

You need to document decisions in a design spec when transitioning from brainstorming to implementation. Capturing requirements and design approaches in writing ensures alignment and establishes an approval gate before development work proceeds.