brainstorming

Guides collaborative design exploration and spec writing before any implementation work begins.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/assafmanor/waypoint --skill brainstorming-assafmanor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/assafmanor/waypoint/tree/main/.claude/skills/brainstorming
Command: npx skills add https://github.com/assafmanor/waypoint --skill brainstorming-assafmanor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? It prevents wasted implementation effort by forcing intent clarification, design review, and explicit human approval before any code is written, catching unexamined assumptions early. ## Core Features & Use Cases - Three-Path Classification: Routes every request into spike, bounded, or architectural tracks with appropriately scaled process and approval gates. - Structured Design Dialogue: Asks clarifying questions one at a time, proposes 2-3 approaches with trade-offs, and presents sectioned designs for approval. - Spec Writing and Review: Writes validated designs to dated spec files, runs a self-review for placeholders and contradictions, and hands off to implementation planning. - Visual Companion Server: Serves browser-based mockups and diagrams via a local WebSocket server when questions are clearer shown than described. - Use Case: When asked to add a new feature, classify the request, present a short design in chat, wait for explicit approval, then implement — instead of jumping straight to code. ## Quick Start Ask the assistant to brainstorm and design a new feature with you before writing any code, starting by classifying the request as a spike, bounded change, or architectural project.

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 approval before implementing anything.

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

A spike answers a feasibility question with throwaway work. Bounded means a well-scoped change to an existing flow in the repo. Architectural covers new projects or subsystems and requires a full written spec and review.

When should I use the visual companion browser mockups?▼

Use the browser companion only when a question is genuinely visual, such as layout comparisons, wireframes, or architecture diagrams. Conceptual questions, tradeoff lists, and requirements discussions stay in the terminal.

Can I skip the design step for a simple one-line change?▼

No. Every path ends with human approval before implementation, though the design artifact scales down to two sentences in chat for simple tasks. The approval gate never scales away.

How do I start the brainstorming visual companion server?▼

Run scripts/start-server.sh with --project-dir pointing at your project root and --open after the user approves the companion. It returns a JSON object with the keyed URL, screen directory, and state directory.