brainstorming

Facilitate structured brainstorming sessions that produce a written design spec.

7|4|Updated Jun 7, 2025
One-click install
npx skills add https://github.com/lootlog/monorepo --skill brainstorming-lootlog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/lootlog/monorepo/tree/main/.agents/skills/brainstorming
Command: npx skills add https://github.com/lootlog/monorepo --skill brainstorming-lootlog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires chokidar, express, ws, and includes scripts (resource) components.

What problem does it solve?

Brainstorming for design projects is a guided process to capture goals, constraints, and success criteria before any implementation, reducing rework and misalignment.

Core Features & Use Cases

  • Explore project context and recent documentation to ground discussions.
  • Ask clarifying questions one at a time to refine scope and success criteria.
  • Propose 2-3 approaches with trade-offs and recommended direction.
  • Present design concepts and generate a formal design brief.
  • Write design docs and enable a spec-review loop for stakeholder alignment.
  • Transition from ideation to implementation planning with a clear next step.

Quick Start

Provide a topic and context, and I will guide you through a structured ideation and design-briefing flow.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I structure brainstorming sessions to capture design requirements?

Structured brainstorming sessions capture intent, requirements, and design decisions by gathering context, asking clarifying questions, and framing options to produce a written design spec. This grounding reduces rework and misalignment before implementation begins.

What is the best way to turn ideas into a formal design brief?

Turning ideas into a formal design brief involves exploring project context, proposing approaches with trade-offs, and presenting design concepts through an approval loop. This structured ideation generates written documentation aligning stakeholders on scope and success criteria.

How do I guide a team from ideation to implementation planning?

Transitioning from ideation to implementation planning requires a structured flow that captures goals and constraints, generates design docs, and enables a spec-review loop. This produces a clear next step for subsequent work with established guardrails.

Can I use structured ideation to align stakeholders before starting development?

Structured ideation aligns stakeholders before development by asking clarifying questions one at a time, proposing recommended directions, and enabling a spec-review loop. This process captures success criteria and constraints to ground subsequent implementation work.

Does this brainstorming process propose multiple design approaches with trade-offs?

The brainstorming process proposes two to three approaches with trade-offs and a recommended direction. This option framing occurs after context gathering and clarifying questions, leading into a design approval loop that produces a formal written specification.