Skip to main content
skill CX Codex

prep-plan — Claude Code skill: prep plans and installation

The prep-plan Claude Code skill builds a week-by-week plan for job and interview preparation. It uses the candidate’s timeline, available hours, target companies, and weak areas from past sessions.

MIT ★ 345 updated 2026-11-14

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add nishant-Tiwari24/cracked
/plugin install cracked@cracked
Open on GitHub

What prep-plan does

The skill gathers the deadline, daily study hours, target roles and companies, DSA level, and programming language. It reads $CRACKED_DIR/journal.md for scores and recurring weak spots, then writes the plan to $CRACKED_DIR/plan.md. ALLOCATION.md guides the time split; company briefs shape topic choices when targets are supplied. The current date comes from date +%F or Python.

On later runs, it compares completed checkpoints with the journal and revises the remaining weeks while keeping finished ones as history. It needs profile data from cracked-profile, the company-intel skill for company-specific planning, and a $CRACKED_DIR journal. If the agent has no Skill tool, it can use the named skills’ SKILL.md files in core/, interview/, profile/, or strategy/.

What it helps with

  • map interview preparation into weekly tasks
  • allocate study time around a deadline
  • factor recurring weak spots into a prep schedule
  • revise the remaining plan after progress reviews

Example prompts for the agent

  • Build a week-by-week interview prep plan around my deadline and weak areas.
  • Plan my preparation for these target companies using my session history.
  • Review my progress and rewrite the remaining weeks of the plan.

How to install prep-plan

1Plugin marketplace

/plugin marketplace add nishant-Tiwari24/cracked
/plugin install cracked@cracked

This installs the whole cracked plugin with all its skills

2Skills CLI (Vercel)

npx skills add nishant-Tiwari24/cracked --skill prep-plan -a claude-code

3Manually: put the files in place

~/.claude/skills/prep-plan/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/prep-plan/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about prep-plan

How do I install prep-plan in Claude Code?

Add the marketplace with /plugin marketplace add nishant-Tiwari24/cracked, then install the plugin with /plugin install cracked@cracked.

What does prep-plan do?

It creates a weekly job-prep schedule using the available time, target companies, and past session results. When run again, it checks progress and updates the unfinished weeks.

What does prep-plan need to work?

It needs data from cracked-profile, the company-intel skill for company-specific plans, and a $CRACKED_DIR folder containing journal.md. It also uses ALLOCATION.md and date +%F or Python to get today’s date.

Source text

SKILL.md · MIT
---
name: prep-plan
description: Build a realistic week-by-week placement / job-prep plan from the candidate's deadline, daily hours, target companies, current level and their actual weak spots from past cracked sessions. Re-running it reviews progress and re-plans. Use when the user asks for a prep roadmap, a study plan for placements or interviews, "how should I prepare in N weeks", what to study next, or wants to review their prep progress.
---

# Prep plan

A plan that ignores where the candidate actually is goes in the bin by week two. This one is built from their deadline, their hours, and their real performance data in the cracked journal, and it's rebuilt whenever they come back.

## 0. Inputs

1. Call the Skill tool with "cracked-profile". You need: `deadline`, `hours_per_day`, `target_companies`, `target_roles`, `dsa_level`, `language`. Ask for any that are missing (in one round).
2. For each company in `target_companies` (max 3), call the Skill tool with "company-intel". Use the briefs' DSA topic mix to weight the patterns, and their process to schedule company-specific mocks. No target companies? Plan for the target tier.
3. Read `$CRACKED_DIR/journal.md`. **Normalise the tags first**: lowercase, hyphenate, map near-duplicates onto the canonical list in `cracked-profile` (`DP`, `dynamic-programming` and `dp` → `dp-1d` or `dp-2d` by context; `edgecases` → `edge-cases`). Then count sessions per skill, collect every `weak_spots` tag with its frequency and recency, count `pattern:` fields, and note score trends.
4. Read `$CRACKED_DIR/plan.md` if it exists. If it does, this is a **review run**: go to §3 first.

## 1. Budget the time

- Weeks available = deadline − today. Get today's date by running `date +%F` (or `python3 -c "import datetime; print(datetime.date.today())"`); never assume it. Total hours = weeks × 7 × hours_per_day × 0.8 (life happens; plan for 80%).
- Split the hours by target, using [ALLOCATION.md](ALLOCATION.md) as the starting point, then shift 10–20% toward the most frequent weak-spot tags.
- If the time is unrealistic for the goal (e.g. 3 weeks, beginner, big-tech target), say so plainly, then give the **best plan for the time available** and a realistic alternative target. Never pretend it'll be fine.

## 2. Write the plan

