Startup V1 Feasibility

When to use

Use when a captured, grilled, and validated startup problem has enough evidence to justify deciding what to build first.

This skill prevents v1 scope creep. The first version should test the riskiest useful assumption, not become a miniature version of the imagined company.

If the user has not run a validation test or cannot provide credible evidence from real prospects, do not produce a build plan by default. Return a Not build-ready verdict, list the missing evidence, and route them back to validation. Only produce a planning-only sketch when the user explicitly asks for a hypothetical plan and label it as unvalidated.

Core principle

A good v1 is small enough to build in 2–4 weeks and sharp enough that real user behaviour teaches something commercially useful.

Workflow