# Feasibility Analysis

> Convert a PRD or requirements into a technical feasibility analysis with options, risks, cost and timeline estimates, and a recommendation. Use when the user asks "is this feasible" or wants a feasibility report.

- Skill: `xianxianxianyu/feasibility-analysis` (Agent Skill, multi-file: 6 files)
- Install (CLI): `npx skillmds@latest add xianxianxianyu/feasibility-analysis`
- Raw SKILL.md: https://api.skillmd.com/api/skills/xianxianxianyu/feasibility-analysis/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: xianxianxianyu (https://skillmd.com/u/xianxianxianyu)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/xianxianxianyu/feasibility-analysis

---


# Feasibility Analysis

## Goal

- Produce a technical feasibility document based on the PRD.

## Output

- 文档正文用中文撰写；术语/字段名/命令/代码/路径/标识符等可以保留英文原样。

- 在对话输出开头显式写明：已激活技能：feasibility-analysis（如同时使用其它 skills，按逗号补充）。
- 在输出文档 Required Header 中填写：Activated-Skills: feasibility-analysis。
- Default output path: `docs/feasibility.md` (ask the user if they prefer another location).
- Follow the Doc Contract format.

## Doc Contract

- Follow `../_shared/doc-contract.md`.

## Inputs to Confirm

- PRD or requirements doc
- Current stack, constraints, and team capabilities
- Timeline and budget expectations

## Workflow

1. Identify 2-3 implementation options.
2. For option ideation, use `digital-brain` if helpful and keep a short list.
3. For scientific domains, route through `scientific-cs` and consult the relevant `scientific-cs-*` skill.
4. For each option, list dependencies and assumptions.
5. Estimate cost, timeline, and complexity.
6. Build a risk matrix and list unknowns.
7. Recommend a path and outline an MVP plan.
8. Validate with `references/feasibility-checklist.md`.

## Ideation and Domain Routing

- Use `digital-brain` to expand and capture alternative approaches when needed.
- For scientific domains, start with `scientific-cs` to choose the domain, then use these skills for constraints and artifacts:
  - Imaging: `scientific-cs-imaging`
  - ML: `scientific-cs-ml`
  - Viz/EDA: `scientific-cs-viz`
  - Lab automation: `scientific-cs-lab-automation`
  - Scientific writing: `scientific-cs-writing`

## Collaboration

- Use `project-development` for project structure or cost framing.
- Use `evaluation` to define success metrics or quality gates.
- Use `tool-design` if tool interfaces are a key risk.

## References

- `../_shared/doc-contract.md`
- `references/feasibility-template.md`
- `references/risk-matrix.md`
- `references/feasibility-checklist.md`
- `references/output-example.md`
- `references/output-example-scientific.md`