Solution Options and Tradeoff Review
Get distinct solution options, explicit tradeoffs, and a recommended approach with a test before implementation.
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
“We keep jumping to the first idea” and “these options all sound the same” are decision problems, not shortages of ideas. This skill develops genuinely different approaches, tests them against your constraints, and recommends a direction with a clear reason to change course.
What it does
- Separates the outcome you need from the solution already embedded in your request.
- Generates three to five approaches that differ in mechanism, ownership, or scope.
- Screens hard constraints before comparing speed, cost, risk, and reversibility.
- Identifies options that are actually components of one solution rather than alternatives.
- Removes dominated options without treating unknowns as evidence of failure.
- Turns the most consequential uncertainty into a bounded pilot with a decision threshold.
What you get
A decision-sized shortlist with explicit tradeoffs, a recommended approach, and the conditions that would favor its runner-up. Missing information is labeled, and quick questions receive a compact answer instead of a full workshop.
Best for
Builders, product teams, and operations leads choosing an approach before committing implementation time, introducing a tool, or changing a workflow.
SKILL.md preview
---
name: solution-options-and-tradeoff-review
description: Compare distinct approaches before implementation by separating outcomes from proposed solutions, screening constraints, and evaluating tradeoffs and reversibility. Recommend a direction and a bounded test of its weakest assumption. Use when the user says "brainstorm approaches", "what are our options?", "help me choose a direction", "before we build this", "these ideas all sound the same", "we keep picking the first solution", or "is there a simpler way?".
---
# Solution Options and Tradeoff Review
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Startup Idea Validation Plan
Test an idea before you build: grade evidence (said, did, paid), find the riskiest assumption, run the cheapest test with kill criteria.
Market-First Venture and PMF Verdict
Get a blunt build, narrow, test, or stop verdict based on buyer demand, retention, distribution, and explicit confidence.
Micro-SaaS Go/No-Go Validation
A build, test, reframe, or kill verdict on a micro-SaaS idea, with revenue math, fatal-flaw gates, and a test you can run this week.
Business Decisions From Live Notion Data
Turn Notion pipeline, revenue, and client records into evidence-backed business decisions and a focused action plan.