brainstorming

Guide design brainstorming sessions to produce formal specifications for approval.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/djwmobley/pipeline --skill brainstorming-djwmobley
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/djwmobley/pipeline/tree/main/skills/brainstorming
Command: npx skills add https://github.com/djwmobley/pipeline --skill brainstorming-djwmobley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming helps teams clarify goals, constraints, and design direction before any implementation, reducing misaligned work and rework later.

Core Features & Use Cases

  • Explore project context and engagement style to tailor the design approach.
  • Ask clarifying questions one at a time to refine scope and requirements.
  • Derive implied features, present 2-3 approach options, and secure user approval before proceeding.
  • Write a formal spec and track TBDs to keep the plan aligned with user intent.

Quick Start

Provide a brief project goal and constraints to begin a design-first brainstorming session.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I convert project ideas into vetted design specifications before coding?

To convert project ideas into design specifications, you provide a brief project goal and constraints to initiate a design-first brainstorming session. The session asks clarifying questions one at a time to refine scope and validates intent before proceeding.

What is the best way to scope features and make architecture decisions during project inception?

Scoping features and making architecture decisions is best handled by deriving implied features and proposing 2-3 approach options for review. This enforces a hard-gate design discipline to secure user approval before moving forward with implementation.

How do I run a design-focused brainstorming session for a new software project?

Running a design-focused brainstorming session involves exploring project context and engagement style to tailor the approach. It then systematically asks clarifying questions, derives implied features, and presents a formal spec for review while tracking TBDs.

Can I use this to validate requirements and enforce a hard-gate design discipline?

Yes, you can validate requirements and enforce a hard-gate design discipline. The session secures user approval on proposed approaches before proceeding, ensuring aligned work and reducing rework later.

Does the brainstorming process generate a formal spec and track TBDs for design review?

Yes, the brainstorming process generates a formal spec and tracks TBDs for design review. This documentation keeps the plan aligned with user intent and optionally triggers a plan phase once the design is approved.