brainstorming

Facilitate software project brainstorming through iterative questioning and design validation.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/dusk-time/tech-openclaw --skill brainstorming-dusk-time
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/dusk-time/tech-openclaw/tree/main/.continue/skills/brainstorming
Command: npx skills add https://github.com/dusk-time/tech-openclaw --skill brainstorming-dusk-time

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill facilitates the transition from ideas to fully formed designs, ensuring that projects are well-thought-out before implementation begins.

Core Features & Use Cases

  • Context Exploration: Understands the current project context by reviewing files and documentation.
  • Clarifying Questions: Refines the idea through structured, one-at-a-time questioning.
  • Approach Proposals: Presents 2-3 different design approaches with trade-offs.
  • Design Validation: Validates each section of the design iteratively.
  • Documentation: Encourages documentation of the final design for future reference.
  • Transition to Implementation: Provides a clear path to the next step, which is creating an implementation plan.
  • Use Case: Before starting a new feature, the 'brainstorming' skill helps gather requirements and define the scope of the project.

Quick Start

Start the brainstorming process for your new feature by invoking the skill and following the outlined steps.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I refine software project requirements before starting implementation?

A collaborative brainstorming process refines software project requirements by utilizing iterative questioning to explore context, propose multiple design approaches with trade-offs, and validate the project scope thoroughly before implementation begins.

What is the best way to transition an idea into a comprehensive software design?

Transitioning an idea into a comprehensive software design involves collaborative dialogue that clarifies requirements one question at a time, proposes distinct design approaches, and validates each section iteratively to ensure thorough exploration before development.

How does collaborative design dialogue work for new feature development?

Collaborative design dialogue works by reviewing existing project context and files, then asking structured clarifying questions sequentially to refine the idea, evaluate design trade-offs, and validate the architecture before creating an implementation plan.

Can I generate multiple design approaches with trade-offs for a feature?

Yes, you can generate multiple design approaches with trade-offs for a feature. The brainstorming process presents 2-3 different design options and validates each section iteratively to ensure comprehensive design coverage before development.

Do I need to document the final design before creating an implementation plan?

Yes, you need to document the final design for future reference. The brainstorming workflow encourages design documentation and provides a clear transition path to the subsequent step of creating an implementation plan.