brainstorming

Guide one-question-at-a-time questioning to transform ideas into validated design sections.

Updated Nov 3, 2025
One-click install
npx skills add https://github.com/ayourtch/kimichat --skill brainstorming-ayourtch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/ayourtch/kimichat/tree/main/skills/brainstorming
Command: npx skills add https://github.com/ayourtch/kimichat --skill brainstorming-ayourtch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solves? This Skill transforms vague ideas into fully-formed, validated designs and specifications, preventing premature coding and ensuring a clear understanding of requirements.

Core Features & Use Cases

  • Collaborative Questioning: Refines ideas through one-at-a-time questions, preferring multiple-choice when possible, to clarify purpose and constraints.
  • Alternative Exploration: Proposes 2-3 different approaches with trade-offs, leading with a recommendation and its reasoning.
  • Incremental Design Validation: Presents design in small sections (200-300 words) for continuous feedback, ensuring alignment at each stage.
  • Use Case: When a user provides a high-level idea like "build a new reporting feature," use this skill to ask clarifying questions, explore architectural options, and incrementally present a detailed design.

Quick Start

I'm using the brainstorming skill to refine the idea for the new user-onboarding flow.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn rough ideas into actionable designs before coding?

Brainstorming transforms vague concepts into fully-formed designs through collaborative questioning, exploration of 2-3 approaches with trade-offs, and incremental validation in small sections. This prevents premature coding and ensures clear requirements before implementation begins.

What's the best way to explore different architectural approaches early in a project?

Present multiple design approaches with explicit trade-offs and reasoned recommendations. This comparative exploration during early scoping clarifies constraints, reveals options, and builds team alignment before committing to a single direction.

How do I gather requirements and validate design decisions incrementally?

Use one-at-a-time collaborative questioning, preferring multiple-choice formats to refine scope. Present designs in 200-300 word sections with validation prompts after each, ensuring stakeholder feedback shapes the artifact continuously.

When should I apply design questioning to product development?

Apply during early project scoping, context gathering, and feature or architecture design phases. This prevents misalignment and rework by establishing shared understanding of purpose and constraints before detailed implementation planning.

Can I document and version design artifacts alongside code?

Yes. Design outputs integrate with git-based versioning, allowing design specifications and code to evolve together with full change history and team collaboration tracking from project inception onward.