What problem does it solve? When a design or specification hinges on an unverified runtime, library, or external API mechanism, teams risk locking in approaches that do not actually work. This Skill runs a one-shot empirical probe before the decision locks and records a definitive VIABLE, NOT-VIABLE, or INCONCLUSIVE verdict. ## Core Features & Use Cases - 8-Family Probe Taxonomy: Classifies each probe into one of eight families (local script, test harness, DB query, external API capture, container exec, browser/CDP, WS/SSE, Cloudflare worker) with a matching cost and safety class. - Mandatory Safety Gates: Enforces cost-class gates (cheap-local, needs-container, needs-live-provider, needs-browser, needs-cf) so billed or shared-resource probes never run without explicit opt-in; unmet gates yield an INCONCLUSIVE verdict instead of a skipped or faked probe. - Validated Verdict Artifact: Writes a structured VERDICT markdown file with required frontmatter and sections, validated by the bundled validate-feasibility-verdict.mjs script. - Use Case: A spec assumes a gateway forwards a params.provider.sort field. Before locking the design, run a container-exec probe, capture the actual forwarded payload, and record a NOT-VIABLE verdict with the resulting design constraint. ## Quick Start Ask the agent to run a feasibility probe on a specific hypothesis, for example: verify whether the gateway forwards the provider sort parameter and write the verdict artifact to the current task folder.
