brainstorming

Guide software ideas through structured brainstorming into approved design specifications.

Updated Mar 3, 2026

Search Tags:#design #architecture #brainstorming #feature development #requirements #software planning

Ready to run

npx skills add https://github.com/zinohome/zinoClaw --skill brainstorming-zinohome

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/zinohome/zinoClaw/tree/main/docker-customize/deskclaw-resources/skills/brainstorming
Command: npx skills add https://github.com/zinohome/zinoClaw --skill brainstorming-zinohome

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents premature implementation by helping teams clarify goals, requirements, constraints, and design decisions before building software changes.

Core Features & Use Cases

Collaborative Discovery: Guides users through project context review and focused questions to understand the intended outcome.
Design Exploration: Compares multiple approaches, evaluates trade-offs, and creates a validated design before implementation begins.
Use Case: A developer planning a new feature can use this Skill to turn an initial idea into an approved specification with clear architecture, scope, and next steps.

Quick Start

Use the brainstorming skill to help me design a new feature by exploring requirements, proposing approaches, and creating a design plan.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I turn feature ideas into approved software design specifications?▼

To turn feature ideas into approved design specifications, structured brainstorming guides context exploration, requirement clarification, approach comparison, and architectural decision documentation before implementation begins.

What is the best way to plan software architecture before starting development?▼

Planning software architecture is best achieved through collaborative discovery, which evaluates project context, compares multiple design approaches, and validates trade-offs to create an approved specification with clear scope and next steps.

How do I clarify requirements and discover constraints for component design?▼

To clarify requirements and discover constraints for component design, navigate a sequential workflow of focused questions that explore project context and intended outcomes to validate the design approach.

Can I use this approach for planning behavior changes in existing software?▼

Yes, you can use this approach for planning behavior changes, as it applies to feature planning, component design, and projects requiring requirement discovery and architectural decisions to prevent premature implementation.

Why do I need to compare multiple approaches before implementing a new feature?▼

Comparing multiple approaches during design exploration prevents premature implementation by evaluating trade-offs and ensuring the selected architecture is validated against goals, constraints, and requirements before development starts.