brainstorm

Turn rough ideas into validated design documents through structured dialogue.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/cjennings/rulesets --skill brainstorm-cjennings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/cjennings/rulesets/tree/main/brainstorm
Command: npx skills add https://github.com/cjennings/rulesets --skill brainstorm-cjennings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorms rough ideas into concrete, design-ready documents through structured dialogue, one-question-at-a-time exploration, and chunked validation.

Core Features & Use Cases

  • One-question-at-a-time dialogue to surface assumptions and options.
  • Diverse option exploration with three conventional + three tail samples.
  • Chunked validation (200-300 words per chunk) to progressively refine ideas.
  • Output artifact docs/design/<topic>.md representing the design document.
  • Use cases: Shaping a new feature, service, or workflow before implementation; clarifying ambiguous problems; validating feasibility before commit.

Quick Start

Begin by outlining the core idea, then proceed through the three phases to produce a design document at docs/design/<topic>.md.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I turn rough ideas into validated design documents?

Structured brainstorming surfaces assumptions through one-question-at-a-time dialogue, generates diverse options including conventional and tail samples, and validates feasibility chunk by chunk before committing to implementation.

How do I structure a design doc for early-stage feature ideation?

The brainstorming workflow outputs a structured design document at docs/design/<topic>.md, utilizing frontmatter to define the topic and enforcing a phased dialogue to shape the content.

Can I use chunked validation for ambiguous problem clarification?

Chunked validation refines ambiguous problems by validating ideas in 200-300 word chunks, ensuring that diverse options and assumptions are tested progressively before producing the final design document.

What is the best way to explore diverse options during workflow ideation?

Generating three conventional and three tail samples provides a broad spectrum of solutions, ensuring the resulting design document accounts for both standard implementations and edge-case scenarios.

Does brainstorming ideation require any specific dependencies or frameworks?

The ideation and validation process relies on a self-contained phased workflow with no dependencies, guiding users from an initial rough idea to a structured design document output.