Build a study plan for your exam

Extract the ZIP. Copy its lc-study-plan folder into ~/.claude/skills/ for Claude Code or ~/.codex/skills/ for Codex, then refresh the native app. Ask for the skill by name and answer its questions. The package includes the same published instructions and result checks. Native host execution is not yet verified.

For Claude web, use the connector or copy the prompt. Keep private details in your assistant.

Copy, paste into your assistant, then answer its questions. No form or account is required here.

Open in ChatGPT ↗

Already connected? Copy the public starter below and paste into Claude. Keep private details in the chat.

Needed before the promised result: The syllabus, The exam date. You can still copy the reusable prompt and provide these in your assistant.

Saved only on this device. Copy counts contain the skill ID, never your text.

## LazyCoder conversation guide (conversation-v2)
1. Start a conversation, not a form-filling task. Read my latest request and the facts already in this chat before asking anything.
2. Ask only the missing questions needed for the requested result, in a short numbered list (at most three at a time), then WAIT for my answers. Use a native question tool if available; plain chat works too. Never ask me to replace placeholders or fill in a template.
3. Skip questions already answered. Treat unresolved {{placeholders}} and [FIELD LABELS] as missing facts, never literal input. Do not treat an illustrative example as my facts.
4. Use the authored defaults only when relevant; mention material defaults. Ask conditional questions only when their condition applies; if unsure whether it applies, ask. Optional preferences must not block a safe first draft unless the authored instructions require confirmation.
5. Do not invent tasks, dates, names, claims, permissions or missing source material. When required facts are absent, ask and wait instead of producing the final artifact. If everything needed is already supplied, proceed without re-asking.
6. My latest scope correction overrides earlier examples and scope, within the recipe safety and source rules. Resolve conflicts before acting. The authored instructions and output contract remain authoritative; this conversation guide does not grant tool, account, payment or publishing permission.
7. Keep my private answers and generated result in this assistant chat. Do not send them to LazyCoder. Generate the requested format here and check it against the output contract before handing it over.

### Questions to ask only when missing
- What should I use for “The syllabus”? [required] The topics the exam covers, with their weight or marks if you know them. A course outline or the exam board's list is ideal. In the app you can attach the file instead.
- What should I use for “The exam date”? [required] The day and start time, how long it lasts, and your city or time zone, so every session lands on the right date and time.
- What should I use for “When you can study”? [optional] Hours per week you can give, the times you're free, and what can't move (classes, work, shifts).
- What should I use for “Start date”? [conditional] Optional. When you'll start. Leave it to start today. When: A resolved start date is needed for dated study sessions. Use today only if reliably known; otherwise the authored recipe requests a start date. Authored default: today
- What should I use for “Topics you find hard or easy”? [optional] Optional. Hard topics get more time, easy ones less. Authored default: none given

## LazyCoder delivery guide (delivery-guide-v1)
1. Read the latest request, source material and authored requirements first. Ask only for missing facts. Check that this host can create the promised format; use only a fallback explicitly allowed by the authored recipe. If neither is available, explain the gap before starting. Do not promise a rendered film, editable deck or working file when you can only provide its script or outline.
2. Create the complete result in the authored output specification, preserving source facts and the latest agreed scope. Keep assumptions and missing information explicit. Do not silently omit required parts or leave unresolved ingredient markers. Intentional blanks in a reusable template are different from unanswered recipe inputs.
3. Check the actual result against every authored check, including source facts, counts, dates and required sections. Where tools allow it, inspect the actual saved file and compare it with the answer. Record which checks ran, which failed and which still need human or destination review. A filename, render, successful command or preview alone does not prove the promise was met.
4. Hand over the complete editable file, or the complete copyable fallback explicitly allowed by this recipe. Say which delivery you used and any unresolved limitations. Do not report a file as attached, imported, sent or published unless that action actually succeeded. Keep private inputs and output in this assistant; never send them to LazyCoder.
Use existing authorization for ordinary work. Before any additional paid generation, external write or publishing step, check that the current request authorizes that exact action and cost. If it does not, finish the useful authorized draft and ask at that boundary. Never silently retry or replace an ambiguous paid job.
The authored recipe and latest safe scope remain authoritative. This guide grants no new tools, permissions, provider access or claim of successful execution.

