skills.rest
AarushiShah
AarushiShahCOMMUNITY
Explore all skills by this author →
GitHub

brainstorming

Refines feature ideas into validated design documents through structured dialogue.

Updated Mar 24, 2026
Search Tags:#brainstorming#software design#specification#requirements#feature planning#design document
One-click install
npx skills add https://github.com/AarushiShah/coding-agents-databricks-apps --skill brainstorming-aarushishah
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/AarushiShah/coding-agents-databricks-apps/tree/main/.claude/skills/brainstorming
Command: npx skills add https://github.com/AarushiShah/coding-agents-databricks-apps --skill brainstorming-aarushishah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Jumping straight into coding without a clear design leads to rework, scope creep, and misaligned features. This Skill turns vague ideas into fully formed, validated designs and specs before any implementation begins. ## Core Features & Use Cases - Guided Requirement Discovery: Explores user intent through one focused question at a time, preferring multiple-choice formats to reduce friction. - Approach Comparison: Proposes 2-3 alternative approaches with trade-offs and a reasoned 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 dashboard feature, use this Skill to clarify requirements, compare architectural approaches, and produce a committed design document at docs/plans/YYYY-MM-DD-topic-design.md. ## Quick Start Ask the agent to brainstorm and design a new feature before writing any code, describing the idea you want to explore.

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 document before coding?▼

Start a brainstorming session that explores your intent through one question at a time, compares 2-3 approaches with trade-offs, then presents the design in validated sections. The final design is written to docs/plans/ and committed to git.

When should I use brainstorming before implementing a feature?▼

Use it before any creative work: creating features, building components, adding functionality, or modifying behavior. It clarifies purpose, constraints, and success criteria so implementation starts from a validated design rather than assumptions.

What does the brainstorming design process cover?▼

The design covers architecture, components, data flow, error handling, and testing. Each section is presented in 200-300 word chunks and validated with you before moving to the next.

Can brainstorming skip straight to implementation?▼

No, the process requires exploring requirements and validating the design first. After validation, it optionally hands off to implementation using git worktrees and a detailed written plan.

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

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

Related Skills

Explore More Software Engineering Skills→
wtyler2505wtyler2505
1

resume

Rebuild session context from memory, recent files, git state, and tasks.

Community
Intermediate
tunneleventunneleven

executing-plans

Execute step-by-step software development plans with verification and git worktrees.

Community
Intermediate
KevinKE93KevinKE93
42

documentation-and-adrs

Record architectural decisions and supporting documentation for future engineers and AI agents.

Community
Intermediate
farzanmrzfarzanmrz
6

doubt-driven-development

Automates adversarial fresh-context review of artifacts before finalizing decisions.

Community
Advanced