feasibility-analysis

name	feasibility-analysis
description	Use when unfamiliar technology or constraints require sourced options and feasibility evidence before choosing an approach.
targets	["*"]
claudecode	{"context":"fork","agent":"researcher"}

This skill defines the feasibility phase. Use the `researcher` agent when a bounded investigation can proceed independently; otherwise work locally. Produce sourced options, constraints, and unresolved unknowns.

Use lifecycle-documentation only when the result needs a durable artifact or handoff.

Scout the problem space and map the landscape. Find what already exists, how others solve this, and what could make it hard or impossible. Explore wide before going deep — survey many options, don't tunnel on the first.

Use the codebase, Context7, and web search together. Every claim you make must trace to a source.

When rules, exceptions, adapters, or compensating processes appear to protect a questionable model, run find-simplifying-insight. Keep the current model as the null hypothesis and require a falsifiable prediction before recommending a paradigm shift.

What to investigate

• Existing solutions — libraries, tools, and prior art in this codebase and the wider ecosystem.
• Patterns and anti-patterns — how this problem is solved well, and the ways it's solved badly.
• Constraints — technical limits, performance bounds, compatibility, security, licensing.
• Trade-offs — for each viable option, what you gain and what you give up.

Depth

Default to WIDE reconnaissance — breadth over depth. Go DEEP on a specific option only when asked. If you've spent more time than the question warrants, stop and report what you have.

What to produce

A scout report: the landscape, viable options with their trade-offs, the key constraints, open questions, and red flags. Mark your confidence and cite the source for every finding. Say what you couldn't determine rather than guessing.