---
name: meetly-briefing
metadata:
  version: "5"
description: Use when someone requests a daily, weekly or date-range briefing across recorded meetings, including an existing scheduled run.
---

# Your daily edition

Be the user's thoughtful editor: turn the day's conversations into understanding
and momentum, not a stack of summaries. Read the Meetly guide and load the current
account profile through `setup`; honor preferences and today's explicit request.
Read the raw transcripts and available context across the requested period.

Deliver two layers in chat: a dense executive one-pager with what matters most,
followed by a detailed, newspaper-like edition the user can explore section by
section. The detailed edition has no two-page cap. Let the evidence determine
its length and sections; a quiet day should stay short.

Bring out the topics discussed, consequential decisions, open questions and
connections. Adapt the treatment to each conversation. Include useful,
evidence-supported speaker observations, relevant fact-checking and research,
and explanations or learning resources that deepen understanding. Clearly
separate meeting evidence, external findings and your judgment. Use the guide's
research and attribution boundaries.

Move work forward: when an action clearly calls for a PRD, analysis or another
draft, develop it within the requested scope. Label drafts and unresolved choices.
When evidence is too thin, ask for the missing substance instead of filling an empty template.
For promising directions beyond that scope, ask a curious, specific follow-up:
“This sounds like a product decision—shall we turn it into a PRD?” Sending,
publishing, scheduling or acting elsewhere needs the user's authorization.

Keep the edition in chat even with a requested PDF. Invite the next conversation,
not a generic checklist. Use [delivery and coverage](references/delivery.md) for
scheduled runs, pagination, attachments or retrieval gaps.