brainstorm

Guide structured brainstorming and design-gate approval before coding begins.

4|Updated Jan 1, 2026
One-click install
npx skills add https://github.com/vertexcover-io/tarash --skill brainstorm-vertexcover-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/vertexcover-io/tarash/tree/main/.claude/skills/brainstorm
Command: npx skills add https://github.com/vertexcover-io/tarash --skill brainstorm-vertexcover-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming and a formal design gate help teams understand complex problems deeply and ensure a validated architecture before implementation, reducing rework and misaligned scope.

Core Features & Use Cases

  • Deep problem understanding: surface hidden assumptions, constraints, and edge cases.
  • Design gate: produce an approved architectural design before any coding begins.
  • Use Case: when starting a complex feature request, run a structured brainstorm to surface questions and define a high-level design plan.

Quick Start

Initiate a guided brainstorm and design gate for the requested problem and require explicit user approval before any implementation begins.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I enforce an architectural design gate before coding begins?

To enforce an architectural design gate, you need a structured workflow that surfaces assumptions and requires explicit approval of functional and non-functional considerations before implementation. This prevents misaligned scope and rework.

What is the best way to brainstorm requirements for a complex system redesign?

The best way to brainstorm requirements for a system redesign is to use a structured process that defines edge cases and high-level design outlines, ensuring teams align on architectural decisions before any code is written.

How do I surface hidden assumptions and constraints during feature planning?

To surface hidden assumptions during feature planning, apply a structured brainstorming workflow that identifies functional and non-functional constraints, forcing teams to resolve questions before implementation starts.

Can I use a design gate workflow for both product management and software engineering tasks?

Yes, you can use a design gate workflow for both product management and software engineering tasks. It applies to complex feature requests and architectural decisions across both domains to align teams before implementation.

When should I require explicit approval before allowing code-level work to begin?

You should require explicit approval before code-level work begins when starting complex feature requests or system redesigns, ensuring a validated architectural plan is in place to prevent scope misalignment and rework.