prep-plan

Installation
SKILL.md

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 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

Installs
61
GitHub Stars
313
First Seen
7 days ago