feasibility-assessor

Evaluate business ideas across financial viability and technical feasibility with de-risking steps.

310|45|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/Mathews-Tom/armory --skill feasibility-assessor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feasibility-assessor
Source: https://github.com/Mathews-Tom/armory/tree/main/skills/feasibility-assessor
Command: npx skills add https://github.com/Mathews-Tom/armory --skill feasibility-assessor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Evaluate business ideas and features across financial viability and technical feasibility to deliver an integrated verdict with actionable de-risking recommendations.

Core Features & Use Cases

  • Integrated feasibility analysis: combines unit economics, break-even considerations, and architecture risk scoring to guide go/no-go decisions.
  • Structured outputs: returns a clear verdict plus recommended next steps and risk mitigations for both business and engineering teams.
  • Use case coverage: ideal for evaluating new product concepts, feature bets, or pivots, with explicit inputs for financial modeling and technical risk.

Quick Start

Provide a concise idea description and key inputs (CAC, LTV, gross margin, and technology risk) to obtain an integrated feasibility verdict.

Frequently Asked Questions about feasibility-assessor

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

FAQPage Schema
How do I assess the financial viability and technical feasibility of a new product concept?

To assess financial viability and technical feasibility, provide your value proposition, target customers, pricing intent, and technology stack. The analysis combines unit economics, break-even considerations, and architecture risk scoring to deliver an integrated go/no-go verdict.

What inputs are needed to calculate ROI projections and unit economics for a feature bet?

Calculating ROI projections and unit economics requires key assumptions like CAC, LTV, gross margin, and technology risk. Providing these explicit inputs allows the assessment to output a structured feasibility verdict with actionable de-risking next steps.

Can I use this approach to evaluate pivots and go/no-go decisions for my business case?

Yes, you can evaluate pivots and go/no-go decisions by supplying a concise idea description alongside financial modeling and technical risk inputs. It is ideal for feature bets and new product concepts, returning clear risk mitigations for both business and engineering teams.

What is the best way to combine architecture risk scoring with unit economics for a build estimate?

The best way to combine architecture risk scoring with unit economics is through an integrated feasibility analysis. This method evaluates your technology stack and financial inputs together, delivering a structured assessment that guides technical build estimates and business viability.

Why does my feasibility assessment require explicit inputs like pricing intent and target customers?

A feasibility assessment requires explicit inputs like pricing intent and target customers to accurately model unit economics and project ROI. Without these key assumptions, the integrated verdict cannot generate actionable de-risking recommendations for your business case.