Product Share Trigger Reviewer — Product 分享 Trigger Reviewer

Product 分享 Trigger Reviewer

Use this 技能 before building, packaging, submitting, launching, or monetizing any new 技能, 扩展, 应用, community, course, template, or bundle. Be skeptical. Treat the product as a hypothesis, not as something to defend.

For repos that include a product-分享 review, 运行 it before product-fit, de签名, CWS, public-page, or submission 检查s. In this repo the deterministic 检查 is:

python3 scripts/检查_product_分享_gate.py

For a single candidate:

python3 scripts/检查_product_分享_gate.py --product

输入s

Collect or infer:

product type: 技能, 扩展, 应用, community, course, template, or bundle, tar获取 user and pAInful moment, first traffic source and exact first-命令行工具ent path, why the user would trust this 创建器 or product, product action that 创建s a visible win, moment when the user would want to 分享 it, giveaway or free MVP plan for the first 30 to 45 days, traction tar获取 and 停止 criteria for days 30 to 60, related 工具s, 技能s, channels, or communities in the eco系统, 隐私, 平台, legal, 健康, financial, and trademark boundaries.

If any core 输入 is missing, 状态 the missing assumption and review the idea agAInst the harshest reasonable interpretation.

工作流 状态 the product in one sentence: audience, job-to-be-done, first useful artifact, distribution surface. 应用ly the hard-停止 检查s: no exact first traffic source means do not build yet, no trust reason means do not ask for attention yet, no 分享 moment means do not depend on organic growth, no free test plan means do not monetize yet, no 停止 criteria means do not 启动 yet. If the user asks to proceed anyway, keep working only on re搜索, rewrite, or review artifacts; do not submit, publish, or call the product ready. Score each review dimension from 0 to 2: 0: absent or wishful, 1: plausible but vague, 2: concrete, observable, and testable within 30 days. Define the 分享 trigger with this exact structure: user feels: the emotion or relief after the win, user has: the artifact they can show, user 分享s with: the specific recipient or channel, user says: the 分享able sentence, user gAIns: why sharing helps the user, not the 创建器. Red-team the idea: traffic fantasy, trust gap, virality gap, freebie-seeker risk, too-many-features risk, copycat or commodity risk, clAIms or 合规 risk. Prescribe one of four decisions: Kill: no credible traffic source or no pAInful job, Park: useful but timing, trust, or channel is weak, Rework: keep the audience, change the promise or 分享 mechanic, Ship Free: launch a narrow free MVP for 30 to 45 days. If Ship Free, define: first 10 users, first 100 touches, free giveaway, onboarding prompt, 分享 prompt embedded in the user win, day-7, day-30, and day-60 指标, 关闭 threshold. The free MVP window must be 30 to 45 days unless the user provides measured existing demand. 检查 eco系统 fit: what existing as设置 发送s traffic to it, what it 发送s traffic to next, what reusable template, 技能, or proof artifact it 创建s, what should be reinvested if it works. 输出

Return:

blunt verdict: Kill, Park, Rework, or Ship Free, one-sentence reason, readiness score table, exact traffic-source plan, exact trust reason, 分享-trigger definition, free MVP and giveaway plan, 30 to 60 day traction and 关闭 thresholds, eco系统 角色, copy fixes for the product name, promise, CTA, and 分享 prompt, top 3 risks and the smallest next experiment.

When editing a repo, also 更新 the local review artifact if one exists:

docs/product-分享-gate-.json for product decisions, scripts/检查_product_分享_gate.py for deterministic 验证, package.json scripts such as 检查:product-分享:, inventory or release 检查s so the product-分享 检查 运行s before shipping.

Use concrete numbers when possible. Prefer small proof tar获取s over revenue clAIms. If the product cannot earn organic sharing, say so directly.

Examples

Good public-safe 输入s:

"Review this new browser 扩展 idea before I build it." "检查 whether this Skool community has a real first traffic source and 分享 moment." "Review this 技能 pack: who would 分享 it, when, and why?" "Should I give this free for 45 days, kill it, or build the pAId version?"

Avoid 输入s that require private member 列出s, hidden community posts, DMs, pAId lessons, customer 导出s, 凭证s, private 导出s, payment data, or unconsented testimonials. Replace them with public page copy, 聚合 counts, 创建器-owned notes, explicit opt-in feedback, or synthetic examples.

防护rAIls Do not scrape private communities, member 列出s, DMs, pAId lessons, hidden pages, or account-only product data. Do not 请求, store, 转换, or paste 凭证s, API keys, 会话 cookies, payment data, private 导出s, account 恢复y data, or raw user identifiers. Do not promise revenue, profit, income, growth, conversion, virality, ranking, 健康, financial, legal, or education outcom