brainstorming

Convert vague concepts into concrete design specifications through guided questions.

Updated Mar 11, 2023
One-click install
npx skills add https://github.com/viktorvan/dot-files --skill brainstorming-viktorvan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/viktorvan/dot-files/tree/main/opencode/skill/brainstorming
Command: npx skills add https://github.com/viktorvan/dot-files --skill brainstorming-viktorvan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming ideas into designs solves the problem of converting vague concepts into concrete design specifications, fostering clear direction and shared understanding among stakeholders.

Core Features & Use Cases

  • Guided ideation: one-question-at-a-time prompts to refine ideas and derive actionable requirements.
  • Incremental design: present architecture and components in 200-300 word sections for focused feedback.
  • Exploration of alternatives: propose 2-3 approaches with trade-offs before committing to a path.
  • Collaborative review: structure reviews to validate purpose, constraints, and success criteria with each iteration.
  • Use Case: for a new feature in a product, start from context, ask clarifying questions, and deliver a structured design proposal ready for implementation.

Quick Start

Brainstorm a new feature by reviewing the current project context, ask one focused question at a time, and present the design in 200-300 word sections for iterative feedback.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn vague product ideas into concrete design specifications?

Guided brainstorming refines vague ideas by asking one clarifying question at a time, exploring 2-3 alternative approaches with trade-offs, and validating constraints iteratively before committing to a design path.

What is the best way to structure architecture and component designs for collaborative review?

The best way to structure architecture designs for collaborative review is presenting them in incremental 200-300 word sections, enabling focused feedback on purpose, constraints, and success criteria at each iteration.

How does incremental design validation work for early-stage product initiatives?

Incremental design validation works by breaking down architecture, data flow, error handling, and testing into 200-300 word sections, allowing stakeholders to validate each part progressively before moving forward.

Can I use guided ideation to document trade-offs for multiple design approaches?

Yes, guided ideation supports documenting trade-offs by proposing 2-3 alternative approaches before committing to a path, ensuring structured exploration of constraints and success criteria during early-stage design.

Does brainstorming requirements analysis help with outlining error handling and testing?

Yes, brainstorming requirements analysis helps outline error handling and testing by progressively detailing architecture, components, and data flow in focused sections to deliver a structured design proposal ready for implementation.