brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Why use this skill?
Use the OpenClaw brainstorming skill to transform ideas into professional design docs. Features automated scoping, design exploration, and iterative validation.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/zlc000190/brainstormingWhat This Skill Does
The brainstorming skill serves as the foundational architectural framework for the OpenClaw AI agent. It acts as a mandatory pre-development layer designed to translate raw user concepts into structured, actionable engineering specifications. By enforcing a rigorous process of requirement gathering, design alternative exploration, and incremental validation, this skill minimizes rework and ensures that all subsequent development aligns strictly with user intent and project constraints. It follows a structured methodology of questioning, proposing multiple design paths, and presenting detailed documentation in digestible, validated sections.
Installation
To integrate the brainstorming skill into your environment, run the following command in your terminal:
clawhub install openclaw/skills/skills/zlc000190/brainstorming
Ensure you have the latest version of the OpenClaw CLI initialized in your project directory before installation.
Use Cases
- Feature Specification: Ideal for scoping out new complex features or UI components to ensure architectural fit.
- Refactoring Projects: Use this when planning a major codebase restructuring to evaluate trade-offs between different implementation patterns.
- Technical Debt Mitigation: When deciding how to replace legacy modules, this skill helps in comparing modern approaches and choosing the most efficient path.
- New Module Development: Perfect for laying the groundwork for internal libraries or system utilities where design decisions have long-term impacts.
Example Prompts
- "I want to add a real-time notification system to the dashboard. Let's brainstorm the approach."
- "We need to refactor the authentication flow to support SSO. Help me design the new architecture."
- "I'm considering switching our database abstraction layer. Can we explore the design implications of this change?"
Tips & Limitations
- Strict Adherence: The skill is designed to be pedantic about process. Do not attempt to bypass the question-and-answer phases; they are critical for alignment.
- YAGNI Compliance: The AI is instructed to be ruthless about "You Ain't Gonna Need It." If you propose unnecessary complexity, expect the agent to challenge you to simplify the scope.
- Incremental Review: Always commit to validating the design sections as they are presented. Moving too fast without confirmation can lead to architectural drift.
- Limitations: This skill does not write code itself; it produces the technical plans. It requires the developer to be active in providing context about the current system state.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-zlc000190-brainstorming": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-read, file-write
Related Skills
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always