brainstorm

Turn ideas into reviewed design specifications before implementation.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/yearofthedan/weaver --skill brainstorm-yearofthedan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/yearofthedan/weaver/tree/main/.claude/skills/brainstorm
Command: npx skills add https://github.com/yearofthedan/weaver --skill brainstorm-yearofthedan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents premature implementation by turning vague ideas into clear, approved designs and specs so developers avoid wasted work, missed assumptions, and risky cross-file changes.

Core Features & Use Cases

  • Context exploration: Instructs the agent to inspect project files, docs, and recent commits before proposing changes.
  • Clarifying questions: Requires one question at a time to refine purpose, constraints, and success criteria.
  • Approach comparison and recommendation: Presents 2–3 alternative approaches with trade-offs and a recommended path.
  • Design, spec, and gatekeeping: Produces a design, writes a spec via /spec, asks for user review, and only transitions to implementation with explicit approval via /slice.
  • Use Case: Ideal for feature additions, component builds, configuration changes, small utilities, and any task where architectural or cross-file effects matter.

Quick Start

Ask the assistant to run the brainstorm workflow for your idea, providing current project context, constraints, and success criteria.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I turn feature requests into design specifications before implementation?

Turning feature requests into design specifications requires exploring project context and clarifying constraints, then comparing multiple approaches with trade-offs to produce a committed spec via /spec before transitioning to implementation.

What is the best way to prevent premature implementation of vague feature ideas?

The best way to prevent premature implementation is using a brainstorm workflow that inspects project context, clarifies constraints one question at a time, and requires explicit user approval before transitioning to /slice.

How do I write a design spec for component builds with cross-file implications?

Writing a design spec for component builds involves inspecting project files and docs, clarifying success criteria, comparing 2-3 alternative approaches with trade-offs, and outputting a committed spec via /spec for user review.

Does this design workflow work for configuration changes and small utilities?

Yes, this design workflow works for configuration changes and small utilities, applying context exploration, clarifying questions, approach comparison, and approval gates to any task where architectural or cross-file effects matter.

When should I not use a brainstorm workflow for feature design?

You should not use a brainstorm workflow for feature design when a task has no architectural or cross-file implications, as the overhead of context exploration, approach comparison, and spec gatekeeping is designed for complex changes.