brainstorming

Refine product ideas into validated design specifications through guided questioning.

4|1|Updated Jan 22, 2026

Search Tags:#planning #architecture #documentation #brainstorming #system design #requirements gathering #agentic workflows

Ready to run

npx skills add https://github.com/jordanhindo/Turtlez --skill brainstorming-jordanhindo

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming helps clarify ambiguous ideas into clear requirements and actionable design directions before any feature work begins.

Core Features & Use Cases

Intent & context discovery: Reviews the current project state (files/docs/recent changes) to ground decisions in what already exists.
Requirement refinement via focused questioning: Asks one question at a time, using multiple-choice options when helpful, to converge on purpose, constraints, and success criteria.
Design alternatives with trade-offs: Proposes 2–3 approaches, recommends a preferred path, and validates the emerging plan incrementally in sections.
Structured delivery: Produces a validated design spec and saves it to docs/plans/YYYY-MM-DD-<topic>-design.md for commit-ready documentation.

Quick Start

Use brainstorming to refine a product feature idea by asking a single clarifying question at a time, then produce a sectioned design spec saved under docs/plans/.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I turn vague product ideas into validated design specifications?▼

To turn vague product ideas into validated design specifications, guided questioning clarifies intent, requirements, and constraints before proposing 2-3 design alternatives with trade-offs for incremental validation.

What is the best way to clarify requirements for feature planning?▼

The best way to clarify requirements for feature planning is sequential one-question-at-a-time refinement, using multiple-choice options to converge on purpose, constraints, and success criteria.

How do I document system design alternatives with trade-offs?▼

Documenting system design alternatives involves proposing 2-3 approaches, recommending a preferred path, validating plans incrementally in sections, and saving the final spec to docs/plans/YYYY-MM-DD-<topic>-design.md.

Does this brainstorming approach work for existing codebases and documentation-heavy projects?▼

Yes, this brainstorming approach works for existing codebases and documentation-heavy projects by reviewing current project state, including files and recent changes, to ground decisions in what already exists.

Can I use guided questioning for component design and behavior changes?▼

Yes, you can use guided questioning for component design and behavior changes by refining ambiguous ideas into clear requirements and actionable design directions before any feature work begins.