brainstorm

Guide abstract ideas into detailed design specifications through structured questioning.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/paxtone-studio/openkodo --skill brainstorm-paxtone-studio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/paxtone-studio/openkodo/tree/main/plugins/kodo/skills/brainstorm
Command: npx skills add https://github.com/paxtone-studio/openkodo --skill brainstorm-paxtone-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill transforms vague ideas into concrete, implementable designs through structured dialogue, ensuring clarity and alignment before development begins.

Core Features & Use Cases

  • Structured Questioning: Guides users through clarifying questions to define requirements.
  • Iterative Design: Proposes and refines design approaches based on user feedback.
  • Design Documentation: Automatically generates and saves design documents.
  • Use Case: Kick off a new feature by using this Skill to explore user intent, define requirements, and collaboratively decide on the best architectural approach before writing any code.

Quick Start

Use the brainstorm skill to explore the idea of a new user authentication flow.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I turn abstract ideas into concrete design specifications before development?

To turn abstract ideas into concrete design specifications, use a structured, question-driven dialogue to define requirements and explore architectural approaches incrementally. This ensures alignment and validates design decisions before implementation begins.

What is the best way to collaboratively brainstorm architectural approaches for a new feature?

The best way to collaboratively brainstorm architectural approaches is through iterative design proposals refined by user feedback. This method proposes, adjusts, and documents architectural decisions incrementally to ensure team alignment.

How do I structure requirements gathering to ensure clarity before writing code?

Structure requirements gathering by using a guided questioning process to clarify user intent and define exact needs. This approach ensures full clarity and alignment before any code is written.

Can I automatically generate design documentation while exploring software requirements?

Yes, you can automatically generate and save design documentation while exploring software requirements. As you define requirements through dialogue, the design documents are incrementally recorded and updated.

When should I use an iterative design process instead of immediately implementing a solution?

Use an iterative design process when you have vague ideas that need transformation into concrete, implementable designs. It ensures clarity, validates architectural approaches, and secures alignment before development begins.