feasibility-analysis

Investigates unfamiliar technology and constraints to produce sourced feasibility options and trade-offs.

4|Updated Jun 19, 2026
One-click install
npx skills add https://github.com/douglance/sdlc-plugin --skill feasibility-analysis-douglance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feasibility-analysis
Source: https://github.com/douglance/sdlc-plugin/tree/main/.rulesync/skills/feasibility-analysis
Command: npx skills add https://github.com/douglance/sdlc-plugin --skill feasibility-analysis-douglance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a project involves unfamiliar technology or unclear constraints, teams risk committing to an approach before knowing whether it is viable. This Skill performs wide reconnaissance across the codebase, Context7, and web search to map existing solutions, constraints, and trade-offs before any approach is chosen. ## Core Features & Use Cases - Landscape Scouting: Surveys existing libraries, tools, prior art, patterns, and anti-patterns both in the codebase and the wider ecosystem. - Sourced Scout Report: Produces viable options with trade-offs, key constraints, open questions, red flags, and confidence levels, with every claim traced to a source. - Simplifying-Insight Check: When rules and workarounds protect a questionable model, it runs a falsifiable check before recommending a paradigm shift. - Use Case: Before adopting a new real-time messaging framework, use this Skill to survey candidate libraries, document licensing and performance constraints, and deliver a sourced comparison for the team to decide on. ## Quick Start Run a feasibility analysis on using GraphQL federation for our services and produce a sourced scout report with options, constraints, and open questions.

Frequently Asked Questions about feasibility-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate whether a new technology is feasible for my project?▼

Run a feasibility analysis that scouts existing solutions, patterns, and constraints across your codebase and the wider ecosystem. The output is a scout report listing viable options with trade-offs, key constraints, open questions, and red flags, each claim cited to a source.

What should a technical feasibility report include?▼

A feasibility scout report should include the landscape of existing solutions, viable options with trade-offs, technical constraints such as performance, compatibility, security, and licensing, plus open questions and red flags. Confidence levels and sources should accompany every finding.

When should I do a feasibility analysis before choosing an approach?▼

Run it whenever the technology or constraints are unfamiliar and a bounded investigation can proceed independently. Default to wide reconnaissance across many options, and go deep on a specific option only when explicitly asked.

How do I know when to challenge an existing architecture instead of extending it?▼

Challenge the current model when rules, exceptions, adapters, or compensating processes appear to protect a questionable design. Keep the current model as the null hypothesis and require a falsifiable prediction before recommending a paradigm shift.

What are the limitations of a wide feasibility reconnaissance?▼

Wide reconnaissance favors breadth over depth, so individual options are not fully validated. It reports what could not be determined rather than guessing, and deep dives on a specific option require a separate, focused investigation.