workflow-brainstorm
Use when you need to turn a vague idea into a confirmed design spec before implementation (new feature/component/behavior change). First check project context, then ask one question at a time, provide 2-3 options with trade-offs, finally output design in segments (~200-300 words each) with confirmation after each. Triggers: brainstorm, clarify idea, design spec, refine concept, requirement clarification.
Best use case
workflow-brainstorm is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when you need to turn a vague idea into a confirmed design spec before implementation (new feature/component/behavior change). First check project context, then ask one question at a time, provide 2-3 options with trade-offs, finally output design in segments (~200-300 words each) with confirmation after each. Triggers: brainstorm, clarify idea, design spec, refine concept, requirement clarification.
Teams using workflow-brainstorm should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/workflow-brainstorm/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How workflow-brainstorm Compares
| Feature / Agent | workflow-brainstorm | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when you need to turn a vague idea into a confirmed design spec before implementation (new feature/component/behavior change). First check project context, then ask one question at a time, provide 2-3 options with trade-offs, finally output design in segments (~200-300 words each) with confirmation after each. Triggers: brainstorm, clarify idea, design spec, refine concept, requirement clarification.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Brainstorming Ideas Into Designs ## Goal Transform "vague ideas/requirements" into **actionable designs and specifications**, producing reusable file artifacts (rather than just staying in chat). > Key requirement: **Ask only one question at a time**. If a topic is complex, break it into multiple rounds of Q&A—don't throw out a checklist all at once. ## Core Process (Must Follow) ### 0) Check Project Context First (Required When Repo Exists) Before asking questions, quickly check: - Key documentation: `README.md`, `docs/`, `design-system.md` (if exists) - Tech stack and constraints: `package.json` / `Cargo.toml` / `pyproject.toml` etc. - Structure overview: top-level directories, main modules - Recent changes: `git log -n 10 --oneline` (if it's a git repo) Output a **very brief** context summary: what you observed + possible constraint points (don't start designing yet). ### 1) Understand the Idea (One Question at a Time) Goal is to gather the minimum information set (purpose / constraints / success criteria). Rules: - Each message asks **1 question** only - Prefer multiple choice (reduce user's cognitive load), use open questions only when necessary - Ask direction-determining questions first (goals/success criteria/non-goals), then details ### 2) Explore Solutions (2-3 Options + Trade-offs) After you understand the requirements: - Provide 2-3 options (A/B/C) - Explain trade-offs for each (complexity/risk/iteration speed/long-term cost) - **Give your recommended option first**, then explain why ### 3) Output Design (200-300 Word Segments + Confirm Each) When you're confident you understand what needs to be done, start outputting the design spec. Requirements: - Output in segments (~200-300 words each) - Ask for confirmation at the end of each segment: e.g., "Does this look good?" - Design should at least cover: - Architecture and module boundaries - Core data flow (input → processing → output) - Error handling and edge cases - Testing and validation strategy (minimum viable set) If user disagrees with a segment: go back to questioning/option phase to clarify—don't push forward. ## Artifacts and Persistence (Strongly Recommended) ### Write Design Document Prefer writing to run directory (artifact-first): - `run_dir/evidence/YYYY-MM-DD-<topic>-design.md` If there's no `run_dir` but there is a `repo_root`: - Create `runs/brainstorm/active/<run_id>/`, and write design to `evidence/` > Note: Writing files is a write operation; if this is the user's project repo, confirm "should I persist to the project?" before writing. ### Enter Implementation (Optional) After design is confirmed, ask one question to let user choose next step: 1. Enter implementation directly (recommend `workflow-ship-faster` or `workflow-feature-shipper`) 2. Write implementation plan first (persist as checklist items in `run_dir/tasks.md`, then wait for confirmation) 3. Need research/code reading first (split to `run_dir/evidence/parallel/<task-name>/` and do in parallel) ## Key Principles - **One question at a time**: Never ask 5 questions in one message - **Multiple choice preferred**: Help user respond faster and more effectively - **YAGNI**: Actively remove "not needed yet" features from the design - **Incremental validation**: Output design in segments, confirm each one
Related Skills
workflow-ship-faster
Ship Faster end-to-end workflow for small web apps (default: Next.js 16.1.1): idea/prototype → foundation gate → design-system.md → lightweight guardrails + docs → feature iteration → optional Supabase + Stripe → optional GitHub + Vercel deploy → optional AI-era SEO (sitemap/robots/llms.txt). Resumable, artifact-first under runs/ship-faster/ (or OpenSpec changes/). Trigger: ship/launch/deploy/production-ready MVP.
workflow-project-intake
Use when you need to clarify requirements and route to the right workflow (idea → executable input). Project intake + routing: help the user brainstorm and clarify intent, persist goal/context artifacts, then dispatch to the right workflow or step skill. Default route is workflow-ship-faster (Next.js 16.1.1) for idea/prototype→launch. Triggers: project kickoff, requirements clarification, brainstorm, ideas, discovery, intake.
workflow-feature-shipper
Use when you need to ship a single PR-sized feature end-to-end (plan -> implement -> verify) with artifacts. Ship core product features quickly in a Next.js codebase: turn a feature idea into an executable plan, implement in PR-sized slices, and keep artifacts under runs/ (or OpenSpec changes/ when available). Supports plan-only mode for early scoping. For prototype UI work, include a demo-ready wow moment (animation/micro-interaction) by default unless user opts out.
workflow-creator
Create workflow-* skills by composing existing skills into end-to-end chains. Turns a user idea into a workflow_spec.md SSOT (via workflow-brainstorm), discovers available skills locally + from skills.sh, and generates a new workflow-<slug>/ skill package. Use when you want to design a new workflow, chain multiple skills into a flow, or turn scattered atomic skills into a resumable plan-then-confirm workflow.
workflow-template-seeder
Seed a new runnable template under templates/NNN-slug/ from a short spec by chaining existing skills (intake → ship-faster stages) while keeping it clean and shareable (no secrets, minimal scope). Use when creating a new template quickly.
workflow-template-extractor
Extract a shareable runnable template under templates/NNN-slug/ from a real project: copy + de-brand + remove secrets + add env examples + docs, with minimal refactors. Use when you have a working project and want to turn it into a template.
workflow-execute-plans
Execute written implementation plans: first read and critically review the plan, then implement in small batches (default 3 tasks), produce verification evidence per batch and pause for feedback; must stop immediately and ask for help when blocked/tests fail/plan unclear. Trigger words: execute plan, implement plan, batch execution, follow the plan.
domain-name-brainstormer
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
ui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
turbo-sdk
Complete Arweave Turbo ecosystem including client SDKs, core upload infrastructure, payment service backend, and CLI tools for permanent decentralized storage
terraform-best-practices
Comprehensive best practices for Terraform infrastructure as code from Anton Babenko's community guide