{ "generated_by": "innovator-hunt", "task_id": "T-mt5859wn", "date": "2026-08-23", "sources": [ { "id": "S-01", "claim": "Amazon Working Backwards / PR-FAQ 核心流程:先写≤1页新闻稿+2-5页FAQ(外部/内部各一类),新闻稿打动不了客户就在写代码前推翻或重做;Kindle/Prime/AWS 等据称经此流程孵化", "type": "external_url", "source": "https://workingbackwards.com/resources/working-backwards-pr-faq/", "verified": "unverified", "note": "由 WebSearch 检索获得,未逐字比对原始文档全文,来源为该方法论提出者(前 Amazon 高管 Colin Bryar / Bill Carr)官方网站,可信度较高但标记未核实(未做二次交叉验证)" }, { "id": "S-02", "claim": "PR/FAQ 是 Amazon 产品开发方法,本质是从客户视角倒推需求", "type": "external_url", "source": "https://workingbackwards.com/concepts/working-backwards-pr-faq-process/", "verified": "unverified" }, { "id": "S-03", "claim": "不存在单一'Google官方发布'的PRD模板;业界通行的Google风格PRD结构为 Context/Problem→Goals&Non-goals→User stories/Requirements→Success metrics", "type": "external_url", "source": "https://www.aha.io/roadmapping/guide/requirements-management/what-is-a-good-product-requirements-document-template; https://productschool.com/blog/product-strategy/product-template-requirements-document-prd", "verified": "unverified", "note": "多个二手聚合站点交叉印证,未找到 Google 官方一手发布文档,knowhow_v1.md §1.2 已明确标注此风险" }, { "id": "S-04", "claim": "Marty Cagan《Inspired》四大产品风险:价值风险/可用性风险/可行性风险/商业可行性风险", "type": "external_url", "source": "https://www.svpg.com/four-big-risks/", "verified": "unverified", "note": "来源为 Marty Cagan 本人所属机构 Silicon Valley Product Group 官网,可信度高,但未与《Inspired》原书文本逐字核对" }, { "id": "S-05", "claim": "四大风险应在产品发现阶段、动工前用便宜方式验证", "type": "external_url", "source": "https://internetgardener.substack.com/p/the-four-big-product-risks", "verified": "unverified" }, { "id": "S-06", "claim": "Shape Up Pitch 文档五要素:Problem/Appetite/Solution/Rabbit Holes/No-gos", "type": "external_url", "source": "https://basecamp.com/shapeup/1.5-chapter-06", "verified": "unverified", "note": "来源为 Basecamp 官方发布的 Shape Up 全文(该书官方站点),来源权威性最高,但仍标记未核实(未做逐字比对)" }, { "id": "S-07", "claim": "Solution 段刻意保持粗粒度(breadboard/fat marker sketch),反对过早收敛详尽规格", "type": "external_url", "source": "https://basecamp.com/shapeup/1.4-chapter-05", "verified": "unverified" }, { "id": "S-08", "claim": "CONVENTIONS.md 内容:时间格式/ID生成器/错误响应/DocStore工具/文件写入原子性/并发锁/SSE事件ID/日志策略/测试约定/命名风格/不变量速查,共12节;核心是DevLoop执行层约定而非PRD撰写方法论本身", "type": "internal_file", "source": "docs/prd/newfunction/_spec/CONVENTIONS.md", "verified": "verified", "note": "已完整读取原文并逐节确认" }, { "id": "S-09", "claim": "prd-planning 是本体名不带前缀;work graph 链路为 brd-planning→prd-planning→sdd-planning→goal-benchmark→planner-validator", "type": "internal_file", "source": "docs/todo/system-design/27-naming-conventions.md §二", "verified": "verified" }, { "id": "S-10", "claim": "prd-planning agent.md 全部原文摘录,包括第16-17行核心判据、第52-59行四类东西表格、第63-65行BRD回扣要求、第29行技术中立性要求、第121-122行traceability要求、第163-164行强制思维隔离第4条", "type": "internal_file", "source": "system/agents/prd-planning/agent.md", "verified": "verified", "note": "已完整读取原文172行并逐行核对引用的行号" }, { "id": "S-11", "claim": "e2e-demo案例 BRD 原文:谁在用/现状痛点/业务成功度量/范围/显式排除", "type": "internal_file", "source": "data/companies/e2e-demo/runs/run_c7d233619784/nodes/rn_36f1845d1b53/brd.md", "verified": "verified" }, { "id": "S-12", "claim": "e2e-demo案例 PRD 原文:功能清单F-1~F-4/行为规则/异常与边界/验收线索/traceability/继承排除范围,共66行", "type": "internal_file", "source": "data/companies/e2e-demo/runs/run_c7d233619784/nodes/rn_42eed93342c5/prd.md", "verified": "verified" }, { "id": "S-13", "claim": "e2e-demo案例 contract.json(同 prd.md 内容的结构化摘要)与 attempt-0.json(verdict=produced,无remediation回合,单轮通过)", "type": "internal_file", "source": "data/companies/e2e-demo/runs/run_c7d233619784/nodes/rn_42eed93342c5/{contract.json,attempt-0.json}", "verified": "verified" }, { "id": "S-14", "claim": "e2e-demo产出网站实际内容:index.html 仅含 hero(h1+一句副标题) + 三个 feature 区块(各一个h2+一句描述),全站0个img标签0个icon;styles.css 仅字号放大+padding留白,无背景图/插画", "type": "internal_file", "source": "data/companies/e2e-demo/projects/p-pyjha7/{index.html,styles.css}", "verified": "verified" } ] }