brainstorming

Refines feature ideas into validated design documents through structured dialogue.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/singhaganesh/Urban-assist --skill brainstorming-singhaganesh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/singhaganesh/Urban-assist/tree/main/.cursor/skills/brainstorming
Command: npx skills add https://github.com/singhaganesh/Urban-assist --skill brainstorming-singhaganesh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Jumping straight into implementation without clarifying requirements leads to rework and misaligned features. This Skill guides a structured conversation that turns a rough idea into a validated design before any code is written. ## Core Features & Use Cases - One-question-at-a-time discovery: Explores purpose, constraints, and success criteria through focused questions, preferring multiple choice when possible. - Approach comparison: Proposes 2-3 alternative approaches with trade-offs and a clear recommendation before settling on a direction. - Incremental design validation: Presents the design in 200-300 word sections covering architecture, components, data flow, error handling, and testing, confirming each section before continuing. - Use Case: Before building a new booking feature, use this Skill to clarify requirements, compare architectural options, and produce a design document saved to docs/plans/ for the implementation phase. ## Quick Start Ask the assistant to brainstorm and design a new feature before implementing it, describing your rough idea in one or two sentences.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn a feature idea into a design before coding?

Start a brainstorming session that asks clarifying questions one at a time, proposes 2-3 approaches with trade-offs, then presents the design in small validated sections. The confirmed design is written to docs/plans/ as a dated Markdown file.

When should I use brainstorming before implementation?

Use it before any creative work such as creating features, building components, adding functionality, or modifying behavior. It ensures requirements, constraints, and success criteria are understood before writing code.

What does the brainstorming design document include?

The design covers architecture, components, data flow, error handling, and testing. It is presented in 200-300 word sections for incremental validation, then saved to docs/plans/YYYY-MM-DD-topic-design.md and committed to git.

Can brainstorming skip straight to implementation?

No, the process requires exploring intent and validating the design first. After the design is approved, it optionally hands off to worktree setup and implementation planning skills for the build phase.

What are the limitations of a dialogue-based design process?

It depends on user availability to answer questions and validate each section, so it is slower than direct coding for trivial changes. It is best suited for non-trivial features where misalignment would be costly.