development-brainstorming

Translate rough software ideas into actionable design specifications through guided questioning.

8|4|Updated Dec 15, 2025

Search Tags:#workflow #design #planning #architecture #brainstorming

Ready to run

npx skills add https://github.com/Jst-Well-Dan/Skill-Box --skill development-brainstorming

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: development-brainstorming
Source: https://github.com/Jst-Well-Dan/Skill-Box/tree/main/no-code-builder/development-brainstorming
Command: npx skills add https://github.com/Jst-Well-Dan/Skill-Box --skill development-brainstorming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plans software architecture and technical designs through guided, incremental questioning and exploring multiple approaches.

Core Features & Use Cases

One-question-at-a-time brainstorming to clarify purpose, constraints, and success criteria.
Present 2-3 design approaches with trade-offs and a recommended path.
Deliver the design in small sections with validation checks after each step.

Quick Start

Begin a brainstorming session to elicit requirements and converge on a design plan.

Frequently Asked Questions about development-brainstorming

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

FAQPage Schema

How do I translate software ideas into technical design specifications?▼

Design specifications translate rough ideas into actionable architecture through guided questioning that clarifies purpose, constraints, and success criteria, then presents multiple design approaches with trade-offs and a recommended path delivered in validated increments.

What's the best way to plan software architecture during development?▼

Plan architecture incrementally by asking one question at a time to elicit requirements, exploring 2-3 design approaches with their trade-offs, then delivering the design in small sections with validation checks after each step to refine decisions.

How do I explore multiple design approaches before committing to one?▼

Present competing design approaches by mapping alternatives with their trade-offs—performance vs. maintainability, complexity vs. scalability—then validate each step incrementally so decisions remain grounded in requirements and constraints.

Can I use design brainstorming to document architecture decisions?▼

Yes. Incremental design dialogue naturally produces documented outputs—component diagrams, data flows, and technical decisions—suitable for integration with project workflows like version control, documentation systems, and testing plans.

When should I start architecture planning in the development workflow?▼

Start planning during the initial software development phase when ideas are still rough. One-question-at-a-time brainstorming clarifies requirements and constraints before implementation, reducing rework and aligning team decisions early.

What's the difference between brainstorming design and just coding?▼

Design brainstorming separates planning from implementation by systematically exploring trade-offs and validating assumptions incrementally, resulting in deliberate architecture and documented decisions rather than emergent design during coding.