brainstorming

Convert ambiguous ideas into an approved design document before implementation.

7|2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/wenerme/ai --skill brainstorming-wenerme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/wenerme/ai/tree/main/skills/brainstorming
Command: npx skills add https://github.com/wenerme/ai --skill brainstorming-wenerme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents wasted engineering effort by forcing early alignment on intent, requirements, constraints, and success criteria before any implementation starts.

Core Features & Use Cases

  • Clarify project context: Review the current repository state (files, docs, and recent commits) to ground decisions in reality.
  • Ask one question at a time: Drive toward a clear understanding by collecting user-specific constraints and goals.
  • Propose and validate designs: Offer 2–3 approaches, present a structured design in sections, and require approval before proceeding.
  • Generate a design doc and move to planning: Save the validated design into docs/plans/YYYY-MM-DD-<topic>-design.md, then transition by invoking the writing-plans skill only after approval.

Quick Start

Ask the brainstorming skill to analyze your current project context, ask clarifying questions one at a time, propose 2–3 approaches, and present a design for approval before any implementation begins.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn ambiguous ideas into an approved design before building?

To turn ideas into an approved design, you must discover requirements, constraints, and success criteria through staged clarification. The process proposes 2-3 approaches, presents a structured design for user approval via validation gates, and saves documentation to docs/plans before implementation begins.

What is the best way to document product specs for feature development?

Documenting product specs works best by saving validated designs into docs/plans using a YYYY-MM-DD-<topic>-design.md filename. This captures repository context, requirements, trade-offs, and success criteria discovered during collaborative planning before implementation starts.

How do I ensure team alignment on requirements before implementation starts?

Ensuring team alignment on requirements requires asking one clarifying question at a time to collect user-specific constraints and goals. Presenting 2-3 design approaches with explicit trade-offs creates a validation gate where stakeholders must approve before proceeding.

Can I use collaborative planning for component creation and behavior changes?

Yes, collaborative planning applies to feature development, component creation, and behavior changes. It grounds decisions by reviewing current repository state including files, docs, and recent commits to validate requirements and constraints before implementation.

What happens after a design is approved in the brainstorming process?

After design is approved in the brainstorming process, the validated design is saved into a dated markdown file in docs/plans. The only next action is delegating to the writing-plans step to transition into downstream planning.