How do I install the Pc Feasibility Study skill?

Run npx skillmds@latest add yknothing/pc-feasibility-study in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pc Feasibility Study safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pc Feasibility Study?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pc Feasibility Study free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pc Feasibility Study?

yknothing (@yknothing) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pc Feasibility Study by yknothing — Agent Skill

Name: Pc Feasibility Study
Author: yknothing

Pc Feasibility Study

Use when discovery has narrowed an idea enough that the team must make a go/no-go, pivot, or scope-down decision based on technical, economic, operational, or timeline viability before requirements, architecture, or major implementation.

yknothing e4bd248 4 files · 3.4 KB Updated Sep 17, 2026

File contents

Feasibility Study

Before committing resources, verify the idea can actually work -- technically, economically, and operationally.

Context

Feasibility is the gate between "interesting idea" and "committed project." It prevents wasting months on ideas that are technically impossible, economically unviable, or operationally unsustainable.

See context and anti-pattern notes.

Inputs

I/O contract notes define required inputs and authority.

Process

Step 1: Technical Feasibility

Can we build it?

Are the core technical challenges solvable with known technology?
Do we have (or can we acquire) the necessary expertise?
Are there hard technical constraints (latency, data volume, regulatory)?
What are the biggest technical risks?

Build a minimal proof-of-concept for the riskiest technical assumption.

Step 2: Economic Feasibility

Should we build it?

Estimated development cost (team size x duration x rate)
Estimated operational cost (infrastructure, support, maintenance)
Revenue model and projected income
Break-even timeline
Opportunity cost (what else could we build instead?)

Step 3: Operational Feasibility

Can we run it?

Do we have the team to maintain it long-term?
What operational burden does it create (on-call, support, compliance)?
Does it fit our existing operational capabilities?
What new capabilities would we need to develop?

Step 4: Timeline Feasibility

Can we ship in time?

Is there a market window we need to hit?
What's the minimum viable timeline?
What scope can be delivered in that timeline?

Step 5: Document Decision

Write a clear go/no-go/pivot recommendation:

Summary of findings across all dimensions
Key risks and mitigations
Recommended next steps (proceed to specification, pivot direction, or shelve)

Outputs

Produce only declared outputs at their documented quality boundary.

Quality Gate

All four feasibility dimensions assessed
Highest-risk technical assumption validated with POC or research
Cost/revenue model documented with assumptions explicit
Clear go/no-go/pivot recommendation with rationale

---name: pc-feasibility-studydescription: Use when discovery has narrowed an idea enough that the team must make a go/no-go, pivot, or scope-down decision based on technical, economic, operational, or timeline viability before requirements, architecture, or major implementation.---# Feasibility Study> Before committing resources, verify the idea can actually work -- technically, economically, and operationally.## ContextFeasibility is the gate between "interesting idea" and "committed project." It prevents wasting months on ideas that are technically impossible, economically unviable, or operationally unsustainable.See [context](references/context.md) and [anti-pattern](references/anti-patterns.md) notes.## Inputs[I/O contract notes](references/io-contract.md) define required inputs and authority.## Process### Step 1: Technical FeasibilityCan we build it?- Are the core technical challenges solvable with known technology?- Do we have (or can we acquire) the necessary expertise?- Are there hard technical constraints (latency, data volume, regulatory)?- What are the biggest technical risks?Build a minimal proof-of-concept for the riskiest technical assumption.### Step 2: Economic FeasibilityShould we build it?- Estimated development cost (team size x duration x rate)- Estimated operational cost (infrastructure, support, maintenance)- Revenue model and projected income- Break-even timeline- Opportunity cost (what else could we build instead?)### Step 3: Operational FeasibilityCan we run it?- Do we have the team to maintain it long-term?- What operational burden does it create (on-call, support, compliance)?- Does it fit our existing operational capabilities?- What new capabilities would we need to develop?### Step 4: Timeline FeasibilityCan we ship in time?- Is there a market window we need to hit?- What's the minimum viable timeline?- What scope can be delivered in that timeline?### Step 5: Document DecisionWrite a clear go/no-go/pivot recommendation:- Summary of findings across all dimensions- Key risks and mitigations- Recommended next steps (proceed to specification, pivot direction, or shelve)## OutputsProduce only declared outputs at their documented quality boundary.## Quality Gate- [ ] All four feasibility dimensions assessed- [ ] Highest-risk technical assumption validated with POC or research- [ ] Cost/revenue model documented with assumptions explicit- [ ] Clear go/no-go/pivot recommendation with rationale

Frequently asked questions