brainstorming

Name: brainstorming
Availability: InStock
Author: axiomantic

Generate design documents and approach decisions from vague feature ideas.

8|5|Updated Dec 30, 2025

Search Tags:#planning #architecture #brainstorming #collaboration #ideation #design-document

Ready to run

npx skills add https://github.com/axiomantic/spellbook --skill brainstorming-axiomantic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/axiomantic/spellbook/tree/main/skills/brainstorming
Command: npx skills add https://github.com/axiomantic/spellbook --skill brainstorming-axiomantic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming early-stage ideas and turning vague concepts into structured design directions can be time-consuming and error-prone. This skill streamlines ideation by guiding the team to concrete outputs ready for evaluation.

Core Features & Use Cases

Structured ideation: generate 2-3 viable design approaches with trade-offs and rationale.
Context-driven: tailor suggestions based on context.feature_idea, context.constraints, and context.existing_patterns.
Output-ready: produce a design_document plan stored under ~/.local/spellbook/docs/<project>/plans/YYYY-MM-DD-<topic>-design.md and an inline approach_decision summary.

Quick Start

Describe your feature idea and any constraints to generate a design document and recommended approach.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I turn vague feature ideas into a concrete design document?▼

To turn vague feature ideas into a concrete design document, provide your feature concept and constraints to generate 2-3 viable design approaches with trade-offs, an approach decision, and an implementation readiness status.

What is the best way to structure early-stage architecture planning and ideation?▼

The best way to structure architecture planning is to generate a design document that evaluates multiple design approaches against existing patterns and constraints, producing a rationale-backed approach decision for your project.

How do I generate design approaches with trade-offs for feature scoping?▼

To generate design approaches with trade-offs for feature scoping, input your feature idea and existing patterns. The system drafts 2-3 viable directions with rationale and sets an implementation_ready flag.

Can I tailor design directions based on specific project constraints and existing patterns?▼

Yes, you can tailor design directions by providing context constraints and existing patterns. The ideation process uses these inputs to generate context-driven suggestions and a design document stored locally.

Where are the generated design document plans stored on my system?▼

Generated design document plans are stored as markdown files locally at the specified path ~/.local/spellbook/docs/<project>/plans/YYYY-MM-DD-<topic>-design.md, alongside an inline approach decision summary.

When should I avoid automated ideation for design planning?▼

You should avoid automated ideation when your feature idea lacks sufficient context or constraints, as the tool relies on context.feature_idea and context.constraints to draft viable design approaches and set implementation readiness.