brainstorming

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

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/danieliudi/trackforge-os --skill brainstorming-danieliudi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/danieliudi/trackforge-os/tree/main/.cursor/skills/brainstorming
Command: npx skills add https://github.com/danieliudi/trackforge-os --skill brainstorming-danieliudi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? It prevents wasted implementation work by forcing intent exploration, requirement clarification, 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 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 when questions are better 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 — or for larger work, produce a committed spec before planning. ## Quick Start Ask the agent to brainstorm and design the feature you have in mind before writing any code, and approve the presented design before implementation starts.

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

How do I show UI mockups during a brainstorming session?

Start the visual companion with scripts/start-server.sh using --project-dir and --open after the user approves it. Write HTML fragments to the screen directory and the server pushes them to the user's browser over WebSocket.

Does the brainstorming skill allow skipping the approval step for simple tasks?

No. Every path ends with explicit human approval before implementation, regardless of task size. Simple tasks only scale down the design artifact to a few sentences in chat, never the approval gate.

Why does the visual companion URL require a session key?

The server generates a per-session token embedded as ?key= in the URL to authenticate HTTP and WebSocket requests. This blocks stray browser tabs, other machines on the network, and DNS rebinding attacks from reading screens or injecting events.