brainstorming

Guide structured design specification creation with beads-tracked epics.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/getspur/spur --skill brainstorming-getspur
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/getspur/spur/tree/main/.spur/skills/brainstorming
Command: npx skills add https://github.com/getspur/spur --skill brainstorming-getspur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of ephemeral, unorganized brainstorming by enforcing a structured, beads-tracked design process that ensures every feature is documented, approved, and ready for implementation.

Core Features & Use Cases

  • Structured Design Workflow: Guides the user through context exploration, approach selection, and spec creation.
  • Beads Integration: Automatically tracks design decisions, rationale, and approval states as beads issues.
  • Use Case: When starting a new feature, use this skill to decompose the requirements, evaluate multiple technical approaches, and generate a formal design document that serves as the source of truth for the development team.

Quick Start

Use the brainstorming skill to design a new authentication module for the current project.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn software feature ideas into formal design specifications?

To turn software feature ideas into formal design specifications, you need a structured workflow that guides context analysis, evaluates technical trade-offs, and documents the approved approach before implementation begins.

What is the best way to track design decisions and rationale for new architecture?

Tracking design decisions and rationale for new architecture requires recording context, evaluated trade-offs, and approval states as structured issues, ensuring all technical choices are validated and serve as the source of truth.

How do I create a structured design workflow for a new software feature?

Creating a structured design workflow involves guiding the team through context exploration, approach selection, and formal spec creation, ensuring every technical decision is recorded and approved before development tasks start.

Can I evaluate multiple technical approaches before starting software implementation?

Yes, you can evaluate multiple technical approaches before implementation by decomposing requirements, analyzing context, and documenting the trade-offs of each potential architecture within a formal design specification.

When do I need a formal specification document for software planning?

You need a formal specification document for software planning when starting a new feature, to prevent ephemeral brainstorming and ensure the development team has an approved, tracked source of truth before coding begins.