Use this prompt recipe for meeting agenda for a weekly review. It gives the AI a clear job, visible source inputs and a review step so the result can be edited instead of blindly copied.
| Best for | operators, project managers, founders, assistants and team leads |
|---|---|
| Search intent | Readers usually need a prompt that converts scattered work notes into decisions, owners, risks and next actions. |
| Expected output | Clean summary, Owner and deadline table, Risks and open questions, Follow-up message |
When this recipe is useful
Use this recipe when the task is specific enough to benefit from AI structure but still needs human judgment. In the situation "for a weekly review", the prompt should make the audience, source material and quality bar explicit before asking for a finished answer.
The goal is not to make a generic meeting agenda. The goal is to create a draft that reflects the real context, avoids unsupported claims and gives the reviewer a clear path for improving the result.
Source inputs to prepare
| Work context | Add the real detail for meeting agenda for a weekly review. If this detail is unknown, ask the AI to return a missing-information question. |
|---|---|
| Goal or decision | Add the real detail for meeting agenda for a weekly review. If this detail is unknown, ask the AI to return a missing-information question. |
| Known owners | Add the real detail for meeting agenda for a weekly review. If this detail is unknown, ask the AI to return a missing-information question. |
| Timeline constraints | Add the real detail for meeting agenda for a weekly review. If this detail is unknown, ask the AI to return a missing-information question. |
| Risks or blockers | Add the real detail for meeting agenda for a weekly review. If this detail is unknown, ask the AI to return a missing-information question. |
Copy-ready prompt
Recommended output structure
- Clean summary: Make this section specific to meeting agenda for a weekly review and easy for a human reviewer to check.
- Owner and deadline table: Make this section specific to meeting agenda for a weekly review and easy for a human reviewer to check.
- Risks and open questions: Make this section specific to meeting agenda for a weekly review and easy for a human reviewer to check.
- Follow-up message: Make this section specific to meeting agenda for a weekly review and easy for a human reviewer to check.
Review checklist
- Owners and dates are marked missing if not provided.
- The output separates decisions from discussion.
- Risks and blockers are not buried.
- The final format can be copied into a team tool.
Common mistakes
- Inventing owners or deadlines.
- Mixing discussion with decisions.
- Skipping risks because they are uncomfortable.
- Creating a plan that ignores resource limits.
How to adapt it
If the first output feels too broad, add one concrete example of the audience, one example of the tone you want, and one example of a claim the AI must avoid. This usually improves the next answer more than adding more adjectives.
If the output is too long, ask the AI to keep the structure but shorten each section around the decision the reader needs to make. If the output is too shallow, add source notes and ask for missing questions before another draft.
FAQ
When should I use this prompt?
Use it when you need meeting agenda for a weekly review and want the AI output to stay tied to your real source inputs, audience and review rules.
What should I prepare first?
Prepare the practical inputs: Work context, Goal or decision, Known owners, Timeline constraints. If one of those is missing, keep it marked as unknown instead of asking the AI to guess.
Can I publish the output directly?
Treat the output as a draft. Check facts, claims, names, dates, policies and promises before using it in public or customer-facing work.