skills.rest
zhu327
zhu327COMMUNITY
Explore all skills by this author →
WebsiteGitHub

brainstorming

Clarifies ambiguous feature requests into validated design specifications through structured questioning and incremental review.

2|Updated Aug 4, 2025
Search Tags:#design#planning#architecture#brainstorming#requirements
One-click install
npx skills add https://github.com/zhu327/go-clean-arch --skill brainstorming-zhu327
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/zhu327/go-clean-arch/tree/main/.cursor/skills/brainstorming
Command: npx skills add https://github.com/zhu327/go-clean-arch --skill brainstorming-zhu327

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you shape an unclear idea into a concrete design before implementation starts, reducing rework and missed requirements.

Core Features & Use Cases

  • Requirements discovery: Ask structured questions to clarify goals, constraints, and success criteria.
  • Option comparison: Present 2-3 approaches with trade-offs and a recommendation.
  • Incremental design review: Break the solution into small sections and validate each part before moving on.
  • Use Case: You want to add a new feature to an app but only have a rough concept; this Skill helps turn that concept into a validated plan.

Quick Start

Use the brainstorming skill to help me clarify and design a new feature for my project.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn rough feature ideas into clear design specifications?▼

To turn rough feature ideas into clear design specifications, this process uses structured questioning to clarify goals, constraints, and success criteria before implementation begins.

What is the best way to scope architecture for incomplete product requirements?▼

Scoping architecture for incomplete product requirements involves comparing 2-3 alternative approaches with trade-offs and providing a recommendation to validate the evolving design.

How do I validate architecture and data flow during feature planning?▼

You validate architecture and data flow by breaking the solution into small sections and incrementally reviewing components, testing, and error handling before moving on.

Can I use this to clarify goals when requirements are evolving?▼

Yes, you can clarify goals for evolving requirements through structured questioning designed for product discovery and feature planning when constraints are incomplete.

When should I avoid using an incremental design review process?▼

You should avoid an incremental design review process if your feature concept is already fully validated and lacks ambiguous requirements needing structured clarification or option comparison.

Related Skills

Explore More Software Engineering Skills→
AzrinPutraAzrinPutra

intent-capture

Guide exploratory conversations to elicit project requirements and generate an intent brief.

Community
Intermediate
UniquecreteUniquecrete

brainstorming

Convert ambiguous product ideas into validated design specifications with guided questioning.

Community
Intermediate
PedroGiudicePedroGiudice
5

architecture-diagram-creator

Generate HTML architecture diagrams with data flows and deployment layers.

Community
Advanced
hoanghd218hoanghd218

brainstorming

Compare software architecture options with trade-offs and acceptance criteria.

Community
Advanced