brainstorming

Guides collaborative design dialogue to turn ideas into approved specs before implementation.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/SleyiW/iWana-neXt --skill brainstorming-sleyiw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/SleyiW/iWana-neXt/tree/main/.agents/skills/brainstorming
Command: npx skills add https://github.com/SleyiW/iWana-neXt --skill brainstorming-sleyiw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Jumping straight into code without a validated design leads to wasted work, unexamined assumptions, and misaligned implementations. This Skill enforces a structured discovery process that explores user intent, requirements, and design trade-offs before any code is written. ## Core Features & Use Cases - Structured Design Dialogue: Explores project context, asks clarifying questions one at a time, proposes 2-3 approaches with trade-offs, and presents designs in sections for incremental approval. - Spec Authoring and Review: Writes validated designs to dated spec documents, runs a self-review for placeholders and contradictions, and gates implementation behind explicit user approval. - Visual Companion Server: Includes a browser-based companion (Node.js server with WebSocket events) for presenting mockups, wireframes, and layout comparisons when questions are visual rather than textual. - Use Case: Before building a new feature, use this Skill to interview yourself about requirements, compare architectural approaches, produce a committed design doc, and only then hand off to implementation planning. ## Quick Start Ask the agent to brainstorm the design for your next feature before writing any code, and answer its clarifying questions one at a time.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I brainstorm a software design before writing code?

Start by exploring the current project context, then answer clarifying questions one at a time about purpose, constraints, and success criteria. The process proposes 2-3 approaches with trade-offs, presents the design in sections for approval, and writes a spec document before any implementation begins.

How do I show UI mockups during a design discussion with an AI agent?

Use the visual companion: run scripts/start-server.sh with your project directory, open the printed localhost URL, and the agent pushes HTML mockups to your browser. Your clicks are recorded as JSON events that the agent reads on its next turn.

Does the brainstorming visual companion work on Windows or in Codex?

Yes. The start script auto-detects Windows (Git Bash/MSYS) and Codex environments and switches to foreground mode, since those platforms reap detached background processes. On Windows, launch it with a background shell call so it survives across turns.

When should I skip the design phase for a simple change?

Never. The process explicitly requires a design for every project, including single-function utilities and config changes, because simple projects are where unexamined assumptions cause the most wasted work. The design can be just a few sentences, but it must be presented and approved.

Why did the brainstorm server stop responding?

The server auto-exits after 30 minutes of inactivity or when its owner process dies. Check for a server-stopped file in the session state directory, then restart it with start-server.sh before pushing new screens.