brainstorming

Guides collaborative design exploration through classified spike, bounded, and architectural workflows.

Updated Aug 12, 2026
One-click install
npx skills add https://github.com/Barbaros911/As-mine --skill brainstorming-barbaros911
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/Barbaros911/As-mine/tree/main/.claude/skills/brainstorming
Command: npx skills add https://github.com/Barbaros911/As-mine --skill brainstorming-barbaros911

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Jumping straight into code on a new feature or change often produces wasted work from unexamined assumptions. This Skill enforces a structured dialogue that explores user intent, requirements, and design before any implementation begins, with a mandatory human approval gate. ## Core Features & Use Cases - Three-Path Classification: Routes every request into spike (feasibility probe), bounded (scoped change to existing code), or architectural (new subsystem) workflows, each with its own checklist and approval gate. - Spec Authoring and Review: Writes validated designs to dated spec documents, runs a self-review for placeholders and contradictions, and hands off to an implementation-planning skill. - Visual Companion Server: Ships a Node.js WebSocket server that serves live HTML mockups, diagrams, and A/B layout options to a browser so visual questions can be answered by seeing rather than reading. - Use Case: Before adding a new booking flow to an existing app, classify the request as bounded, ask clarifying questions one at a time, present a short in-chat design, and only implement after explicit approval. ## Quick Start Ask the assistant to brainstorm the design for your next feature before writing any code, and answer its clarifying questions until it presents a design for your approval.

Frequently Asked Questions about brainstorming

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

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

Classify the request as spike, bounded, or architectural, then explore project context and ask clarifying questions one at a time. Present a design scaled to the task and wait for explicit human approval before any implementation begins.

What is the difference between spike, bounded, and architectural tasks?▼

A spike answers a feasibility question with throwaway work. Bounded covers well-scoped changes to flows already in the repo. Architectural covers new projects or subsystems and requires a written spec plus an implementation plan.

How do I show UI mockups in a browser during brainstorming?▼

Run scripts/start-server.sh with --project-dir and --open after the user approves the visual companion. Write HTML fragments to the returned screen_dir; the Node.js server serves the newest file and records clicks to state_dir/events.

Does the brainstorming server work in remote or containerized environments?▼

Yes, bind a non-loopback host with --host 0.0.0.0 and set --url-host for the printed URL. Access is gated by a session key in the URL, and auto-open is skipped on remote binds so you share the URL manually.

Why does the brainstorm companion show a paused overlay?▼

The overlay appears after the WebSocket has been disconnected for about 15 seconds, usually because the server stopped or hit its idle timeout. Restart with the same --project-dir and the open tab reconnects automatically on the same port.

When should I skip writing a design spec document?▼

Skip the spec file for spikes and bounded tasks, where a short in-chat design plus approval is sufficient. Only the architectural path writes a dated design document to the specs directory and requires user review of the written spec.