Workflows Brainstorm
Explore requirements and approaches through collaborative dialogue before planning implementation
Install
npx skills add ratacat/claude-skills --skill workflows-brainstormgit clone --depth 1 https://github.com/ratacat/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/workflows-brainstorm ~/.claude/skills/workflows-brainstormPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
## Arguments [feature idea or problem to explore] # Brainstorm a Feature or Improvement **Note: The current year is 2026.** Use this when dating brainstorm documents. Brainstorming helps answer **WHAT** to build through collaborative dialogue. It precedes `/workflows:plan`, which answers **HOW** to build it. **Process knowledge:** Load the `brainstorming` skill for detailed question techniques, approach exploration patterns, and YAGNI principles. ## Feature Description <feature_description> #$ARGUMENTS </feature_description> **If the feature description above is empty, ask the user:** "What would you like to explore? Please describe the feature, problem, or improvement you're thinking about." Do not proceed until you have a feature description from the user. ## Execution Flow ### Phase 0: Assess Requirements Clarity Evaluate whether brainstorming is needed based on the feature description. **Clear requirements indicators:** - Specific acceptance criteria provided - Referenced existing patterns to follow - Described exact expected behavior - Constrained, well-defined scope **If requirements are already clear:** Use **AskUserQuestion tool** to suggest: "Your requirements seem detailed enough to proceed directly to planning. Should I run `/workflows:plan` instead, or would you like to explore the idea further?" ### Phase 1: Understand the Idea #### 1.1 Repository Research (Lightweight) Run a quick repo scan to understand existing patterns:
Details
- Skill name
workflows-brainstorm- Repository
- ratacat/claude-skills
- Path
skills/workflows-brainstorm/SKILL.md- Repo updated
- 11 February 2026
FAQ
What does the Workflows Brainstorm skill do?
Explore requirements and approaches through collaborative dialogue before planning implementation
How do I install the Workflows Brainstorm skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add ratacat/claude-skills --skill workflows-brainstorm. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Workflows Brainstorm popular?
It lives in ratacat/claude-skills, which has 59 GitHub stars and 10 forks.
Related skills
Skill Creator
59ratacat/claude-skills
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
Skill Installer
59ratacat/claude-skills
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
Agent Browser
59ratacat/claude-skills
Browser automation using Vercel's agent-browser CLI. Use when you need to interact with web pages, fill forms, take screenshots, or scrape data. Alternative to Playwright MCP - uses Bash commands with ref-based element selection. Triggers on "browse website", "fill form", "click button", "take screenshot", "scrape page", "web automation".
Workflows Compound
59ratacat/claude-skills
Document a recently solved problem to compound your team's knowledge
Triage
59ratacat/claude-skills
Triage and categorize findings for the CLI todo system
Workflows Plan
59ratacat/claude-skills
Transform feature descriptions into well-structured project plans following conventions
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.