sdd:brainstorm

Help turn ideas into fully formed designs and specs through natural collaborative dialogue.

neolabhq/context-engineering-kit|Updated Apr 8, 2026

Works with

Claude CodeCursorClineWindsurfCodexGoose

Installation Guide

Select your AI agent

How to use sdd:brainstorm on Cursor

AI-first code editor with Composer

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

›Cursor installed and configured on your machine
›Node.js 16+ with npm — verify with node --version
›Active project directory where you want to add sdd:brainstorm

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/neolabhq/context-engineering-kit --skill sdd:brainstorm

Fetches sdd:brainstorm from neolabhq/context-engineering-kit and configures it for Cursor.

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?

│

│ ── Universal (.agents/skills) ────────────────

│ · Cline · Codex · Goose · Windsurf

│ ●Cursor(selected)

│ · Cursor · Aider · Continue

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/sdd:brainstorm

Restart Cursor to activate sdd:brainstorm. Access via /sdd:brainstorm in your agent's command palette.

⚠

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

›View source on GitHub ›Skills CLI docs ›About Cursor ›What are agent skills?

Documentation

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

✓

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

✓

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

✓

Improve work quality by 30-40% with less effort

Overview

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.

The Process

Understanding the idea:

Check out the current project state first (files, docs, recent commits)

Ask questions one at a time to refine the idea

Prefer multiple choice questions when possible, but open-ended is fine too

Only one question per message - if a topic needs more exploration, break it into multiple questions

Focus on understanding: purpose, constraints, success criteria

Exploring approaches:

Generate 6 possible approaches with trade-offs. Approaches should each include a text and a numeric probability. Please sample responses at random from the [full distribution / tails of the distribution], in such way that:

For first 3 responses aim for high probability, over 0.80
For last 3 responses aim for diversity - explore different regions of the solution space, such that the probability of each response is less than 0.10

Present options conversationally with your recommendation and reasoning

Lead with your recommended option and explain why

Presenting the design:

Once you believe you understand what you're building, present the design

Break it into sections of 200-300 words

Ask after each section whether it looks right so far

Cover: architecture, components, data flow, error handling, testing

Be ready to go back and clarify if something doesn't make sense

After the Design

Documentation:

Write the validated design to .specs/plans/<topic>.design.md

Use docs:write-concisely skill if available

Commit the design document to git

Implementation (if continuing):

Ask: "Ready to set up for implementation?"

Use git:create-worktree to create isolated workspace

Use sdd:add-task to create task file for target approach

Key Principles

One question at a time - Don't overwhelm with multiple questions

Multiple choice preferred - Easier to answer than open-ended when possible

YAGNI ruthlessly - Remove unnecessary features from all designs

Explore alternatives - Always propose 2-3 approaches before settling

Incremental validation - Present design in sections, validate each

Be flexible - Go back and clarify when something doesn't make sense

sdd:brainstorm

Installation Guide

How to use sdd:brainstorm on Cursor

Prerequisites

Run the install command

Select Cursor when prompted

Verify installation

Security Notice

Documentation

List & Monetize Your Skill

Use Cases

Task Automation & Efficiency

Knowledge Enhancement

Quality Improvement

Install Skill

Brainstorming Ideas Into Designs

Overview

The Process

After the Design

Key Principles

Implementation Guide

Best Practices

When to Use This

Learning Path

Related Skills

ddd:software-architecture

ml-paper-writing

beautiful-mermaid

llm-council

blockchain-developer

dokie-ai-ppt

Reviews

Discussion