◆ HTML

Create a weekly schedule in HTML

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskCreate a web page for the team's weekly schedule. It needs to list everyone's tasks, deadlines,…+
Create a web page for the team's weekly schedule. It needs to list everyone's tasks, deadlines, and who's on call for support this week. Use the draft in the shared document.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I publish this week's web schedule, make it easier for Sarah and the remote team to…+
Before I publish this week's web schedule, make it easier for Sarah and the remote team to read. Highlight urgent tasks, make sure the on-call person is clearly visible, and ensure it looks good on a small laptop screen. The last one was a mess on her device.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI've included everyone's tasks in the web schedule for this week, but I'm unsure how to…+
I've included everyone's tasks in the HTML schedule, but I'm unsure how to visually group them effectively for different teams.
I've included everyone's tasks in the web schedule for this week, but I'm unsure how to visually group them effectively for different teams – engineering, design, and content. I'm worried if it's just a long list, people will miss their specific items, and we'll have another missed deadline. What's the best structure to make it clear and scannable for each group?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternMy web schedules often become outdated quickly, leading to confusion about who is doing what…+
My HTML schedules often become outdated quickly, leading to confusion.
My web schedules often become outdated quickly, leading to confusion about who is doing what and when. I spend too much time manually updating them, and by mid-week, they're usually ignored. What habit should I change to make these web schedules more dynamic and less of a static snapshot, so they remain a valuable, living resource for the team?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from HTML's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.