brainstorming

Guides collaborative design exploration and produces approved specification documents before implementation.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/marcocpt/trae_skills --skill brainstorming-marcocpt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/marcocpt/trae_skills/tree/main/brainstorming
Command: npx skills add https://github.com/marcocpt/trae_skills --skill brainstorming-marcocpt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? It prevents wasted implementation effort by forcing structured exploration of user intent, requirements, and design alternatives before any code is written, ensuring every project starts from an approved specification. ## Core Features & Use Cases - Structured Design Dialogue: Explores project context, asks one clarifying question at a time, presents 2-3 alternative approaches with trade-offs, and delivers section-by-section design proposals for user approval. - Specification Generation: Writes validated design documents to docs/superpowers/specs/, runs self-checks for placeholders, contradictions, ambiguity, and scope, then hands off to a planning skill. - Visual Companion: Serves browser-based prototypes, wireframes, and diagrams via a local Node.js server with WebSocket-based click tracking for visual decision-making. - Use Case: Before building a new feature, run this Skill to clarify requirements, compare architectural approaches, and produce a committed design document that an implementation plan can be built from. ## Quick Start Use the brainstorming skill to help me explore requirements and design an approach for the new feature I want to build before writing any code.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I brainstorm a software design before writing code?

Start by exploring the existing project context, then ask clarifying questions one at a time about purpose, constraints, and success criteria. Present 2-3 alternative approaches with trade-offs, get section-by-section design approval, and write the result to a specification document.

What should a software design specification document include?

A design specification should cover architecture, components, data flow, error handling, and testing strategy. It must be free of placeholders, internal contradictions, and ambiguous requirements, and scoped tightly enough for a single implementation plan.

How do I show UI prototypes during requirements gathering?

Use the visual companion server started via scripts/start-server.sh, which serves HTML mockups to a browser and records user clicks to a .events file. Write content fragments with semantic filenames and the server wraps them in a themed frame automatically.

Does the brainstorming visual companion work on Windows or Codex?

Yes, the start script auto-detects Windows (MSYS/Cygwin) and Codex environments and switches to foreground mode. On Windows, run the Bash tool call with run_in_background set to true so the server survives between session turns.

When should a project be split before writing a specification?

Split a project when the request describes multiple independent subsystems, such as a platform with chat, billing, and analytics. Decompose it into sub-projects with their own spec, plan, and implementation cycles, then brainstorm the first sub-project normally.