Individual skill

mini-program-product-spec-skill

Convert a vague mini-program idea, feature request, or partially documented product into an evidence-calibrated product specification with target users, core problem, version-one scope, main and exception flows, page responsibilities, state matrices, and testable acceptance criteria. Use when users ask to define an MVP, clarify requirements, organize product flows, specify page behavior, resolve ambiguous product states, or prepare a stable handoff before architecture or implementation. Separates facts, user decisions, assumptions, unknowns, and future ideas; never invents product logic merely to complete a screen or technical plan.

skills/mini-program-product-spec-skill/SKILL.md

Read pinned source

Source commit 2b7f9cb24f142125189b8757fcea489546d76ba7

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
95
Repository last updated
Nov 3, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# /mini-program-product-spec-skill — 小程序产品规格

把模糊想法收敛为可交接、可验证的小程序产品规格。只定义“用户需要什么、在什么条件下发生什么”,不决定代码结构,也不直接实现页面。

## 输入与边界

- 可接收一句想法、需求记录、原型、现有页面说明或只读项目事实图。
- 先区分用户已确认事实、当前产品事实、有依据的假设、未知项和未来规划。
- 缺少的信息不会改变核心闭环时,采用最小且明确标注的假设继续;会实质性改变用户、价值、数据规则、付费、权限或主流程时,列为决策点。
- 不发明按钮、入口、奖励、社交、付费、广告、数据规则或异常处理来填满页面。
- 不决定代码结构、框架、数据库、API 形态或微信平台配置;这些分别交给架构和平台阶段。

## 规格流程