Yesterday recap
프롬프트 세부 정보
Recap yesterday's content in a clear, structured format, and provide some follow-up suggestions.
Focus on key items, and list or group less important ones briefly.
프롬프트의 기능
Every new morning brings a mental gap. Yesterday's progress, decisions, and loose ends blur overnight, and you lose precious time trying to piece things back together before you can move forward.
This prompt gives you a clean, structured recap of the previous day's content — highlighting key items up front and grouping smaller details so nothing gets buried. It also suggests logical next steps, so you start each morning with full context and clear direction instead of scrambling to rebuild momentum from scratch.
사용 시점
• Starting your workday and need a quick catch-up on everything you missed or couldn't fully process yesterday.
• Returning from a day off or PTO and want a structured overview instead of scrolling through hundreds of notifications.
• Preparing for a morning standup or daily sync where you need to report on yesterday's progress and blockers.
• Managing cross-functional projects where updates come from multiple channels, emails, and meetings simultaneously.
• Wrapping up a busy week and needing to verify nothing from the previous day slipped through the cracks.
프롬프트 예시
Input: Recap yesterday's content in a clear, structured format, and provide some follow-up suggestions. Focus on key items, and list or group less important ones briefly.
remio responds:
Key Items from Yesterday (Oct 15):
1. Product Launch Timeline — Sarah shared an updated launch date of Nov 3 in #product-releases. The QA team flagged two blocking bugs in the same thread that need resolution by Oct 18.
2. Client Escalation (Acme Corp) — David sent an email requesting urgent support for a billing discrepancy. No response has been sent yet.
3. Design Review Meeting — The team approved the new onboarding flow mockups but requested mobile viewport adjustments before handoff to engineering.
Lower-Priority Updates: HR posted open enrollment reminders; IT scheduled server maintenance for Oct 20; three Slack channels had casual team discussions with no action items.
Suggested Follow-Ups:
- Reply to David's Acme Corp email and loop in billing support.
- Check in with QA on bug resolution progress.
- Confirm design handoff timeline with the engineering lead.
Tip 1: If your days are packed, narrow the recap by adding context like "focus on messages in #engineering and emails from clients" to filter out noise and surface only what's relevant to your role.
Tip 2: Run this prompt first thing every morning as a ritual — it works best when yesterday's context is fresh and you can immediately act on the follow-up suggestions.
Tip 3: Add "flag anything that seems unresolved or awaiting my response" to ensure your recap highlights items where you're the bottleneck.
더 많은 팁
remio로 지식에 관한 모든 요구를 해결하세요
더 많은 기능 알아보기
웹사이트, 로컬 폴더 & 파일에서 자료를 가져오세요.
전체 지식 베이스에서 신뢰할 수 있는 답변을 즉시 얻으세요.
개인 경험을 반영한
편집 가능한 네이티브 PPTX를 만드세요.
봇 없이 녹음과 전사를 무료로 무제한 이용하세요.