360 Secure SkillHub
360 安全技能中心

Product Validation Planner

该技能帮助独立创始人、产品经理和小团队在投入开发前验证产品想法。它提供可重复的流程、检查清单、模板和轻量分析，用于形成验证计划、原型方向和面向用户的定位，并给出验证说明与后续步骤。输出基于用户提供的想法、约束和成功标准，不依赖外部服务或宿主专属运行时。

kyro-ma
kyro-ma
热度 9.67
最近更新 2026-07-29 11:34:14
分类：效率依赖：内部调用大模型 / 读写文件应用场景：工作流 / 模板 / 市场分析 / 研究 ...

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add product-validation-planner-120606
Metadata
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.