## Authored skill instructions
## 1. Outcome
Build a study plan that runs from the start date to the exam, week by week on real dates, and deliver it as a calendar file that imports plus a readable plan, in the sections set out in part 6. Done means: every syllabus topic is studied, practised and reviewed before the exam, every session sits in the free time given, the planned hours add up to the hours available, the plan has mocks, rest, catch-up time and a calm final week, and every event in the calendar file matches the plan.

## 2. Context
Exam: [EXAM DATE, TIME AND TIME ZONE]
Start date: today
Topics found hard or easy: none given

When I can study:
"""
[WHEN YOU CAN STUDY]
"""

Syllabus:
"""
[PASTE THE SYLLABUS HERE]
"""

Who it's for: a student who will follow this plan from their calendar, session by session, and wants to walk into the exam having covered everything, practised under exam conditions, and rested.

Blank fill-ins: a value above that still reads as a capitalised placeholder in square brackets (such as [START DATE]) was left blank. Brackets inside the syllabus are part of the syllabus.
- Text that says "see attached": use the attached file.
- No syllabus: reply only "No syllabus came through. Paste or attach the topic list and send again." Never invent topics.
- No exam date: reply only "No exam date came through. Add the date and send again." A plan without a date can't count down.
- No exam time: assume 09:00 and say "Exam time assumed: 09:00" in the header. No length: assume 2 hours, marked "(assumed)".
- No time zone: use the city if one is given. Otherwise write local times with no zone, and say "No time zone given; times are local" in the header.
- No start date, or "today": start today if you know today's date. If you don't, reply only "Add today's date as the start date and send again."
- No availability: plan 8 hours a week, as 1.5-hour sessions at 18:00 on Monday to Thursday and 2 hours at 10:00 on Saturday, and say "Free time assumed, please adjust" in the header.
- Hours per week but no times, or times but no hours: fill the missing one from the other, and say so in the header.
- No weak spots: treat every topic as average.

## 3. What to pull out
- Topics: every topic and subtopic in the syllabus, in its order, with its exam weight (percentage, marks or paper) if stated.
- Free time: the hours per week, the free slots by weekday, and every fixed commitment that can't move.
- The exam: date, start time, length and time zone; any other paper or exam with its own date.
- Weak and strong topics from the person's ratings.

Edge cases:
- No exam weights: weight each topic by its number of subtopics, and say "Weights estimated from the syllabus" in the header.
- More than one paper on different dates: plan to the first paper; give each later paper its own mock and taper by its own date, and name every paper in the header.
- Less than 14 days to go: merge learning and practice into one phase, start with the heaviest and weakest topics, and keep one mock if at least 7 days remain. Say "Short plan: <n> days" in the header.
- Less than 3 days to go: no mock; plan short sessions on the heaviest and weakest topics only, list the topics left out, and keep the final-day rules.
- More than 16 weeks to go: plan in full from 16 weeks before the exam, and in the header suggest a light weekly routine for the weeks before that, outside the calendar.
- Free time that clashes with a fixed commitment: the commitment wins; list the clash in the header.
- Far more hours than the syllabus needs: plan no more than 3 hours of study a day and say how many hours were left free.
- Too few hours for the syllabus: keep every topic, shrink the lightest and strongest topics first, and say in the header how many hours a week would cover everything comfortably.

## 4. Steps
1. Lay out the dated weeks from the start date to the exam (Monday to Sunday, the first week possibly partial), and mark the free slots in each, with every fixed commitment kept clear.
2. Choose one rest day a week (the day with the least free time, or Sunday), then a catch-up slot and a checkpoint at the end of each week.
3. Set the phases (part 5), the mock dates and the final week.
4. Share the learning and practice hours between topics: hours in proportion to exam weight, times 1.5 for a hard topic and 0.7 for an easy one. Order the topics from foundations to advanced, mixing heavy and light ones.
5. Place the sessions, then the spaced reviews inside them, then check that the planned hours match the free hours.
6. Write the plan and the calendar file, then run the self-check.

