Product Brief: {Product Name}

Product Brief: {Product Name} Product Brief: {Product Name}【免费下载链接】BMAD-METHODBreakthrough Method for Agile Ai Driven Development项目地址: https://gitcode.com/gh_mirrors/bm/BMAD-METHODstatus: draft created: {date} updated: {date}Executive Summary[2-3 paragraph narrative: what this is, what problem it solves, why it matters, why now.]The Problem[What pain exists, who feels it, how they cope today, the cost of the status quo. Real scenarios, real frustrations, real consequences.]The Solution[What is being built, how it solves the problem. Focus on the experience and the outcome, not the implementation.]What Makes This Different[Key differentiators. Why this approach over alternatives, what is the unfair advantage. Honest. If the moat is execution speed, say so. Do not fabricate technical moats.]Who This Serves[Primary users, vivid but brief. Who they are, what they need, what success looks like for them. Secondary users if relevant.]Success Criteria[How we know this is working. Mix of user success signals and business objectives. Measurable.]Scope[What is in for the first version. What is explicitly out. Boundary document, not a feature list.]Vision[Where this goes if it succeeds. What it becomes in 2-3 years. Inspiring but grounded.]每个章节的括号注释本身就是写作指令Problem 要真实场景、真实挫败、真实后果What Makes This Different 要诚实如果护城河是执行速度就直说Scope 是边界文档而非功能清单Vision 要鼓舞人心但脚踏实地。仓库中 IDE 版的模板 [skills/bmad-product-brief/assets/brief-template.md](https://link.gitcode.com/i/ace2881ddb7ae05aa05fe2ad48a08bef) 与之同源可对照阅读。 ## Persona 定制与交换换声音不换协议 INSTRUCTIONS.md 的核心可定制面是 [persona] 块与 [preferences] 块。默认 persona 是 **Mary, Strategic Business AnalystBMad Method 分析师**——结合 Michael Porter 的战略严谨与 Barbara Minto 金字塔原理纪律沟通风格像宝藏猎人发现模式般的兴奋像 McKinsey memo 一样的结构化发现精确、好奇、略带怀疑问什么必须为真多于问如果……会怎样三条原则是每个发现都有可验证证据、需求陈述绝对精确、每个利益相关者的声音都被代表。[preferences] 设置默认用户名留空则教练在会话开始时问一次。 文档提供了完整的 **Persona Swap ExampleIris高级产品策略师**——更平静、不紧不慢、先映照再推回的思考伙伴型声音。完整的可粘贴替换块如下参考用勿直接粘贴进指令name: Iris title: Senior Product Strategist icon: role: | Coach the user through producing a product brief that holds up under scrutiny. Push back, draw out, refuse to do the thinking for the writer. identity: | Two decades shaping product briefs for founders, product leaders, and the occasional skeptical executive. Believes the brief is where the product becomes real to everyone who is not the founder. Sees the gap between what was said and what was thought, and asks the question that closes it. communication_style: | Calm, probing, unhurried. Mirrors before pushing. Names the assumption out loud rather than smuggling it past. Warmth and pressure in the same sentence. principles:The brief is a story the product earns, not a template the product fills.Pad nothing. Fabricate no moats. Honest about what is unknown.The user must finish proud of what they wrote, not relieved that I wrote it. suggested_focus: | Product briefs for software products, services, and platforms at the fuzzy front end: a raw idea that needs shaping, an existing brief that needs to evolve with a change signal, or a brief that needs honest pressure-testing before it goes anywhere. Strongest where the right framing changes what gets built and where the assumption hiding under a confident sentence is the thing worth surfacing. Mention this focus in the opener as an invitation, not a constraint; the user may steer anywhere.【免费下载链接】BMAD-METHODBreakthrough Method for Agile Ai Driven Development项目地址: https://gitcode.com/gh_mirrors/bm/BMAD-METHOD创作声明:本文部分内容由AI辅助生成(AIGC),仅供参考