Brainstorming
Runs Claude through a structured ideation pass before committing to an approach.
Before & after
Same prompt, same agent — the only difference is the skill.
I can help you think through this decision! There are definitely pros and cons to both approaches, and it really depends on several factors specific to your situation. The rewrite approach might be cleaner in some ways, but the refactor could be less disruptive. I'd recommend considering your team size, timeline, and how mission-critical the API is. You might also want to think about technical debt, performance impacts, and maintenance overhead. There are other options too—you could do a hybrid approach. Would you like me to explore any particular angle more deeply? I'm happy to discuss whatever feels most relevant to your context.
OPTION 1: Full rewrite (3-4 months) PROS • fresh architecture with modern patterns • clean codebase easier to maintain • chance to drop legacy baggage CONS • complete service downtime during migration • team unproductive during learning curve • high risk if timeline slips CHALLENGES • new bugs will emerge in production OPTION 2: Strangler fig (incremental) PROS • zero downtime, routes requests to old/new as ready • team ships value weekly • easy rollback per endpoint CONS • temporarily doubles complexity (dual codebases) • slower time to full completion (6-8 months) CHALLENGES • coordination overhead managing two systems in parallel OPTION 3: Branch-by-abstraction PROS • single codebase, no dual-system overhead • endpoints ship independently • low deployment risk CONS • requires careful feature flag architecture upfront • testing complexity high (both paths) CHALLENGES • slow if team doesn't nail abstraction design first RECOMMENDATION: Strangler fig. Rewrite kills momentum; abstraction requires expertise you may not have. Strangler lets you ship incrementally and bail if roadblocks emerge.
About this skill
name: brainstorming description: Use when Runs Claude through a structured ideation pass before committing to an approach.
Brainstorming
Brainstorming is one of the widely used skills in the collection, giving Claude a structured process for generating and evaluating multiple approaches to a problem before implementation starts, instead of jumping straight to the first idea.
What you get
- A structured multi-option ideation pass with tradeoffs spelled out.
Customize your output
- Adjust the number of options generated or the evaluation criteria.
Example output
A short list of considered approaches with pros, cons, and a recommendation.
Best for
Builders who want Claude to consider alternatives before committing to a plan.
SKILL.md preview
---
name: brainstorming
description: Use this skill when multiple approaches to a problem need structured ideation and evaluation before implementation starts.
version: 1.0.0
category: Productivity
author: AgentVolt
license: proprietary
tags:
- productivity
- standard
---
# Brainstorming
Runs a structured ideation pass across multiple candidate approaches before any implementation work begins.
## When to use
… (sign up to view the full skill)More productivity skills
View all Productivity skills →AI Productivity System
A complete AI-driven system for planning your day, triaging tasks, and shipping more without burning out.
Inbox Zero Workflow
An opinionated triage loop that gets a buried inbox to zero in about twenty minutes.
Calendar Triage
Reviews the week ahead, flags where you are overcommitted, and suggests what to cut or move.
Slack Catch-Up Agent
Summarizes what you missed across your Slack channels overnight, ranked by what needs a reply.