product-validation-planner

原始内容

---
name: product-validation-planner
description: >-
  Help users with Validated demand: Founders and builders need a repeatable way to turn rough product ideas into validated plans, prototypes, and user-facing positioning. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for business-and-operations, product idea, validation, prototype, saas, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.
---

# Product Validation Planner

## Requirement

Use this skill to help solo founders, product managers, makers, and small teams who need to test whether a product idea is worth building before spending heavily with:

> Validated demand: Founders and builders need a repeatable way to turn rough product ideas into validated plans, prototypes, and user-facing positioning. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.

Demand score: 100/100 (`70/70` demand, `30/30` local feasibility).
Evidence: 12 signals across 3 source families.

Read `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.

## Workflow

1. Restate the user's outcome, constraints, available inputs, and success criteria.
2. Turn the operational problem into a repeatable process, checklist, template, or lightweight analysis.
3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.
4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.
5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.
6. Validate the output against the success criteria and list any remaining risks or follow-up work.

## Expected Outputs

- A tailored answer or artifact for the user's immediate situation.
- A reusable checklist or workflow when the task is repeatable.
- A verification note showing how the result was checked.

## Validation

- The output directly addresses the discovered requirement.
- The user can act on the result without reading the original source post.
- Assumptions, limits, and required inputs are visible.
- The final response includes a short usage or next-step note when helpful.

## Triggers

Keywords: `business-and-operations`, `product idea`, `validation`, `prototype`, `saas`, `startup`

Example trigger sentences:

- `Help me Founders and builders need a repeatable way to turn rough product ideas into validated plans, prototypes, and user-facin.`
- `I need a practical workflow for Founders and builders need a repeatable way to turn rough product ideas into validated plans, prototypes, and user-facin.`
- `Use $product-validation-planner to handle Founders and builders need a repeatable way to turn rough product ideas into validated plans, prototypes, and user-facin.`

name: product-validation-planner description: >- Help users with Validated demand: Founders and builders need a repeatable way to turn rough product ideas into validated plans, prototypes, and user-facing positioning. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for business-and-operations, product idea, validation, prototype, saas, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.

Product Validation Planner

Requirement

Use this skill to help solo founders, product managers, makers, and small teams who need to test whether a product idea is worth building before spending heavily with:

Validated demand: Founders and builders need a repeatable way to turn rough product ideas into validated plans, prototypes, and user-facing positioning. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.

Demand score: 100/100 (70/70 demand, 30/30 local feasibility). Evidence: 12 signals across 3 source families.

Read references/requirement-plan.md when source evidence, planning details, or review criteria are needed.

Workflow

Restate the user's outcome, constraints, available inputs, and success criteria.
Turn the operational problem into a repeatable process, checklist, template, or lightweight analysis.
Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.
Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.
Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.
Validate the output against the success criteria and list any remaining risks or follow-up work.

Expected Outputs

A tailored answer or artifact for the user's immediate situation.
A reusable checklist or workflow when the task is repeatable.
A verification note showing how the result was checked.

Validation

The output directly addresses the discovered requirement.
The user can act on the result without reading the original source post.
Assumptions, limits, and required inputs are visible.
The final response includes a short usage or next-step note when helpful.

Triggers

Keywords: business-and-operations, product idea, validation, prototype, saas, startup

Example trigger sentences:

Help me Founders and builders need a repeatable way to turn rough product ideas into validated plans, prototypes, and user-facin.
I need a practical workflow for Founders and builders need a repeatable way to turn rough product ideas into validated plans, prototypes, and user-facin.
Use $product-validation-planner to handle Founders and builders need a repeatable way to turn rough product ideas into validated plans, prototypes, and user-facin.