brainstorming

Guide ideas into approved design documents before implementation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/rahulsc/forge --skill brainstorming-rahulsc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/rahulsc/forge/tree/main/skills/brainstorming
Command: npx skills add https://github.com/rahulsc/forge --skill brainstorming-rahulsc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill transforms raw ideas into fully-formed, approved design documents, ensuring that all new features, refactors, or designs are well-thought-out before implementation begins.

Core Features & Use Cases

  • Exploratory Dialogue: Engages in collaborative discussion to explore intent and requirements.
  • Design Proposal: Generates 2-3 distinct approaches with trade-offs for user consideration.
  • Design Documentation: Creates and commits a formal design document to the repository.
  • Review Integration: Manages a design review loop with a sub-agent and user approval.
  • Use Case: When starting a new feature like "implementing a user profile page," this skill will help define the scope, explore different UI/UX approaches, and produce a design document before any code is written.

Quick Start

Use the brainstorming skill to explore and design before implementing.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn ideas into approved design documents for new features?▼

To turn ideas into approved design documents, engage in exploratory dialogue to define scope, compare 2-3 distinct approaches with trade-offs, and commit a formal design document for user approval before implementation.

What is the best way to plan system designs and refactors before writing code?▼

The best way to plan system designs and refactors before coding is to enforce a no-code-before-design policy, challenging assumptions and comparing approaches to produce a committed design document requiring user approval.

How does a design review loop work for feature requirements and ideation?▼

A design review loop for feature requirements works by generating a formal design document, managing collaborative review with a sub-agent to challenge assumptions, and securing final user approval before proceeding.

Do I need to finalize requirements before starting design documentation?▼

You do not need to finalize requirements before starting design documentation; the process uses exploratory dialogue and context exploration to actively challenge assumptions and define requirements collaboratively.

Can I use this ideation process for both new features and system refactors?▼

Yes, you can use this ideation process for both new features and system refactors, as it facilitates context exploration and approach comparison to culminate in a committed design document for user approval.