brainstorm-protocol

To turn vague ideas into a concrete design brief, you need a structured brainstorming process that maps the problem space before exploring solutions. This Skill enforces a nine-step dialogue that surfaces constraints and risks, yielding a formal brief.

Problem-space exploration for early-stage brainstorming identifies constraints, unknowns, and core objectives before solution generation. It maps the ambiguous request landscape to ensure the resulting design brief targets actual user needs and manages project risks.

Structure a brainstorming session for greenfield platform requests by following a guided nine-step protocol. This process enforces problem-first thinking, covering constraint identification, divergent thinking, convergence, and risk tracking to produce a formal design brief.

Yes, you can use this structured brainstorming process for internal tooling initiatives. The protocol supports product, platform, and internal tooling contexts to accelerate outcome-focused design by formalizing vague requests into actionable briefs.

You need a formal design brief when facing ambiguous or greenfield requests where solution requirements are unclear. Generating a brief first enforces problem-space mapping and risk management, preventing premature solution development and misaligned outcomes.

The best way to track risks and unknowns during early design exploration is through a structured convergence process. This protocol systematically identifies and documents risks alongside constraints, ensuring the final design brief captures all critical project variables.