brainstorming

Turn vague ideas into validated design plans with structured inquiry and approval.

Updated Aug 20, 2022
One-click install
npx skills add https://github.com/Neroro64/dotfiles --skill brainstorming-neroro64
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/Neroro64/dotfiles/tree/main/configs/omp/agent/skills/brainstorming
Command: npx skills add https://github.com/Neroro64/dotfiles --skill brainstorming-neroro64

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Brainstorming enables teams to translate vague ideas into concrete design directions by clarifying goals, constraints, and success criteria before any implementation work begins.

Core Features & Use Cases

  • Guided context assessment: analyze project context, stakeholders, and goals.
  • Iterative design exploration: present 2-3 design approaches with trade-offs and recommendations.
  • Design documentation: produce a design doc and prepare for a spec-review loop before implementation.
  • Collaboration and approvals: gather user feedback and obtain explicit approval before moving to implementation.

Quick Start

Start by understanding the current project context, then ask one clarifying question at a time, propose 2–3 design approaches, and present the design for user approval.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn vague ideas into structured design documentation?

To turn vague ideas into structured design documentation, you analyze project context and stakeholders. This process clarifies goals and constraints, producing validated design plans and formal documentation before implementation begins.

What is the best way to conduct requirement clarification for a new project?

The best way to conduct requirement clarification is through structured inquiry, asking one question at a time. This intent discovery method ensures goals and constraints are fully defined before proposing multi-option design approaches.

How do I explore multiple design approaches before starting implementation?

You explore multiple design approaches by generating 2-3 options with detailed trade-offs. This iterative design exploration allows teams to compare directions and select a validated plan before transitioning to implementation.

Can I use this for architecture planning and stakeholder collaboration?

Yes, you can use this for architecture planning and stakeholder collaboration. It applies to projects requiring intent discovery and design documentation, gathering feedback to obtain explicit approval before moving to implementation.

How do I get design approval before moving to implementation?

You get design approval by presenting a formal design doc and entering a spec-review loop. This gathers user feedback and ensures explicit approval, creating an approval-based transition to implementation.