AI Learning Plan / Skill Roadmap

Section 1: Goal Definition and Current-Level Baseline

1.1 End Goal (SMART Definition)

Target Outcome: [[Specific, Measurable Goal: e.g. "Build and deploy a production-ready RAG chatbot that answers questions from a custom knowledge base"]]

Why This Matters: [[Personal motivation: e.g. "Automate 4 hours of weekly research work" / "Land a role as an AI Engineer" / "Launch an AI-powered product"]]

Success Looks Like:

• [[Deliverable 1: e.g. "A working GitHub repo with documented code"]]

• [[Deliverable 2: e.g. "Can explain the system to a non-technical stakeholder"]]

• [[Deliverable 3: e.g. "Deployed and running on real users / real data"]]

1.2 Current-Level Baseline

Complete this self-assessment before starting. Honesty here saves weeks of wasted effort.

Baseline Summary: [[Your honest 1–2 sentence self-assessment: e.g. "I've watched YouTube tutorials on Python but never written a project from scratch. I understand what LLMs are but have never called an API."]]

Known Gaps to Fill Before Starting:

• [[Prerequisite gap 1: e.g. "Basic Python syntax (variables, loops, functions)"]]

• [[Prerequisite gap 2: e.g. "Understanding of REST APIs and JSON"]]

• [[Prerequisite gap 3: e.g. "Familiarity with command-line basics"]]

Section 2: Milestone-Based Phases

Phase 0: Prerequisites (Fill Gaps First)

Duration: [[1–2 weeks, adjust based on gaps identified above]]
Required before: Phase 1

Prerequisite checklist: only move forward when you can check all boxes:

• [ ] [[Prerequisite 1: e.g. "Can write a Python function that takes input and returns output"]]

• [ ] [[Prerequisite 2: e.g. "Can make a basic API call and parse the JSON response"]]

• [ ] [[Prerequisite 3: e.g. "Can use a terminal: navigate directories, install packages with pip"]]

Fast-track resources for Phase 0:

• [[Resource 1: e.g. "Python in 4 Hours: freeCodeCamp YouTube (free, 4 hr)"]]

• [[Resource 2: e.g. "Codecademy Learn Python 3: first 5 modules only (free tier)"]]

• [[Resource 3: e.g. "HTTP Crash Course: Traversy Media YouTube (free, 45 min)"]]

Phase 1: Beginner Foundation

Duration: [[Weeks 1–4 of your main plan]]
Weekly commitment: [[Hours per Week]]
Exit criteria: Complete Phase 1 Checkpoint (Section 3) before advancing.

What you learn:

• [[Core concept 1: e.g. "How large language models work: tokens, context window, temperature"]]

• [[Core concept 2: e.g. "Prompt anatomy: role, instruction, context, format, constraints"]]

• [[Core concept 3: e.g. "Key tools and APIs: OpenAI, Anthropic Claude, Hugging Face"]]

• [[Core concept 4: e.g. "Zero-shot, few-shot, chain-of-thought prompting patterns"]]

Phase 1 Resources:

Phase 1 Hands-On Project:

> [[Project Name: e.g. "Personal Prompt Toolkit"]]
> Build a collection of [[10–15]] reusable prompts for a task you do regularly (e.g., [[email drafting / meeting summaries / research synthesis]]). Test each prompt across at least [[2]] models. Document which works best and why in a short README.

Spaced-Repetition Approach for Phase 1:

• After each study session, write [[3]] things you learned without looking at notes (active recall).

• Review your notes from [[2 days ago]] before starting today's session (spaced repetition).

• Use a flashcard app (Anki, Remnote) for vocabulary: add [[5]] new cards per session.

Phase 2: Intermediate Application

Duration: [[Weeks 5–10 of your main plan]]
Weekly commitment: [[Hours per Week]]
Prerequisite: Phase 1 checkpoint passed.
Exit criteria: Complete Phase 2 Checkpoint (Section 3) before advancing.

What you learn:

• [[Intermediate concept 1: e.g. "RAG (Retrieval-Augmented Generation): embeddings, vector databases, chunking"]]

• [[Intermediate concept 2: e.g. "Function calling and tool use: structured outputs, API chaining"]]

• [[Intermediate concept 3: e.g. "Evaluation: measuring output quality, building test suites"]]

• [[Intermediate concept 4: e.g. "Prompt chaining and multi-step workflows"]]

• [[Intermediate concept 5: e.g. "Cost and latency trade-offs: model selection, caching, batching"]]

