start

Route vague product-evaluation requests into outcome workflows and evidence planning.

14|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/sparkline-ventures/product-eval --skill start-sparkline-ventures
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start
Source: https://github.com/sparkline-ventures/product-eval/tree/main/skills/start
Command: npx skills add https://github.com/sparkline-ventures/product-eval --skill start-sparkline-ventures

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps users get oriented in product-eval and choose the right outcome path when they are starting from a vague goal, a broad product question, or a new investigation scope. It prevents premature analysis by first clarifying what decision the user is trying to make and what evidence should guide it.

Core Features & Use Cases

  • Route to the right outcome: Guides the user toward ranking opportunities, deciding on one bet, pressure-testing a plan, or writing an output.
  • Scope the investigation: Helps create or reuse a distinct investigation scope so evidence and decisions stay organized.
  • Set up the evidence plan: Asks for the product, users, decision goal, time horizon, available sources, and success metric or constraint before analysis begins.
  • Keep the workflow focused: Minimizes internal orchestration in the chat and keeps the conversation centered on the next useful business action.

Quick Start

Tell me what product decision you want to make, the product and users it applies to, and what evidence or sources I should use.

Frequently Asked Questions about start

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

FAQPage Schema
How do I scope a product evaluation when starting from a vague exploratory question?

Setting up an evidence plan for a new product investigation requires identifying your product context, target users, decision goal, time horizon, available sources, and a success metric or constraint. Establishing these parameters ensures your analysis remains focused and evidence-driven.

What is the best way to route broad product questions into actionable workflows?

Routing broad product questions into actionable workflows involves categorizing your decision goal to guide you toward ranking opportunities, deciding on one bet, pressure-testing a plan, or writing an output. This minimizes internal orchestration and focuses on the next useful business action.

Do I need a success metric to start an early-stage product decision analysis?

Yes, you need a value-shaping success metric or constraint to proceed safely with early-stage product decisions. Defining this metric alongside your product context and scope ensures the evaluation workflow has a clear benchmark for evidence planning and analysis.

How do I keep an investigation scope organized for broad product-evaluation requests?

You keep an investigation scope organized by creating or reusing a distinct investigation scope for each product-evaluation request. This ensures that evidence planning, decision goals, and workflow routing stay aligned and separated from other exploratory questions.

When should I avoid using workflow routing for product evaluation setup?

You should avoid using workflow routing if you lack the required product context, target users, decision goal, scope, evidence sources, and success metric. Without these inputs, the routing cannot safely guide you to the correct outcome workflow for your analysis.