solution-exploration

Explores the problem and the range of possible approaches before any code is written — clarifying what is actually being asked, surfacing options with their tradeoffs, and converging on one. Use this at the start of any feature, component, or behavior change, when a request is ambiguous, when the first idea is the only idea on the table, or when a design decision needs pressure-testing before commitment.

Try your first task

Explore approaches for a small feature

Start a fresh conversation.

Use the solution-exploration skill to examine this proposed feature before any code is written. Clarify the desired outcome, current problem, affected users, explicit exclusions, and observable success condition. Then present three genuinely different approaches—including the smallest workable approach and one requiring no new moving parts—with costs, tradeoffs, and necessary assumptions. Recommend one approach, explain why the others lost, and identify the assumption on which the recommendation depends most heavily.

Required inputs

Proposed feature or behavior change
Desired outcome and current problem
Affected users or systems
Known constraints and explicit exclusions

Suggested template by Skill Leaderboard, grounded in the linked source. Task evidence ↗

Inside SKILL.md

46 lines

Section content has not been verified for this skill yet.

Full source remains withheld under the current source-display policy. Read the author’s source ↗