Phase 2 Resources:

Phase 2 Hands-On Projects:

> [[Project 2A: e.g. "Document Q&A Bot"]]
> Build a RAG pipeline over [[a PDF or document collection you own]]. Use [[OpenAI / Anthropic]] embeddings + [[Chroma / Pinecone]] vector store. Measure retrieval accuracy with [[5–10]] hand-crafted question/answer pairs. Write a brief evaluation report.

> [[Project 2B: e.g. "Automated Workflow Agent"]]
> Build a [[2–3 step]] agent that uses tool-calling to automate a real task: e.g., [[pulls live data from an API → summarizes → drafts a Slack message]]. Deploy it so it can run on a schedule or trigger.

Phase 3: Advanced Mastery

Duration: [[Weeks 11–[[End Week]] of your main plan]]
Weekly commitment: [[Hours per Week]]
Prerequisite: Phase 2 checkpoint passed.
Exit criteria: Capstone project complete, peer-reviewed, and documented.

What you learn:

• [[Advanced concept 1: e.g. "Fine-tuning: when to fine-tune vs. prompt, LoRA, QLoRA"]]

• [[Advanced concept 2: e.g. "Multi-agent systems: orchestration, memory, handoffs"]]

• [[Advanced concept 3: e.g. "Production concerns: observability, rate limits, fallbacks, cost monitoring"]]

• [[Advanced concept 4: e.g. "Evaluation at scale: LLM-as-judge, automated regression suites"]]

Phase 3 Resources:

Phase 3 Capstone Project:

> [[Capstone Project Name: e.g. "Production AI Feature for a Real Product"]]
> Build and deploy a complete AI-powered feature that solves [[a real problem in your work or life]]. Requirements:
> - Live deployment accessible to at least [[1 real user other than yourself]]
> - Evaluation suite with [[≥20]] test cases, documented pass rate
> - README documenting architecture, decisions, trade-offs, and lessons learned
> - Cost and latency report: actual spend and p95 latency under load
> - [[Optional: blog post or demo video explaining what you built]]

Section 3: Checkpoints and Assessments

Phase 1 Checkpoint (End of Week [[4]])

Pass all five before advancing to Phase 2. If you score below [[3/5]], spend one more week on Phase 1 before re-testing.

Self-assessment questions (score 0–2 each):

1. Explain, in plain language, what [[the core concept of your skill]] is and why it matters. Can you explain it to a non-technical friend in under 2 minutes?

1. Look at this prompt / piece of code / example: [[paste a real example from your practice]]. Identify [[2]] things that could be improved and explain why.

1. Without looking at notes, write out the [[3–5]] most important rules or patterns you've learned so far.

1. Find [[one thing that confused you this week]]. Research it and explain it in your own words.

1. Open your Phase 1 project. Can you add a small improvement in under [[30 minutes]] without following a tutorial?

Phase 1 pass score: [[4–5/5 → advance | 2–3/5 → review Week [[3–4]] material | 0–1/5 → restart Phase 1]]

Phase 2 Checkpoint (End of Week [[10]])

Practical assessment (complete all three):

1. Build-from-scratch test: Without a tutorial, build [[a minimal version of your Phase 2A project]] in under [[2 hours]]. Use only documentation, not step-by-step guides.

1. Debugging challenge: Intentionally introduce [[2]] common bugs into your project (e.g., [[broken context window handling / wrong embedding model]]). Fix them using only error messages and docs.

1. Explanation test: Record yourself (voice memo is fine) explaining [[your Phase 2 project]] to an imagined new colleague. Can you cover: what it does, how it works, what trade-offs you made, and what you'd do differently?

Phase 2 pass criteria: All three completed + you feel [[80%+]] confident explaining your project to a peer.

Phase 3 / Capstone Assessment

Peer review process:

• Share your capstone project with [[at least 1 person]] who works in [[the same field or a related field]].

• Ask them to complete this review form:

Self-review final checklist:

• [ ] Capstone deployed and working in production

• [ ] Evaluation suite passing at [[≥80%]]

• [ ] Cost and latency within [[your defined targets]]

• [ ] README complete with architecture diagram and decision log

• [ ] Peer review completed with score [[≥3.5/5 average]]

Section 4: Weekly Schedule and Time Budget

Time Budget Reality Check

Your available hours per week: [[Hours per Week]]
Recommended split: [[60%]] active practice / [[30%]] learning (video, reading) / [[10%]] review (flashcards, notes)

