by Corepass

Use Remy

Turn meeting notes into actions

Separate decisions, actions, and open questions.

Scope: Work with written notes in the desktop app.

Organize existing meeting notes into decisions, action items, and open questions so participants know what needs to happen next. This example works with written records. It does not transcribe audio, send messages, or create tickets in other systems.

1. Provide the meeting context

Paste the notes into a chat and include the meeting date, topic, and intended readers. You can also save the written notes in your local project and give Remy the file path to read.

Expressions such as “tomorrow” or “Friday” depend on the meeting date. Keep dates unconfirmed when they cannot be resolved. Do not let Remy assign an owner simply because a person mentioned an issue.

2. Try a complete example

The following meeting record is fictional. You can send the whole prompt:

Example prompt
Organize these meeting notes for the participants to confirm.

Meeting date: October 9, 2026.
Topic: Preparing for the first user trial.

Original notes:
- We agreed to onboard five partner companies first.
- Alice will prepare the user guide by October 12.
- Ben owns the installation-flow checks, but no deadline was set in the meeting.
- Someone suggested making a demo video. We have not decided whether to make it, and no owner was assigned.
- The support email address is not yet settled and needs confirmation.
- The trial start date is not settled. We will discuss it after the installation checks are complete.

Provide:
1. Confirmed decisions.
2. An action table with the item, owner, deadline, and completion criteria.
3. Questions that still need a decision or confirmation.

Use only the owners, dates, and commitments in the original notes.
Mark missing information “To be confirmed.” If you suggest completion criteria, explicitly label them as suggestions.
Do not turn an idea raised in discussion into an agreed task.

3. Review the result

Check that the result preserves these distinctions:

Original information How to represent it
Invite five partner companies first A confirmed decision
Alice's user guide is due by October 12 An action with a named owner and deadline
Ben owns installation checks, with no date A confirmed owner and a deadline to be confirmed
A demo video was suggested but not agreed An open decision, without automatically assigning work
The support email is unsettled An open question, without inventing an address or owner
The trial date is unsettled Do not infer a launch date from another task's deadline

For real meeting records, pay particular attention to names, dates, numbers, commitments, and unresolved questions.

4. Apply confirmed changes

For example, once a participant confirms the installation-check deadline, continue with:

Example prompt
Confirmed update: Ben's installation checks are due on October 13.
The demo video is still undecided, and the trial start date is still unconfirmed.

Update only the affected action item. Preserve the other decisions and open questions.

Changes to ownership or commitments should be confirmed by the relevant people before being added to the record.

5. Save the meeting record

After checking the content, select a project that includes the destination folder and ask Remy to save the record:

Example prompt
Save the checked meeting record to docs/meetings/2026-10-09-trial-preparation.md.
Keep the meeting context, confirmed decisions, actions, and open questions.
If the file already exists, explain that first and wait for me to decide whether to replace it.

Open the file and confirm that it reflects the final decisions before sharing it through your team's usual process. Creating the record does not automatically notify the owners or create tasks in another system.

6. Keep exploring