brainstorming

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

1|Updated Sep 13, 2026
One-click install
npx skills add https://github.com/silentFellow/public-dotfiles --skill brainstorming-silentfellow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/silentFellow/public-dotfiles/tree/main/agents/skills/brainstorming
Command: npx skills add https://github.com/silentFellow/public-dotfiles --skill brainstorming-silentfellow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? It prevents wasted implementation effort by forcing intent exploration, requirement clarification, and explicit human approval before any code is written for creative or architectural work. ## Core Features & Use Cases - Three-Path Classification: Routes every request into spike, bounded, or architectural tracks with appropriately scaled process and a hard approval gate. - Structured Design Dialogue: Asks clarifying questions one at a time, proposes 2-3 approaches with trade-offs, and presents sectioned designs for incremental approval. - Spec Authoring and Review: Writes validated design documents 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, diagrams, and clickable option screens via a local WebSocket server for questions better shown than described. - Use Case: When asked to add a new subsystem, classify the request as architectural, interview the stakeholder about purpose and constraints, present design sections for approval, then commit a spec before planning implementation. ## Quick Start Ask the agent to brainstorm and design the new feature with you before writing any code.

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 with an AI before coding?▼

Invoke the brainstorming flow before any implementation request. It classifies your task as spike, bounded, or architectural, asks clarifying questions one at a time, proposes approaches with trade-offs, and requires your explicit approval before any code is written.

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 existing code flows with a short in-chat design. Architectural covers new projects or subsystem restructuring and requires a full written spec and review.

How does the visual companion browser mockup server work?▼

A local Node.js server watches a content directory for HTML files and serves the newest one to your browser over a key-authenticated WebSocket connection. You click options in the browser, and selections are recorded as JSON events the agent reads on its next turn.

Can I skip the design approval step for simple changes?▼

No. Every path ends with explicit human approval before implementation, regardless of simplicity. What scales with task size is the design artifact length, not the approval gate, since simple tasks are where unexamined assumptions cause the most wasted work.

Where are brainstorming design specs saved?▼

Validated design documents are written to docs/superpowers/specs/ with a dated filename pattern like YYYY-MM-DD-topic-design.md and committed to git, unless your user preferences override the default location.