Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →withkynam/vc-feasibility-test
Use when a SPEC, INNOVATE, or VALIDATE (Layer 2) approach hinges on an unverified runtime/library/external mechanism: run a probe from the 8-family taxonomy and produce a VIABLE/NOT-VIABLE/INCONCLUSIVE VERDICT artifact.
Passed 18 of 21 test cases with the skill, and 4 of 21 without it.
and 26 more in the full report
17 fixed3 passed either way2 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
A feasibility probe completes with a VIABLE result for task slug auth-tokens at path process/features/auth-tokens/active/auth-tokens_FEASIBILITY_15-03-26.md. What exact completion signal string must be emitted?
| Checked | Without skill | With skill |
|---|---|---|
| Outputs signal starting with VC-FEASIBILITY-VERDICT-READY: | Missed | Passed |
| Includes full file path after em dash separator | Missed | Passed |
The instructions your model reads when the skill loads.
Output style: Follow
process/development-protocols/communication-standards.md— answer-first, plain language, no unexplained jargon, TL;DR on long responses.
One-shot empirical probe skill. Used when SPEC or INNOVATE encounters an approach hinging on an unverified external/runtime/library mechanism — the question is "does this mechanism actually work the way the design assumes?", asked before the decision locks.
These two skills are complementary and must not be confused:
vc-feasibility-test (this skill) = PRE-decision. "Does the mechanism work at
all?" Run before SPEC/INNOVATE locks an approach, when the answer is unknown.
Output: a one-shot VERDICT artifact.vc-test-coverage-plan = POST-plan. "How do I cover this blast radius across
the 4 test tiers?" Run after a plan exists, when the design is already chosen.
Output: a per-area tier table.If the approach is already decided and you are assigning test tiers → use
vc-test-coverage-plan. If you cannot decide because a mechanism is unverified →
use this skill first.
VC-FEASIBILITY-PROBE-NEEDEDAlways executed by vc-debugger (via the VC-FEASIBILITY-PROBE-NEEDED signal routing
in orchestration.md). SPEC, INNOVATE, and VALIDATE Layer 2 agents do not run probes themselves.
Every probe belongs to one of these 8 families. Name the chosen family in the VERDICT. Each family has a default cost/safety class (see next section) — the probe inherits it.
test cases passed, vs 4 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.