Plan your week in time blocks

Start with this exact skill.

In a connected assistant, copy this public starter. Add your own facts in the conversation after retrieval. This starter contains no personal task inputs.

Use LazyCoder get_skill to retrieve "time-blocked-week" at version "recipe-8b57825b22b4309576061b2e". Confirm release "publication-2cc5f3d871330e560bedbc0a" before using it; if unavailable, ask me to refresh the skill page. Follow its execution.conversation guide, instructions and output contract. Ask only missing questions in chat, at most three at a time, and wait for my answers before producing the result. Skip facts already provided; do not invent them. Keep my task details and result in this chat; do checks here, never with hosted validate_inputs or check_output.

Copy the starter, open Claude, and paste it into a chat with LazyCoder enabled. Opening Claude does not send your request or confirm a connection.

Prefer to prepare a filled prompt first? Customize the same skill. Connection trouble? Recover while keeping this skill selected.

From example to your own result

1. Keep the structure. Use the required sections and checks below as a starting point.
2. Replace the example facts. Bring Your to-dos, Week starting and time zone. Missing facts should remain questions, not invented details.
3. Review before use. Inspect the final document or file in the intended app. An illustration proves the preview renderer, not the assistant’s output quality.

What to check in your result

• Your fixed commitments stay exactly where they are
• Hours wanted are checked against hours free, and anything that didn't fit is named, with where it went
• Sleep, meals and breaks are kept, with gaps between blocks
• Your hardest work sits in your best hours
• A daily flex slot, a weekly review, and a rule for when a day goes wrong
• A calendar file to import, or calendar text to save as one where your app can't make files

Structural checks do not establish factual accuracy or usefulness. How we review.