# Set up the project meeting workflow

Set this up with the initial project home. The user should be able to open an
agenda and run the next conversation, not receive a suggestion to add notes later.

## Choose a useful starting point

Use the team's known cadence. For a weekly project sync, prepare a decision- and
risk-focused agenda. For standups, keep it short and centered on changed work and
blockers. If cadence is unknown, prepare a **proposed weekly project sync** agenda
with date and participants unset; tune it after sharing the initial home. Do not
create both rituals by default, invent past meetings, or populate a calendar with
speculative sessions. Respect an explicitly asynchronous or solo workflow.

Use the current tool schemas and the connection's dedicated meeting-note tool
when available for actual meeting notes. A reusable agenda template is not a
meeting that has happened. If the tool requires an agreed date or attendees,
create a clearly labeled ordinary agenda draft instead of inventing those values.

## Prepare the agenda from actual project context

For a weekly sync, include:

- **Purpose and pre-read:** the decision or alignment needed, with working links
  to the project brief and relevant specs.
- **Progress since the last sync:** link the current task view. For the first
  meeting, use known current state; do not invent changes since a nonexistent
  previous meeting.
- **Decisions and risks:** seed discussion topics from unresolved decisions and
  blocked work. Separate a question to decide from an accepted decision.
- **Notes and outcomes:** provide compact capture prompts for decisions,
  rationale, and unresolved questions. Leave outcomes blank until supplied.
- **Actions:** link the canonical task tracker. Capture agreed action, owner,
  and date when known; do not maintain a competing checklist of the same work.

For a standup, use progress, next focus, blockers/help needed, and follow-ups.
Seed real blockers and task links, but do not fabricate individual updates or
assign each collaborator work. Detailed discussions can link to a follow-up doc.

## Make the next meeting easy

Create a native reusable database template with a clean agenda and project
links, then prepare the first agenda from it. Keep the reusable template separate
from that meeting's notes and outcomes.

Make the notes area visible on the home through a compact list or table with
meeting title, date, and status. Keep the undated prepared agenda visible and
sort dated notes newest first. Filter shared notes by the actual project
relation. Separate reusable agendas from held meetings so templates do not appear
as meeting history. Keep the main Docs view focused on specifications and reference
material when meeting notes share that database.

A future note should link back to its project; resulting tasks and decision docs
should link to the originating note. When moving the initial home into a Projects
database, reconcile its notes and agenda too, preserving links and avoiding copies.

Setting up notes does not schedule calendar events, send invitations, enable
recording, or configure recurring automation. Only do those with an explicit
request. Report the prepared agenda and notes workflow as ready; describe cadence
as proposed until confirmed and never claim a recurring meeting is scheduled.