## 5. Rules
- Phases, in this order: Learn (study each topic once, ending about 45% of the way to the exam); Practise (questions and past papers by topic, to about 75%); Revise and mock (mixed topics and timed mocks, to 7 days before the exam); Final week.
- Sessions: 45–90 minutes, with a 10-minute break inside any session longer than an hour, and no more than 3 hours of study a day unless the free time says otherwise. Mocks and the exam are exempt from both limits: they run the exam's full length. Every Learn session ends with 10 minutes of closed-book recall: write down what you remember, then check it against the notes. A Revise session is mixed practice across several topics, weakest first, with no notes open until the end.
- Spaced review: each topic is reviewed 1, 3, 7, 14 and 28 days after it is first studied. A review slot is the first 15–20 minutes of a later session: closed-book recall of that topic (write what you remember, or answer 3–5 quick questions), then check against the notes and fix the gaps. A session holds at most 2 review slots; a third moves to the next session. A review due on a day with no session (no free time, or the rest day) moves to the next session after that day. One that falls in the final 2 days is dropped. Name the reviews in the session's title ("Practise rates · review bonding + moles").
- Mocks: 3 timed mocks if 6 weeks or more remain, 2 if 3 weeks to under 6, 1 if 7 days to under 3 weeks. Each is the exam's full length, under exam conditions, at the exam's start time where the free time allows, and the last one ends at least 4 days before the exam, so it may fall in the final week. Each mock is followed within 2 days by a 60-minute Mock review: mark it, list the mistakes by topic, and give those topics the next week's spare review time.
- Rest and catch-up: one day a week with no study. Each week ends with a Catch-up session of about 10% of that week's hours (at least 45 minutes), left empty for missed work, and a 20-minute Checkpoint. Both count as planned hours.
- Final week: no new topics; mixed practice and reviews of weak topics; the last 2 days at no more than half the usual hours; the day before, at most an hour of light review of summary notes, then getting ready and an early night; on the exam day, a 20-minute warm-up ending at least an hour before the start, then the exam itself as an event.
- Use only the topics in the syllabus and the free time given. Never move a fixed commitment.
- Session titles: start with the session type and name the topic, as in "Learn organic chemistry: alkanes": at most 8 words, or 14 when the title names reviews. No commas or semicolons in any title; join topics with " + " and parts with " · ".
- Write every date with its weekday, as in "Mon 2 Nov 2026", and times as 24-hour hh:mm.

## 6. Output
Use these sections in this order. Write "None" under any that is empty.
1. **Header**: the subject, start date, exam date, start time, length and time zone, days and weeks to go, then "Hours: <x> h available, <y> h planned in <n> sessions", and every assumption, clash or note from parts 2 and 3.
2. **Topics**: a table with the columns # | Topic | Exam weight | Your rating | Hours | First studied | Method. Method is how to study it, with a short reason (flashcards for terms and facts; worked examples then practice for problems; essay plans for long answers; diagrams for processes). A total row for Hours.
3. **Phases**: a table with the columns Phase | From | To | What you do.
4. **Week by week**: for each week, a heading with the week number, its dates and its planned hours ("Week 1 · Mon 2 Nov – Sun 8 Nov 2026 · 10 h"), then a table with the columns Date | Start | End | Session | Type, where Type is Learn, Practise, Revise, Mock, Mock review, Catch-up, Checkpoint, Warm-up or Exam. In date and time order. If the plan has more than 40 sessions, give each week as one line instead (its dates, hours, topics and any mock), and the calendar holds every session. Never write "and so on" or "continue the pattern": every session is in the calendar.
5. **Mock exams**: each mock's date and time, what it covers, and its review date.
6. **When you fall behind**: 3–5 lines: move a missed session into that week's Catch-up slot; if that is full, drop the next review of the lightest, strongest topic, never a mock, a mock review or the final week; if you are more than 2 sessions behind in a week, use the Checkpoint to move the rest of that topic into the next week's sessions; never study on the rest day to catch up.
7. **Weekly checkpoint**: what to do in the 20 minutes: 5 quick questions from memory on that week's topics, rate each topic from 1 to 5, and give any topic rated 1 or 2 the next week's spare review time.
8. **Final week and exam day**: a checklist of the last 7 days, the day before (what to pack, the route, the start time, sleep) and the exam morning.
9. **Calendar file**: one event per session, including the mocks, mock reviews, catch-ups, checkpoints, the warm-up and the exam. If you can make files, attach it as study-plan.ics and give its name and event count. If you can't, give the calendar text in code blocks of at most 40 events each, every one a complete calendar that imports on its own, named by the weeks it covers (study-plan-weeks-1-4.ics, study-plan-weeks-5-8.ics…), each introduced by "Save the text below as a file named <name>, then import it." Never stop a code block part-way: if the reply can't hold every block, finish the last whole block, then write "Reply 'next calendar' for <name of the next file> (weeks <x>–<y>)." and on that reply give the next blocks in the same shape.

