brainstorming

Convert ambiguous ideas into concrete designs through iterative dialogue in 200–300 word sections.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/cncorp/arsenal --skill brainstorming-cncorp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/cncorp/arsenal/tree/main/dot-claude/skills/brainstorming
Command: npx skills add https://github.com/cncorp/arsenal --skill brainstorming-cncorp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps turn ideas into designs and specs through collaborative dialogue, iterating in small sections.

Core Features & Use Cases

  • Guided ideation: one question at a time, 200-300 word design chunks.
  • Trade-off exploration: present 2-3 approaches with pros/cons.
  • Incremental validation: validate design in sections.

Quick Start

Start brainstorming with a topic, then proceed to design phases incrementally.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn a vague product idea into a concrete design specification?

Collaborative ideation converts ambiguous ideas into concrete designs through guided dialogue. This Skill asks clarifying questions one at a time, explores 2–3 design approaches with trade-offs, and delivers designs incrementally in 200–300 word sections to validate fit before proceeding further.

What's the best way to plan software architecture when starting from scratch?

Architecture planning benefits from iterative refinement through structured dialogue. This approach presents multiple design directions with pros and cons, validates each section with stakeholders, and enforces DRY principles to avoid redundant decisions and inconsistent patterns across the architecture.

How do I validate feature specifications before building them?

Feature specification works best through incremental validation after each design section. The Skill checks understanding and alignment with requirements after delivering each 200–300 word chunk, catching mismatches early and reducing rework during development.

Can I use this approach to compare different design directions for the same problem?

Yes. The Skill presents 2–3 alternative approaches with explicit trade-offs, letting you weigh technical, cost, and complexity factors. This comparative exploration helps teams select the best direction before committing resources to implementation.

Do I need to search for existing implementations before designing a feature?

Yes. The Skill runs semantic search for existing implementations before proposing designs, avoiding reinvention and surfacing proven patterns. This prerequisite step informs which approaches are most practical and where novel solutions add genuine value.