Save to `$CRACKED_DIR/plan.md`:

```markdown
# Prep plan · <target> · <today> → <deadline>

## Reality check
<2–3 lines: time budget, the gap, the strategy>

## Weekly plan
### Week 1 (<dates>): <theme>
- DSA: <patterns + target problem counts, e.g. "Sliding window + two pointers: 12 problems (4E/6M/2H)">
- Core: <subject topics>
- Projects/Resume: <one concrete deliverable>
- Mock: <which cracked skill to run and when, e.g. "Sat: /mock-interview on arrays (medium)">
- Checkpoint: <a measurable goal to hit by Sunday>

### Week 2 …

## Daily template (<hours>/day)
<a time-boxed routine, e.g. 60 min new pattern · 45 min revision (spaced repetition of old problems) · 30 min core subject · 15 min log>

## Rules
- Weekly: 1 mock (alternating /mock-interview, /oa-sim, /core-viva), 1 /prep-plan review
- Never more than 2 days without revising old problems
```

Principles:
- **Pattern-first DSA**: group problems by pattern (use the `pattern-coach` skill's catalog by calling the Skill tool with "pattern-coach" if you need it). Sequence: arrays/hashing → two pointers/sliding window → binary search → stack → linked list → trees → heaps → graphs → DP → backtracking.
- **Front-load** resume and project work (`/roast-my-resume`, `/make-it-hireable`): applications open before interviews.
- **Mock early**, from week 1, not at the end. Mocks find weak spots; the plan adapts around them.
- **Company-weighted DSA**: when briefs exist, include each target company's top recent reported questions (`questions.py get "<Company>" --window 3m`) as named problems in the weekly lists.
- In the final 1–2 weeks: company-specific prep (`/resume-blueprint`, `/jd-match`, `/oa-sim` in that company's style, `/hr-round` company mode), revision, and no new topics.
- Keep it achievable. A plan they finish beats a perfect plan they abandon.

## 3. Review run (when a plan exists)

1. Compare the plan's checkpoints so far with the journal: which mocks happened, which scores, which weak-spot tags persist or are new.
2. Show a short progress report: `On track / Behind by ~N days / Ahead`, plus the 3 most important observations (e.g. "DP still fails in 3 of 3 mocks", "Communication up from 5 to 8").
3. Ask what got in the way, if they're behind. One question.
4. Rewrite the **remaining** weeks in `plan.md`. Keep completed weeks as history, marked ✅/🟡/❌.

## 4. Finish

Give the plan's headline and **this week's first three actions**, each with the exact cracked command to run. There's no scorecard for planning sessions; don't log to the journal.

---

*Skill calls:* if your agent has no Skill tool, open the named skill's `SKILL.md` in the cracked skills folder (`core/`, `interview/`, `profile/`, `strategy/`) and follow it instead.

© Nishant Tiwari · MIT · nishant-Tiwari24/cracked

Similar skills

All skills for Notes, tasks and projects →

From the same set20

The whole set →
resume-blueprint resume-blueprint is a Claude Code skill that builds a company-specific resume plan. It activates when someone wants to tailor a resume or get a template for a particular employer. CX Codex +1 ★ 345repo stars rejection-review The rejection-review Claude Code skill analyzes a failed interview or OA and identifies likely causes. It turns the findings into three focused drills and a revised prep plan. CX Codex +1 ★ 345repo stars hr-round The hr-round Claude Code skill coaches candidates through HR and behavioral interview questions. It reviews each answer and turns real experience into reusable stories. CX Codex +1 ★ 345repo stars jd-match The jd-match Claude Code skill compares a resume with a job description and scores the match. It activates when tailoring an application or preparing for an interview for a specific role. CX Codex +1 ★ 345repo stars core-viva The core-viva Claude Code skill quizzes developers on CS fundamentals and SQL. It starts for interview revision and adjusts question difficulty based on answers. CX Codex +1 ★ 345repo stars offer-decode The offer-decode Claude Code skill breaks down a job offer and estimates take-home pay. It runs on an offer letter, a CTC breakdown, or a request to compare terms and draft a negotiation reply. CX Codex +1 ★ 345repo stars system-design-mock The system-design-mock Claude Code skill runs practice interviews for system design, from fresher to SDE-2 level. It starts when someone asks to rehearse HLD or LLD, including a design prompt for a specific system. CX Codex +1 ★ 345repo stars referral-dm The referral-dm Claude Code skill drafts tailored messages for referral requests and job outreach. It can respond to hiring posts, contact recruiters or alumni, and write follow-ups. CX Codex +1 ★ 345repo stars

Project sponsors

Companies that keep this analytics open