brainstorming

Refine vague ideas into user-approved designs through structured collaborative questioning.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/ahsanghalib/ai-workflow --skill brainstorming-ahsanghalib
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/ahsanghalib/ai-workflow/tree/main/skills/brainstorming
Command: npx skills add https://github.com/ahsanghalib/ai-workflow --skill brainstorming-ahsanghalib

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump into implementation before an idea, feature, or change request is clearly defined, leading to rework and misaligned outcomes. This Skill turns an incomplete idea into a clear, user-approved direction through focused conversation before any code is written. ## Core Features & Use Cases - Request Classification: Sorts each request into Spike, Bounded, or Architectural paths so the design effort matches the actual complexity. - Focused Questioning: Asks one material question at a time about purpose, constraints, success criteria, and non-goals, separating confirmed facts from assumptions. - Approval-Gated Design: Presents a scaled design brief with trade-offs and validation strategy, then waits for explicit user approval before any implementation. - Use Case: A user says "we should add notifications to the app." The Skill classifies the request, asks targeted questions about users and success criteria, compares two or three approaches, and produces an approved design brief that hands off cleanly to technical design or implementation workflows. ## Quick Start Ask the assistant to brainstorm and refine your feature idea into an approved design before writing any code.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn a vague feature idea into an approved design?▼

Start a brainstorming session that classifies the request as a spike, bounded change, or architectural effort. The process asks one focused question at a time about goals, constraints, and success criteria, then presents a design brief for explicit approval before implementation.

What is the difference between spike, bounded, and architectural requests?▼

A spike answers a feasibility question with a disposable probe. A bounded request is a small, well-scoped change handled with a short in-chat design. An architectural request involves new subsystems or cross-cutting interfaces and uses the fuller design process.

When should I not use brainstorming for a request?▼

Avoid it for focused product discovery, repository-grounded technical design, UI design, delivery planning, debugging, or direct implementation. Those belong to specialist workflows such as product-discovery, technical-design, frontend-design, or project-init.

Does design approval allow the assistant to start coding?▼

No. Approval of the design only confirms the direction. Implementation, commits, publishing, and other consequential actions each require separate user authorization and the applicable engineering workflow.

What happens after a brainstorming design is approved?▼

Bounded work proceeds to an engineering workflow with test-driven development when a behavior seam exists. Architectural work hands off to technical-design, frontend-design, or product-discovery, and project-init when durable dependency-ordered tasks are needed.