brainstorming

Facilitate structured design exploration and produce validated design specifications.

3|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/sthiermann/stn-skills --skill brainstorming-sthiermann
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/sthiermann/stn-skills/tree/main/skills/brainstorming
Command: npx skills add https://github.com/sthiermann/stn-skills --skill brainstorming-sthiermann

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps teams convert vague or ambiguous requirements into validated and well-understood design specifications, reducing the risk of overlooked assumptions and design flaws.

Core Features & Use Cases

  • Structured problem analysis: Guides users through in-depth understanding and scope clarification.
  • Multi-lens exploration: Applies multiple cognitive frameworks to identify risks and opportunities.
  • Approach evaluation: Uses weighted decision matrices and adversarial review to select the best solution.
  • Use case: Before implementing a new feature, teams run this Skill to explore alternative architectures, surface hidden risks, and produce a comprehensive, validated design document.

Quick Start

Use the brainstorming skill with a problem description to generate and evaluate multiple approaches efficiently.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I convert ambiguous software requirements into validated design specifications?

To convert ambiguous requirements into validated design specifications, use structured problem analysis to clarify scope, apply multi-lens exploration for risks, and use weighted decision matrices to select the best architecture.

What is the best way to evaluate alternative software architectures before implementation?

Evaluating alternative architectures is best done using a weighted decision matrix to score approaches and conducting an adversarial review to surface hidden risks, ensuring thorough evaluation before implementation begins.

When do I need to use a multi-lens analysis for product development?

You need multi-lens analysis for product development when facing vague problem statements, as applying multiple cognitive frameworks helps identify risks and opportunities that single-perspective evaluations often miss.

How does adversarial review help reduce scope creep in software engineering?

Adversarial review reduces scope creep by systematically challenging proposed design specifications, exposing overlooked assumptions and design flaws early, which prevents costly architectural changes during implementation.

Can I use approach scoring for complex software architecture decisions?

Yes, you can use approach scoring for complex software architecture decisions by applying weighted decision matrices to quantify trade-offs across multiple criteria, yielding a validated and objective design selection.

Why does structured design exploration prevent design flaws in new features?

Structured design exploration prevents design flaws by enforcing systematic problem understanding and adversarial review before coding, ensuring all architectural assumptions are validated and documented in a comprehensive specification.