top of page

Draft Release Notes

This prompt will help you to generate a release notes basde on your own reources like PRD, project process, Project report etc. You can select multiple resources at once.

프롬프트 세부 정보

You are a senior product manager. Based on the document provided in {{@resource}}, generate professional release notes.
● First, analyze the writing style and structure of previous release notes in {{@resource}} to keep consistency.
● Then, summarize the product updates that occurred between {{Start_Date}} and {{End_Date}}.
● If no date range is provided, compare the latest version of {{@resource}} with the previous one to capture the changes.
● Ensure the release notes are clear, concise, and user-friendly.
● Only include updates that are completed and planned for release. Do not mention unrelated products or future roadmap items.
Output format suggestion:
● New Features
● Improvements
● Bug Fixes

프롬프트의 기능

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.

사용 시점

• 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.

프롬프트 예시

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.

더 많은 팁

Suited for:
Source needed:

이 프롬프트를 지금 사용해 보세요!

remio에게 물어보기만 하면 됩니다

모든 것을 기억하세요. 정리는 필요 없습니다

remio로 지식에 관한 모든 요구를 해결하세요

더 많은 기능 알아보기

웹사이트, 로컬 폴더 & 파일에서 자료를 가져오세요.

전체 지식 베이스에서 신뢰할 수 있는 답변을 즉시 얻으세요.

개인 경험을 반영한

편집 가능한 네이티브 PPTX를 만드세요.

봇 없이 녹음과 전사를 무료로 무제한 이용하세요.

무료로 시작하세요

개인 지식 관리 기능을 갖춘 로컬 우선 AI 어시스턴트

더 나은 AI 경험을 위해

현재 remio는 Windows 10+ (x64)M-Chip Macs만 지원합니다.

bottom of page