visa-coletor

Generate executable evidence-collection plans for hypothesis gaps.

Updated May 4, 2026
One-click install
npx skills add https://github.com/Adgmed2018/visa --skill visa-coletor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: visa-coletor
Source: https://github.com/Adgmed2018/visa/tree/main/agents/visa-coletor
Command: npx skills add https://github.com/Adgmed2018/visa --skill visa-coletor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Resolve hypothesis gaps by generating executable evidence collection plans (interviews, market tests, MVPs, and public data analyses) to ensure evidence exists before advancing.

Core Features & Use Cases

  • Converts vague assumptions into concrete, testable plans that specify evidence types, recruiters, and validation criteria.
  • Produces templates for interviews, surveys, smoke tests, and MVPs that align with the discovery pipeline.
  • Integrates with the existing visa context to maintain traceability of gaps and evidence plans.

Quick Start

Generate a concrete evidence plan for the current hypothesis gaps using the project context.

Frequently Asked Questions about visa-coletor

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

FAQPage Schema
How do I convert hypothesis gaps into testable evidence plans?

Resolve hypothesis gaps by generating executable evidence collection plans that specify evidence types, recruiters, and validation criteria. This translates vague assumptions into concrete interviews, surveys, smoke tests, and MVPs.

What is the best way to plan discovery interviews and MVP tests for product validation?

Plan discovery interviews and MVP tests by generating concrete templates aligned with the discovery pipeline. This ensures evidence specifies validation criteria and recruiters before advancing the product.

How do I create validation criteria for surveys and smoke tests from vague assumptions?

Create validation criteria for surveys and smoke tests by converting vague assumptions into executable evidence collection plans. The process specifies required evidence types and templates directly from the current gap context.

Do I need existing gap context to generate evidence collection plans?

Yes, you need existing gap context from the project state and gaps documentation to generate evidence collection plans. This context is required to craft concrete templates and validation criteria for the discovery pipeline.

Why use an evidence plan for product discovery instead of building an MVP directly?

Using an evidence plan for product discovery ensures testable evidence exists before advancing. It traceably links hypothesis gaps to specific validation methods like interviews and public data analyses, preventing premature MVP builds.