skills.rest
stevengonsalvez
stevengonsalvezCOMMUNITY
Explore all skills by this author →
GitHub

brainstorm

Turn vague ideas into a structured spec.md with iterative questioning.

Updated Apr 10, 2026
Search Tags:#architecture#requirements#spec#brainstorm#product-management#use-cases#iterative-questioning
One-click install
npx skills add https://github.com/stevengonsalvez/nanoclaw-standalone --skill brainstorm-stevengonsalvez
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/stevengonsalvez/nanoclaw-standalone/tree/main/container/skills/brainstorm
Command: npx skills add https://github.com/stevengonsalvez/nanoclaw-standalone --skill brainstorm-stevengonsalvez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorm sessions often stall without a concrete, shareable specification. This Skill guides you from vague ideas to a structured spec that teams can implement.

Core Features & Use Cases

  • Iterative clarification: Ask one clarifying question at a time and build on previous answers.
  • Structured spec generation: Produce sections like problem statement, goals, use cases, functional requirements, architecture overview, data models, testing, and deployment.
  • GitHub repository readiness: Optionally generate a spec.md and assist with initial repo setup.

Quick Start

Describe your idea to start, and the tool will guide you to a complete, iterative spec.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I turn a vague product idea into a structured spec?▼

To turn a vague idea into a structured spec, describe your concept to initiate an iterative questioning process that refines input and generates a document with goals, use cases, and architecture.

Can I generate a spec.md file ready for a GitHub repository?▼

Yes, you can generate a spec.md file for GitHub repository readiness, producing a reusable specification document containing problem statements, functional requirements, and testing sections.

What is the best way to document functional requirements for a new feature?▼

The best way to document functional requirements is through iterative clarification, asking one question at a time to build on previous answers and produce a comprehensive specification.

Does this brainstorming process include architecture and data models?▼

Yes, the brainstorming process includes architecture overviews and data models within the generated specification, ensuring teams have the technical structure needed for implementation.

How do I write use cases for product management workflows?▼

You write use cases by providing an initial idea, which triggers an iterative questioning process that refines the workflows and outputs a structured spec document with dedicated use case sections.

Related Skills

Explore More Product & Management Skills→
thmspithmspi

brainstorming

Organize raw ideas into actionable design concepts with structured inquiry.

Community
Advanced
MartinoPoloMartinoPolo
1

mpx-init-repo

Initialize a Git repository with .gitignore and Claude Code templates.

Community
Intermediate
nobelknobelk

prd-to-design-doc

Convert Product Requirements Documents into RFC-style Developer Design Documents.

Community
Advanced
mazreanmazrean

writing-technical-design

Generate technical design documents with progressive disclosure across context layers.

Community
Advanced