From brainstorming-skills
Use before implementing features, building components, or modifying code behavior. Explores software design requirements, architecture, and technical constraints. For research hypothesis generation or experimental design, use scientific-brainstorming instead.
How this skill is triggered — by the user, by Claude, or both
Slash command
/brainstorming-skills:software-brainstormingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Help turn software ideas into fully formed designs and specs through natural collaborative dialogue.
Help turn software ideas into fully formed designs and specs through natural collaborative dialogue.
Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design in small sections (200-300 words), checking after each section whether it looks right so far.
Scope: This skill focuses on software engineering design (features, components, architecture, technical implementation). For scientific research ideation (hypotheses, experiments, methodologies), use scientific-brainstorming instead.
Understanding the idea:
Exploring approaches:
Presenting the design:
Documentation:
docs/plans/YYYY-MM-DD-<topic>-design.mdImplementation (if continuing):
npx claudepluginhub jaaaackielai/deep-learning-claude-code --plugin brainstorming-skillsYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.