01 / The familiar format
You could share this as a wiki page.
A fictional wiki entry with the same underlying facts. Read it here, then compare how the HTML version presents the information.
Team wiki · Fictional example
Alder Reports — proposed priority for this cycle
Goal and capacity
Prepared September 7, 2026, by Rowan for Priya. Goal: make report labels easier to understand. Priya allows capacity for one small improvement this cycle; no end date, approved choice or schedule is supplied.
Candidates
A: revise the glossary, estimated by Rowan at two editor days. Twelve selected support notes mention confusing labels, but they are not representative or a unique-customer count. No revision result is measured. B: custom report labels, estimated by the delivery team at five developer days. Developer availability is unknown, and consistent meanings require a settled glossary first. C: color refresh, estimated at one designer day, with no supplied evidence connecting color to label understanding.
Proposed order
Rowan proposes glossary first, custom labels after definitions and developer availability are settled, and deferring the color refresh for lack of problem evidence. Priya must decide; this proposal reserves no staff and authorizes no work. Effort across roles is not interchangeable, and no numerical weights or scores are agreed.
Revisit conditions
Revisit if evidence or capacity changes. Actual priorities and dates belong in the existing planning board; this snapshot does not update it.
02 / The HTML version
Same information. See what needs your attention.
This is the complete static HTML example, not a screenshot. Scroll inside the preview to read it all. It has no live data, scripts, forms, or external resources.
Inspect the complete HTML source
This is the authored source for the example. The preview above passes through our HTML sanitizer before rendering in an isolated frame.
<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1"><title>Alder Reports · Priority proposal</title><style>
*{box-sizing:border-box}html{color-scheme:light}body{margin:0;background:#f5f8fc;color:#182e46;font:17px/1.65 system-ui,sans-serif}main{max-width:1000px;margin:auto;padding:clamp(20px,5vw,64px)}h1,h2,h3,p{margin:0 0 18px}h1{font:500 clamp(32px,5vw,58px)/1.14 Georgia,serif;letter-spacing:-.025em;overflow-wrap:anywhere}h2{font:500 29px/1.3 Georgia,serif;overflow-wrap:anywhere}h3{font-size:19px;line-height:1.4}.label{font:700 12px/1.6 system-ui,sans-serif;letter-spacing:.08em;text-transform:uppercase}.intro{font-size:20px}.lead{background:#23486b;color:white;padding:24px;margin:28px 0}.lead p:last-child{margin:0}.grid{display:grid;grid-template-columns:repeat(auto-fit,minmax(min(100%,230px),1fr));gap:20px;margin:24px 0}.card{background:white;border:1px solid #bbc5c4;padding:24px}.metric{font:500 38px/1.2 Georgia,serif;display:block;margin-bottom:12px}section{margin:36px 0}ul,ol{padding-left:22px}li{margin-bottom:12px}.note{font-size:14px}.warning{border-left:5px solid #956118;padding-left:20px}a{color:inherit;text-underline-offset:4px}a:focus-visible,summary:focus-visible{outline:3px solid #956118;outline-offset:4px}table{width:100%;border-collapse:collapse;table-layout:fixed;font-size:15px}th,td{text-align:left;vertical-align:top;border-bottom:1px solid #bbc5c4;padding:12px 8px;overflow-wrap:anywhere}caption{text-align:left;font-weight:700;padding:12px 0}pre,code{white-space:pre-wrap;overflow-wrap:anywhere}footer{border-top:1px solid #bbc5c4;padding-top:24px;margin-top:40px;font-size:14px}@media(max-width:480px){th,td{padding:10px 4px;font-size:14px}}@media print{body{background:white}.card,.lead{break-inside:avoid}h2,h3{break-after:avoid}}
</style></head><body><main><header><p class="label">Alder Reports / September 7, 2026 / Fictional planning brief</p><h1>Fix the meanings before adding more labels.</h1><p class="intro">One small improvement fits this cycle. Rowan proposes the glossary revision; Priya still needs to decide.</p></header><aside class="lead"><h2>Proposed first: the glossary.</h2><p>Two editor days estimated. Twelve selected support notes mention confusing labels. No choice is approved or scheduled.</p></aside><section><h2>Three candidates, different reasons to wait</h2><div class="grid"><article class="card"><h3>Glossary revision</h3><p>Directly addresses the supplied label-confusion evidence. A beneficial result has not yet been measured.</p></article><article class="card"><h3>Custom labels</h3><p>Five developer days estimated. Needs a settled glossary first; developer availability is unknown. Defer until both are resolved.</p></article><article class="card"><h3>Color refresh</h3><p>One designer day estimated. No supplied evidence connects it to label understanding. Proposed deferral.</p></article></div></section><section class="warning"><h2>What the evidence does not tell us</h2><p>Twelve notes are not a representative sample or a count of unique affected customers. The estimates use different roles and cannot be treated as interchangeable capacity. No scoring weights are agreed.</p></section><section><h2>The decision belongs in planning</h2><p>Priya must approve the priority through the existing planning board. This proposal reserves no staff and gives no delivery date. Revisit if new problem evidence or changed capacity is supplied.</p></section><footer>Fictional worked example by share/artifacts. Names, dates, figures and records are invented for demonstration. Static snapshot; no live data or automatic updates.</footer></main></body></html>
Make the next one about your work.
- Take the task to your agent. We provide a request with the goal, example, and checks. Copy it into the conversation where your context lives.
- Supply only what is missing. Use material your agent is authorized to access. Don’t substitute the example’s invented facts for your own.
- Review a draft before sharing. Check facts, readability, and sensitive information. Publishing and choosing who can open it are separate, explicit decisions.
Make this with my agentNo publishing connection is needed for an initial local draft. Your agent needs to be able to create an HTML file; preview and connection support vary by client.