# Product Validation

> Pressure-test demand for a product or idea, diagnose an existing product’s growth ceiling, and define the smallest test for the riskiest assumption. Use when vetting an idea, interrogating weak demand, or choosing proceed, sharpen, or pause before building.

- Skill: `majesticlabs-dev/product-validation` (Agent Skill)
- Install (CLI): `npx skillmds@latest add majesticlabs-dev/product-validation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majesticlabs-dev/product-validation/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: majesticlabs-dev (https://skillmd.com/u/majesticlabs-dev)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/majesticlabs-dev/product-validation

---


# Product Validation

## Boundary

Own the executable demand test and proceed, sharpen, or pause verdict. Do not manufacture market evidence, require a full build, force precise scores from weak inputs, or run deceptive smoke tests.

## Required Inputs

- Idea or current product and intended buyer
- Observed demand, usage, retention, revenue, churn, and workaround evidence
- Founder or team advantage and distribution access
- Time, budget, technical, legal, and operational constraints
- Target jurisdictions, participant protections, data needs, and payment or fulfillment obligations

## Workflow

1. Choose new-idea or existing-product mode and state missing evidence.
2. Interrogate demand: named buyer, recent trigger, current workaround, cost, urgency, and demonstrated commitment.
3. For an existing product, calculate simple ceiling scenarios from observed acquisition and churn, with visible assumptions.
4. Identify the narrowest valuable wedge and the strongest status-quo competitor.
5. List fatal assumptions and rank them by evidence weakness and consequence.
6. Design a pre-build or low-build test that attacks the top assumption and minimizes participant cost and data collection.
7. Before launch, make availability and test status transparent, support every claim, avoid forced enrollment, and verify cancellation and deletion paths.
8. For any paid test, verify price, payment handling, fulfillment ability, cancellation, and refunds before collecting money. Escalate jurisdictional or regulated-product uncertainty to qualified counsel.
9. Set proceed, sharpen, and pause criteria before collecting results.
10. Return a verdict with counterevidence, unknowns, and a time-boxed next step.

## Output

1. **Verdict: proceed, sharpen, or pause**
2. **Demand and counterevidence summary**
3. **Ceiling scenarios when applicable**
4. **Fatal assumptions and smallest test**
5. **Decision date and criteria**

## Quality Gate

- Interest is not mislabeled as demand.
- Market and growth estimates use ranges and explicit assumptions.
- The test can invalidate the idea.
- Participants are not misled about availability, status, terms, or obligations.
- No unsupported claim, involuntary enrollment, unnecessary personal data, or unsafe paid commitment is used.
- The verdict names what evidence would change it.