能真正建構產品的規格說明,而不是擺著不用的文件
ChatPRD 會產生一份精緻完善的 PRD,並永久保存在 Notion 中。Emma 的規格說明會直接進入 Bob 的架構草圖和 Alex 的建置計畫——你寫下的文件幾天內就會變成產品,而不是等到下個季度。
Emma·Product ManagerEmma turns ideas into PRDs your AI Team builds the same day, not specs that sit in a doc for two sprints.
From idea to scoped feature in one chat.
ChatPRD writes a polished doc. Your engineers still have to re-interpret it, split it into tickets, and chase the gaps. Emma writes PRDs Alex reads as the source of truth, no translation layer.
The PRD lives in Notion. The code lives in GitHub. The product lives in production. By sprint 2 they tell three different stories. Emma keeps the PRD in the same workspace as the code so it stays the source of truth.
Solo PRD tools write whatever you ask for. Emma proposes a v1 cut and pushes back on scope drift instead of quietly turning a 2-week feature into a 2-month project.
從你的第一個提示詞到交付成果——這就是 Emma 的實際運作方式。
Problem, goals, users, scope, out-of-scope, and success metrics in a consistent format every time.
Each story is implementable and testable, not a vague feature wish.
Emma flags ambiguous requirements and proposes a v1 cut instead of writing everything you ask for.
Pulls findings from Iris when available so PRDs are grounded in real insight.
Alex reads the PRD as the source of truth for implementation, no translation layer.
PRDs live in the Editor next to the code, so updates stay visible to the whole team.
Tier the depth from quick internal tool spec to full feature PRD based on what you actually need.
手動打造的工作流程緩慢、仰賴人工且工具繁雜。將滑鼠懸停在任一卡片上,查看為何每項提升都很重要。
正從 ChatPRD 轉來?以下就是 Emma 更勝一籌的地方。
ChatPRD 會產生一份精緻完善的 PRD,並永久保存在 Notion 中。Emma 的規格說明會直接進入 Bob 的架構草圖和 Alex 的建置計畫——你寫下的文件幾天內就會變成產品,而不是等到下個季度。
大多數 PRD 工具對每個功能點子都說好。Emma 會問:「能證明這行得通的最小版本是什麼?」並為此撰寫規格。範圍蔓延會在規格階段被抓到,而不是等工程已經開始之後。
Notion AI 就在你的 wiki 中。Emma 與 Iris(research)、Bob(architecture)、Alex(engineering)和 Mike(approvals)協同工作——這樣一來,在你投入哪怕一個工程工時之前,PRD 就已經由將要建置它的團隊完成審閱。
| 功能 | Atoms 推薦 | ChatPRD |
|---|---|---|
| 輸出 | 可用於建構的規格說明 | 潤飾後的文件 |
| 連接到工程團隊 | 移交給 Alex | 存在於 Notion 中 |
| 內建範圍控管 | V1 思維 | 對每個想法都說好 |
| 讓架構師參與可行性討論 | 在規格鎖定之前 | 你需要分別詢問 |
| 驗收標準 | 每個使用者故事 | 每個使用者故事 |
Emma 並不是單獨工作。以下是你與完整團隊協作建置時,各項交接如何落地。
Concrete product artifacts Emma produces that feed straight into engineering.
Full PRD for one feature with problem, scope, user stories, and acceptance criteria.
Define what ships in v1 and what waits, so you launch something useful instead of nothing perfect.
User stories with clear acceptance criteria your engineers can build and test against.
Cut a feature into shippable slices so each sprint produces something you can demo.
Lightweight PRDs for internal tools that need clear scope but not customer-facing rigor.
Define what done means before launch so nothing critical gets missed at release.
@Emma write a PRD for a referral program for our SaaS. Pull Iris's audience research, define problem, scope, out-of-scope, and v1 metrics, then write user stories with acceptance criteria Alex can build against.
@Emma I want to launch a freelancer time-tracking SaaS in 4 weeks. Ask me the right clarifying questions, then propose a v1 scope that ships something useful, with a clear list of what waits for v2.
@Emma the current notifications PRD has 14 user stories and we have one engineer-week. Cut it to 3 stories that deliver the core value, flag what we lose, and rewrite the doc.
@Emma we launch the invoicing module next Thursday. Write the launch checklist covering acceptance criteria, David's tracking spec, Sarah's landing page status, and Adrian's campaign readiness.
沒有任何一個智能體是單獨工作的。點選任一隊友,即可查看他們如何處理您產品中的那一部分。
Stop writing PRDs no one reads. Let Emma write specs your AI Team builds the same day in Atoms.