brainstorming

Organize six-step brainstorming sessions that generate traceable specs and docs/brainstorms.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/JayJihyunKim/rein --skill brainstorming-jayjihyunkim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/JayJihyunKim/rein/tree/main/plugins/rein-core/skills/brainstorming
Command: npx skills add https://github.com/JayJihyunKim/rein --skill brainstorming-jayjihyunkim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

rein-native brainstorming helps turn ideation into a concrete spec within existing codebase and architecture constraints. brownfield requires validating feasibility and compatibility before options converge, while greenfield uses a light question set to quickly converge intent.

Core Features & Use Cases

  • Brownfield gatekeeping validates feasibility and compatibility before options converge.
  • Greenfield fast intent capture uses a light question set to converge intent quickly.
  • Documentation linkage records brainstorm outputs to docs/brainstorms/ and references brainstorm ref: in spec.

Quick Start

Provide your idea, specify brownfield or greenfield context, and initiate the brainstorm to produce a converged direction and a draft spec.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn brainstorming ideas into a concrete spec under existing system constraints?

Structured brainstorming converts ideation into a traceable spec by enforcing a Step 0–6 workflow that validates feasibility against real codebase constraints before converging options into draft documentation.

What's the best way to brainstorm features for a brownfield codebase?

Brownfield brainstorming requires gatekeeping validation to check feasibility and compatibility within the existing architecture before allowing options to converge into a final spec.

How do I quickly capture and document intent for a greenfield project?

Greenfield brainstorming uses a light question set to rapidly converge project intent, followed by automatic generation of brainstorm records and draft specs for immediate use.

Does this brainstorming workflow automatically link outputs to project documentation?

Brainstorming documentation linkage automatically records outputs to the docs/brainstorms/ directory and references the brainstorm ref: within the generated spec for traceability.

Can I use codex-ask validation to check brainstorming directions before committing?

Codex-ask validation is enforced during the structured workflow to verify brainstorming directions, ensuring that feasibility checks pass before a converged direction generates final documentation.

What are the limitations of structured brainstorming for spec generation?

Structured brainstorming requires strict adherence to a Step 0–6 workflow and codex-ask validation, meaning users must complete the full convergence process before automatic spec documentation is generated.