Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
69
84%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
The canonical home for this skill is brainstorm in NeoLabHQ/context-engineering-kit
Help turn 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.
Understanding the idea:
Exploring approaches:
Presenting the design:
if user provided draft specification file, then update it directly, if not then use /add-task skill to create task file for target approach
Important: In specification file, write target approach in sections, in ## Initial User Prompt -> ### Requirements section, before ## Description section. Description will be filled in future stage.
After filling task file, suggest use to run /clear and then /plan-task <task-file-path> to refine the task file.
23e2428
Canonical home
since May 4, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.