A BETTER WAY TO SHARE THE WORK
Help people arrive ready for the discussion
Use the page to establish common ground—not to decide before people arrive.
New to creating with an agent? The request will guide it through the task. Bring your notes; you don’t need to write HTML.
What should go in a workshop pre-read?
Lead with the question the workshop needs to explore, then provide only the evidence and preparation participants need. Your agent can organize authorized notes into a short HTML pre-read that separates facts, proposals and open choices. Keep the actual discussion and decision record in their established workflows.
01 / SEE THE DIFFERENCE
Choose what to learn before choosing a pilot
Fictional help-center workshop; no option has been approved.
The workshop will recommend which help-center pilot to explore, not authorize publishing. Six selected support notes mention navigation confusion. Three selected notes mention outdated examples; counts are not prevalence. Options: test a topic index or revise two examples. Effort estimates are missing. Ask participants to bring one unanswered question and one constraint from their role. Facilitator Sam proposes reviewing evidence, comparing options and recording gaps. Lee decides later in the project workflow.
- Purpose
- Recommend a help-center pilot to explore; do not authorize publishing.
- Evidence
- Six selected navigation notes and three outdated-example notes; neither count measures prevalence.
- Choices
- Test a topic index or revise two examples. Effort estimates are missing.
- Prepare
- Bring one unanswered question and one role-specific constraint. Sam facilitates; Lee decides later in the project workflow.
Open a complete fictional HTML example, with its source notes →
Create my workshop pre-read02 / MAKE IT YOURSELF
Start with the evidence. Shape the page around the reader.
State the question participants will work on
A workshop to explore options is different from a meeting authorized to choose one. Say which it is. Keep a missing decision owner or uncertain mandate visible instead of writing an agenda that assumes approval.
Give everyone the same essential evidence
Select the few facts needed for the discussion and show their limits. Separate supplied observations from interpretations. Keep deeper optional reading below the essentials so preparation is not a demand to reconstruct the whole project.
Ask for useful preparation
Request a concrete contribution such as one question or a constraint from the participant's role. Do not quietly turn preparation into a vote or a commitment. Include supplied reading-time guidance only if it is realistic and verified, not an invented promise.
Make the live session easier to start
Create static HTML with the question, background, options and preparation task. Review access and logistics. Record discussion outputs after the session separately; the pre-read remains context, not evidence that everyone agreed.
03 / TRY THIS PROMPT
Copy this into your agent. Add your source material.
Use the conversation where you already did the work, or start one with your notes. Replace the placeholders and supply any missing context; only attach information you are allowed to share with your agent.
Get the ready-to-copy creation request for guided questions, this task, and a draft review before anything is published.
Create a workshop pre-read from my authorized purpose, evidence, open options and preparation requirements. Ask for missing essentials. State whether the session explores, recommends or decides. Separate facts, interpretations and proposals; do not invent agreement, votes, effort estimates, logistics or decision authority. Lead with the discussion question and one concrete preparation task. Keep optional background separate. Use static HTML with no scripts or forms and my saved style if available. The page does not collect responses or attendance. Show the draft and unresolved questions; keep decisions in the existing workflow. Do not publish or change access without separate explicit approval.
04 / BEFORE YOU SEND
A polished page still needs your judgment.
- Is the session's actual authority clear?
- Is essential reading separate from optional background?
- Can participants identify the specific preparation task?
- Are open options and missing evidence still visibly open?
When HTML fits
A short shared context page people can read before or at the start of a discussion.
When another format fits better
Use meeting, collaboration or polling tools for live participation. The page does not capture attendance, votes or approval, and is not the post-meeting decision record.
FROM DRAFT TO A LINK
Make it clear. Make it yours. Then share it.
Keep creating and revising in the agent you already use. With a compatible connection, share/artifacts publishes the reviewed HTML so you do not have to rebuild it in another editor. Ask your agent to use your saved artifact style for headings, color, and tone; review the result before sending it.
Choose who should be able to open the page and verify the returned link. For corrections to the same deliverable, update the existing artifact without changing its link. Publish a separate artifact when the old edition needs to remain available.
These are static pages, not live apps: no scripts, forms, or automatic data refresh. Source collection and scheduling depend on your agent and its available tools, not on share/artifacts.
Make this with my agentQuestions before you start
Should the pre-read contain a recommendation?
It can, if that is part of the supplied context. Label it as a recommendation and give alternatives and material limits room to be considered.
What if participants do not read beforehand?
Plan reading time in the session if the facilitator chooses that approach. Do not claim the page verifies reading or attendance.
Can I use it as the final decision record?
Create a separately reviewed record from the actual discussion. A pre-read cannot establish what participants later agreed.