Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Chris1Wang3/Idea-on-Trial --skill pm-requirement-review-simulatorgit clone --depth 1 https://github.com/Chris1Wang3/Idea-on-TrialWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/chris1wang3/idea-on-trial/pm-requirement-review-simulator)<a href="https://agentmods.dev/skills/chris1wang3/idea-on-trial/pm-requirement-review-simulator"><img src="https://agentmods.dev/badge/skills/chris1wang3/idea-on-trial/pm-requirement-review-simulator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/chris1wang3/idea-on-trial/pm-requirement-review-simulator"><img src="https://agentmods.dev/badge/skills/chris1wang3/idea-on-trial/pm-requirement-review-simulator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00078 | $0.02023 |
| Opus 5 | $0.00039 | $0.01012 |
| Sonnet 5 | $0.00016 | $0.00405 |
| Haiku 4.5 | $0.00008 | $0.00202 |
Grade A, and why
pm-requirement-review-simulator scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM 需求评审模拟器
EN Five roles stress-test your PRD before the real meeting → survival score + meeting assets.
中文 五角色预演评审攻防 → 存活率报告 + 会议脚本。
When / 何时用： 评审前预演 · 跨部门博弈 · 会议资产准备
Not / 不用： 从零写 PRD · 上线后全面复盘 · 替用户拍板
Review our group-buying feature.
帮我评审拼团功能。
结构化输入 → user_templates.md
可直接触发的说法
以下口语输入都应触发本技能，不要求用户先提交完整 PRD：
- 帮我预演一下这个需求评审会。
- 这个 PRD 会被研发/运营/老板怎么怼？
- 我只有草稿，先帮我评一下。
- 帮我准备评审会上可能被问的问题和回答。
- 这个需求能不能过会？给我存活率。
- 严格挑战一下这个方案。
- 评审前帮我生成 RACI、会议脚本和行动清单。
最小可用输入
最低可启动：需求名称 + 核心功能。若缺业务目标，先按“提升关键业务指标”预填并要求用户确认。
推荐输入：业务目标、用户场景、核心功能、约束条件、技术依赖、评审角色、PRD 来源（完整 PRD / 展示版 / 草稿 / 口述）、输出格式。
可兼容输入：
- 只有草稿：按“草稿 PRD”评审，缺失项保守分 1。
- 只有展示版：启用展示版评分校准，不因合理脱敏项过度扣分。
- 只有链接/截图：先提取可见需求，再标注不可见缺口。
- 用户说“直接生成”：只跳过业务信息追问，缺失项按保守分处理；不视为跳过输出格式确认。
工作流
1) 提交需求 2) 信息采集清单 3) 识别类型 + PRD 来源 + N/A 维度
4) 五角色标准评审 5) 子项打分 → 存活率 6) 按用户选择生成 HTML / Markdown 报告 + 会议资产
信息采集清单（第 2 步）
1️⃣ 需求名称 2️⃣ 业务目标 3️⃣ 核心功能 4️⃣ 行业 5️⃣ 公司规模 6️⃣ 技术栈
7️⃣ 约束 8️⃣ 评审角色 9️⃣ 需求类型 🔟 N/A 维度 1️⃣1️⃣ PRD 来源 1️⃣2️⃣ 输出格式（HTML / Markdown）
跳过项保守分 1。
采集交互（优先使用可操作表单）：
-
必须直接复用 assets/intake-form.html，不得由 Agent 临时拼装另一套清单 UI；该文件是跨 Agent 稳定展示的唯一表单实现。
-
当前环境支持对话内交互页面/可视化控件时，将上述 12 项渲染为可编辑表单，而非只输出文本清单。
-
需求名称、目标、功能、技术栈与约束允许编辑；PRD 来源与需求类型使用单选；评审角色与 N/A 维度使用复选；输出格式不预选。
-
推断值标记
[推断]；展示版/草稿来源必须显式显示，避免按完整 PRD 误评。 -
提交按钮使用“确认清单并开始评审”，提交后按
{schema_version:"1.0", skill, action, data}回传结构化参数；优先window.codex.submitForm，兼容window.openai.sendFollowUpMessage，再进入类型识别、角色质疑与评分。 -
当前环境不支持交互页面时，才退回文本清单；格式未确认不得生成，用户明确委托默认时使用 HTML。
五角色 × 五维
| 角色 | 主评维度 |
|---|---|
| 🛠️ 技术 | 技术友好 |
| 📈 运营 | 运营价值 |
| 🎨 设计 | 运营价值 |
| 👔 老板 | 老板满意 |
| ⚖️ 法务 | 合规安全 |
五维：逻辑自洽（永不 N/A）· 技术友好 · 运营价值 · 老板满意 · 合规安全。公式 → scoring-engine-deterministic.md。
输出
按采集表确认的格式生成：HTML 使用 report-template-pro.html；Markdown 使用同一评审结构。格式锁与自检 → review-playbook.md。
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 138 lines · 78 tokens per session scan A 0c2492196d02
pm-requirement-review-simulator is a skill published in the GitHub repository Chris1Wang3/Idea-on-Trial (4 stars, last pushed 23d ago), licensed MIT. It adds 78 tokens to every session and 2,023 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
jira-bug-reporter
Create detailed bug reports from session evidence — auto-populate Jira tickets with session URLs, error messages, device info, and reproduction steps. Use when the user wants to file a bug from a Fullstory session.
asc-submission
Prepare an app for App Store submission or TestFlight distribution using the App Store Connect MCP server. Use when user says "prepare submission", "submit to app store", "prepare for review", "update metadata", "set what's new", "check submission readiness", "distribute to testflight", or wants to manage App Store…
influencer-marketing-manager
Provides business judgment and management for influencer and creator partnerships. Use for goals, creator strategy, cross-stage decisions, SOPs, or automation. Also use for concise, stage-specific operator-tool guidance, even without tool execution, when operational evidence must support the next marketing decision.…
atlassian-jira-sync
Sync Jira issues with local tasks. Use during daily planning or when user asks about Jira issues.
linear-issue-sync
Sync Linear issues with local tasks. Use during daily planning or when user asks about Linear issues.
jira-issue-sync
Sync Jira issues with local tasks. Use during daily planning or when user asks about Jira issues.