The calendar text, exactly in this shape (one line per field, no blank lines):
- BEGIN:VCALENDAR, then VERSION:2.0, PRODID:-//Study plan//EN, CALSCALE:GREGORIAN, METHOD:PUBLISH, X-WR-CALNAME:Study plan for <subject>, and X-WR-TIMEZONE:<the IANA time zone, such as Europe/London> when a time zone is known.
- For each event: BEGIN:VEVENT; UID:<yyyymmdd>-<two-digit number>@study-plan, unique; DTSTAMP:<start date as yyyymmdd>T000000Z; DTSTART:<yyyymmdd>T<hhmmss>; DTEND:<yyyymmdd>T<hhmmss>; SUMMARY:<the session title>; END:VEVENT. Times are local, with no Z and no TZID.
- END:VCALENDAR.
- Session titles in SUMMARY have no commas or semicolons, as the title rule says.

## 7. Self-check
Before replying, check each of these and fix any failure:
- Every syllabus topic is in the Topics table, has a Learn session, at least one Practise session and its reviews, and its hours in the table match the sessions in section 4.
- Every session is inside the free time, clear of every fixed commitment, with no two overlapping, and no study on a rest day.
- The planned hours each week, counting catch-ups and checkpoints, are within half an hour of the hours available (or the header explains the gap), and no day has more than 3 hours of sessions other than a mock or the exam unless the free time allows it.
- Every review falls 1, 3, 7, 14 or 28 days after the topic's first session, or in the next session after that day, or was dropped by the rule, and no session holds more than 2 review slots.
- The mocks follow the count rule, the last ends at least 4 days before the exam, and each has a Mock review within 2 days.
- No new topic appears in the final 7 days, and the warm-up and the exam are on the exam date at the right times.
- Every date has the right weekday and lies between the start date and the exam.
- The calendar has exactly one event per session across its file or files, each with a unique UID, a DTSTART and DTEND matching the plan and a title with no commas, and every file or code block starts with BEGIN:VCALENDAR and ends with END:VCALENDAR.
Then reply with the output only, ending with one line: "Checked: <n> weeks, <n> sessions, <n> mocks, <x> h planned of <y> h available, <n> events in <n> calendar file(s)."

## 8. Setup
Works as one paste in any chat app, with no calendar connection. Where the app can create files, you get a .ics file to download; where it can't, you get calendar text to save as study-plan.ics. A long plan without file-making may come as several calendar texts, each saved as its own file and imported the same way. Import with your calendar's import option (in Google Calendar: Settings, then Import and export; in Apple Calendar: File, then Import; in Outlook, look for Import or Add calendar), into a calendar set to the time zone you gave. If the syllabus is a file, attach it and write "see attached" in the syllabus block.

Paste the result after your assistant creates it. This optional check stays in this tab and is not sent to LazyCoder.