Your adjusted timeline: [[Phase 0: _ wk → Phase 1: wk → Phase 2: wk → Phase 3: wk → Total: _ wk]]

Sample Weekly Schedule ([[10 hrs/week]] example: adjust to your hours)

Buffer rule: Never schedule more than [[80%]] of your available hours. Life happens: [[2 hours/week]] of buffer prevents falling behind from cascading.

Section 5: Spaced and Active Learning System

Active Recall Protocol

Do this at the end of every study session (takes [[5 minutes]], doubles retention):

1. Close all notes and tabs.

1. Write down [[3–5]] things you just learned, from memory.

1. Write down [[1 question you still have]].

1. Check your notes: fill in the gaps.

1. Add new vocabulary to your flashcard deck (Anki or Remnote).

Spaced Repetition Schedule

The Feynman Technique (use when a concept feels foggy)

1. Write the concept name at the top of a blank page.

1. Explain it as if teaching a [[12-year-old / a new colleague with no background]].

1. Where you get stuck or vague → that is exactly what to study next.

1. Re-read the source, simplify your explanation, repeat.

Section 6: Common Pitfall Warnings

Pitfall 1: Tutorial Hell
Watching tutorials feels like progress but isn't. After completing any tutorial, immediately build something different using the same technique: without following the tutorial. If you can't, you don't know it yet. Cap tutorial time at [[30%]] of your weekly hours.

Pitfall 2: Skipping Prerequisites
Starting Phase 2 without Phase 1 mastery is the most common reason learners quit. The Phase 1 checkpoint exists for this reason: respect it even when it feels slow.

Pitfall 3: Building Without Evaluating
A project that "seems to work" is not evidence of mastery. Every project should have [[at least 10]] test cases with known-correct answers so you can measure whether it actually works, not just whether it sometimes works.

Pitfall 4: Learning in Isolation
Learning alone is slower and less effective. Find [[at least 1 person]] at a similar level to pair with: a learning partner doubles accountability and surfaces blind spots you'd never catch alone. [[Discord servers, Reddit communities, and local meetups]] are good places to find them.

Pitfall 5: Unrealistic Timelines
If you have [[5 hours/week]], you cannot master [[Skill]] in [[4 weeks]]. Use the timeline table in Section 4. Underestimating how long things take leads to discouragement and quitting, not faster learning.

Pitfall 6: Over-Tooling Early
Beginners often spend more time evaluating and switching tools than actually building. Pick [[one stack]] in Phase 1 and stick with it until Phase 2. Compare alternatives only after you have hands-on experience with the first.

Pitfall 7: Passive Reading Without Doing
Reading a book about [[your skill]] without running the code or applying the concept gives you familiarity but not skill. Every chapter should produce [[at least one small exercise or experiment]].

Section 7: Accountability and Review Cadence

Weekly Review (Every [[Sunday]], [[30–60 min]])

Answer these five questions in a running document or journal:

1. What did I complete this week? (list lessons, projects, hours logged)

1. What was the hardest thing I encountered? (describe the specific blocker)

1. How did I resolve it? (or: what do I still need to figure out?)

1. Am I on track with my timeline? (behind by [[__]] weeks / on track / ahead)

1. What is my single priority for next week?

Monthly Review (Once per Month, [[45–60 min]])

1. Re-run the baseline assessment from Section 1.2: score yourself honestly.

1. Update the [[Phase progress tracker]] below.

1. Adjust your timeline if needed: it is not a failure to extend the timeline; it is a failure to pretend you are on track when you are not.

1. Identify [[one skill area to go deeper in]] next month.

Phase Progress Tracker

Accountability Options (choose at least one)

• Learning partner: [[Name of partner]]: weekly [[15-minute]] sync to share wins and blockers.

• Public commitment: Post a [[weekly update on LinkedIn / Twitter / community Discord]]: public accountability dramatically improves follow-through.

• Mentor / coach: [[1 session per month]] with someone who is [[1–2 levels ahead of you]] in [[Skill]]. Can be informal (coffee chat) or paid (30-minute coaching call).

• Community: Join [[one active community]] related to [[Skill]]: [[e.g. Hugging Face forums, r/MachineLearning, LangChain Discord, Anthropic Discord]]. Lurk the first week, post a question the second week.

Resources Summary

Phase-by-Phase Quick Reference

Recommended Tools and Environments

This learning plan was generated using the AI How-To Learning Plan workflow. It is a personalized roadmap template: fill in all [[Token]] fields with your specific context before using. Timelines are estimates; adjust based on your actual weekly progress reviews.