🌸 万物焕新春季特惠 年度计划立减 30% 🌸 优惠码：SPRING2026
草案发布说明
Prompt detail
您是一位高级产品经理。请根据 {{@resource}} 中提供的文档，生成专业的发布说明。
● 首先，分析 {{@resource}} 中以往发布说明的写作风格和结构，以保持一致性。
● 然后，总结 {{Start_Date}} 和 {{End_Date}} 之间发生的产品更新。
● 如果没有提供日期范围，请将 {{@resource}} 的最新版本与之前的版本进行比较，以记录变更。
● 确保发布说明清晰、简洁且易于理解。
● 仅包含已完成和计划发布的更新。请勿 提及无关产品或未来的产品路线图项目。
输出格式建议：
● 新功能
● 改进
● 问题修复
What the prompt does
Writing release notes means combing through PRDs, project trackers, and status reports to identify what shipped, what improved, and what got fixed. It's tedious and error-prone, especially when updates span multiple documents and teams.
With remio, you select your source documents — PRDs, project reports, sprint summaries — and specify a date range. remio analyzes the content, matches the tone and structure of your previous release notes, and outputs a clean draft organized into New Features, Improvements, and Bug Fixes. Only completed, release-ready updates make the cut.
When to use
• You're preparing release notes for an upcoming product launch and need to consolidate updates from multiple PRDs and sprint reports into one cohesive document.
• Your team ships biweekly and you need to quickly compare the latest project documents against the previous cycle to capture what changed.
• Stakeholders are asking for a customer-facing changelog and you need to translate internal technical documents into user-friendly language.
• You're onboarding as a new PM and need to reconstruct release history from existing project documentation.
• End-of-quarter review requires a summary of all shipped features across several workstreams.
Prompt examples
Input: Resource: Q2 Mobile App PRD v3.2, Sprint Reports May 1–May 31; Start Date: May 1, 2025; End Date: May 31, 2025
remio responds:
Release Notes — Mobile App v3.2 (May 2025)
New Features
• Biometric login: Users can now authenticate using Face ID and fingerprint on supported devices.
• Offline mode for saved documents: Previously saved files are accessible without an internet connection.
Improvements
• Reduced dashboard load time by 40% through optimized API calls documented in Sprint 9 report.
• Updated onboarding flow copy to align with new brand guidelines referenced in the PRD.
Bug Fixes
• Resolved crash on iOS 17 when switching between tabs during file upload.
• Fixed notification badge count not resetting after messages were read.
These notes follow the structure and tone established in your previous v3.1 release notes.
Tip 1:
Always include your previous release notes as one of the selected resources — remio will match the tone, structure, and level of detail so your changelog stays consistent across versions.
Tip 2:
Specify the exact date range rather than relying on version comparison. This ensures remio captures updates from sprint reports and status docs that may not be versioned.
Tip 3:
Tag both technical docs and user-facing docs as resources to help remio distinguish internal changes from customer-relevant updates.
More tips
remio满足您对知识的所有需求
了解更多功能
从网站、本地文件夹和文件中获取资源。
从您的整个知识库中获取即时、可靠的答案。
您的工作助手，可在台式机、浏览器和移动设备上使用。
无限次免费录音和转录，非机器人操作。