skills.rest
withkynam
withkynamCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

vc-feasibility-test

Run one-shot feasibility probes and produce a VIABLE/NOT-VIABLE/INCONCLUSIVE VERDICT artifact.

1.1k|223|Updated May 27, 2026
Search Tags:#feasibility#probe#verdict#layer-2#external-mechanism#vc-debugger
One-click install
npx skills add https://github.com/withkynam/vibecode-pro-max-kit --skill vc-feasibility-test
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vc-feasibility-test
Source: https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-feasibility-test
Command: npx skills add https://github.com/withkynam/vibecode-pro-max-kit --skill vc-feasibility-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill helps teams decide whether unverified external mechanisms will work before locking a design.

Core Features & Use Cases

  • Run one-shot feasibility probes across the 8 probe families to test a mechanism.
  • Produce a VIABLE/NOT-VIABLE/INCONCLUSIVE VERDICT artifact and a Resulting Design Constraint summarizing licenses, forbids, and uncertainties.
  • Integrate with vc-debugger workflow for automated gating between SPEC, INNOVATE, and VALIDATE phases, including PVL context.

Quick Start

Provide a hypothesis and a task folder to run a one-shot feasibility probe before locking a design.

Frequently Asked Questions about vc-feasibility-test

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

FAQPage Schema
How do I verify an unverified external mechanism before locking a software design?▼

Run a one-shot feasibility probe against the external mechanism to test if the runtime or library works as assumed. This generates a VIABLE, NOT-VIABLE, or INCONCLUSIVE verdict artifact to guide design locking decisions.

What is a feasibility probe and when do I need to run one?▼

A feasibility probe is an empirical test validating uncertain external mechanisms or libraries. You need to run one when SPEC, INNOVATE, or VALIDATE layer-2 design decisions depend on an unverified mechanism working as assumed.

How do I test external library compatibility during the SPEC or VALIDATE phases?▼

Test external library compatibility by specifying a probe family and cost class to empirically evaluate the mechanism. This yields a verdict artifact and a resulting design constraint summarizing licenses, forbids, and uncertainties.

Can I use a feasibility probe to automate gating between SPEC and VALIDATE phases?▼

Yes, you can automate gating between SPEC, INNOVATE, and VALIDATE phases by integrating probes with the vc-debugger workflow. This uses PVL context and verdict artifacts to gate phase transitions.

What are the limitations of running a feasibility test on an external mechanism?▼

A feasibility test may return an INCONCLUSIVE verdict if the external mechanism cannot be fully verified. The output artifact then summarizes remaining uncertainties, forbids, and licensing constraints as a resulting design constraint.

Related Skills

Explore More Software Engineering Skills→
yuyuxinliyuyuxinli
1

pol-probe

Validate falsifiable hypotheses with disposable PoL probes before production development.

Official
Advanced
withkynamwithkynam
1.1k

vc-generate-spec

Generate a plain-language product-discovery SPEC from research findings and user intent.

Community
Advanced
vikingokftvikingokft

stitch::generate-design

Generate web or mobile design screens from prompts using Stitch MCP.

Official
Advanced
lovecrushfamilylovecrushfamily
1

vc-feasibility-test

Run empirical probes to evaluate external API and library viability.

Community
Advanced