brainstorming

Name: brainstorming
Availability: InStock
Author: yanochka11

Transform unclear software requirements into structured design specifications.

Updated May 5, 2026

Search Tags:#brainstorming #feature development #specification #software architecture #requirements analysis #design planning

Ready to run

npx skills add https://github.com/yanochka11/harness_bro --skill brainstorming-yanochka11

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents premature implementation by helping teams clarify goals, requirements, constraints, and design decisions before writing code or changing systems.

Core Features & Use Cases

Context Exploration: Guides analysis of existing project state, documentation, and constraints before proposing solutions.
Design Collaboration: Structures one-question-at-a-time discovery, approach comparisons, and iterative design approval.
Use Case: When planning a new feature or modifying an existing application, use this Skill to create a validated design specification before moving into implementation planning.

Quick Start

Use the brainstorming skill to help me design a new feature by exploring requirements, proposing approaches, and creating an approved plan.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I turn feature ideas into structured software architecture specifications?▼

Feature idea specification is achieved by analyzing project context, conducting one-question-at-a-time requirement discovery, and securing staged design approval before writing code. This process prevents premature implementation by validating goals and constraints collaboratively.

What is the best way to plan requirements analysis for new software components?▼

Requirements analysis for new software components is best planned by exploring existing documentation, comparing design approaches, and writing structured specifications. This ensures all project constraints and behavior changes are validated before development begins.

Can I use this for modifying existing application behavior and project architecture discussions?▼

Yes, modifying existing application behavior and discussing project architecture are supported through collaborative discovery and context exploration. The process validates constraints and proposes structured design changes before any implementation workflow begins.

How do I create an approved design plan before moving into implementation planning?▼

An approved design plan is created by guiding teams through iterative approach comparisons and staged design approval. Once requirements are clarified and constraints analyzed, the workflow transitions directly into implementation planning.

Does this approach prevent premature implementation when developing new features?▼

Yes, preventing premature implementation is the core objective when developing new features. By structuring goal clarification, requirements analysis, and design approval beforehand, teams avoid writing code before system changes are fully validated.