NEXELENCE

Learning

Generative AI and Agentic AI: Background, Full Roadmap, Syllabus and Future

What generative AI and AI agents are, how they developed, and a complete eight-stage roadmap with syllabus covering prompting, RAG, fine-tuning, agents and MCP, plus risks, free resources and an honest outlook.

23 Oct 2026 · 12 min read

Generative AI, systems that produce text, images, code and more, went from research curiosity to everyday tool in just a few years. The next wave, agentic AI, goes a step further: software that uses these models to plan, call tools and complete multi-step tasks. This guide explains the background, the key ideas, a complete learning roadmap with syllabus, the risks you must understand and where the field may go. Sources are linked at the end, and anything that is our own estimate or opinion is labelled.

The key ideas in plain language

  • Generative AI refers to models that create new content, such as text, images, audio or code, after learning patterns from large amounts of data.
  • Large language models (LLMs) are very large neural networks trained on substantial text data that can handle many language tasks, from answering questions to summarising and writing code.
  • Prompting means steering a model with instructions and examples, without changing the model itself.
  • Fine-tuning adapts a model by training it further on your own examples. Parameter-efficient methods fine-tune only a small number of extra parameters and can reach performance comparable to full fine-tuning at far lower cost.
  • Embeddings and vector search turn text into lists of numbers so that similar meanings sit close together, which lets software retrieve relevant passages by meaning rather than exact words.
  • Retrieval-augmented generation (RAG) combines a language model with a searchable store of documents, so answers can draw on current, private or domain-specific information. The idea was introduced in a 2020 research paper.
  • Tool use (function calling) lets a model return a structured request to call a function, such as a search or a database query. Your application runs it and passes the result back.
  • Agents are systems in which a model directs its own process and tool use. Anthropic's widely read engineering guide separates two kinds of agentic system: workflows, where models and tools are orchestrated through predefined code paths, and agents, where the model dynamically decides its own steps and tools. IBM describes agentic AI as a system that can accomplish a specific goal with limited supervision.

A short history

Dates below are first-submission or announcement dates from the sources listed at the end.

WhenMilestone
June 2014Goodfellow and colleagues introduce generative adversarial networks (GANs), in which a generator and a discriminator compete as a two-player game.
June 2017"Attention Is All You Need" introduces the Transformer, an architecture built entirely on attention, which became the foundation of modern language models.
October 2018BERT sets new results across eleven natural language processing benchmarks.
May 2020GPT-3 is described as a 175-billion-parameter language model that performs many tasks from just a few examples in the prompt. The same month, the RAG paper is published.
June 2020Denoising diffusion probabilistic models show high-quality image generation, starting the diffusion-model wave behind many image generators.
June 2021LoRA shows that fine-tuning very large models can use dramatically fewer trainable parameters and less GPU memory.
October 2022The ReAct paper shows models interleaving reasoning and actions, an early blueprint for tool-using agents.
Late 2022ChatGPT is released to the public, bringing chat-based generative AI to a mass audience.
February 2023Toolformer explores models teaching themselves to use tools. LLaMA is released to the research community, with models from 7 to 65 billion parameters trained on publicly available data, and helps spark the open-weight model ecosystem.
November 2024Anthropic announces the Model Context Protocol (MCP), an open standard for connecting AI applications to external data and tools, since adopted by several assistants and developer tools.
December 2024Anthropic publishes "Building effective agents", a practical guide that distinguishes workflows from agents and describes common patterns.

The learning roadmap: eight stages

The plan assumes roughly ten hours of study a week and some comfort with Python. The durations are our own planning estimates, not guarantees. Free and paid courses publish their own pacing, which is a useful reference: the Hugging Face LLM course is designed so each chapter takes about a week at six to eight hours a week, and its Agents course is organised in units of about a week at three to four hours. DeepLearning.AI lists short courses from under two hours (for example MCP) to around 26 hours (RAG), as stated on its course pages.

StageFocusEstimated time
0Foundations: Python, APIs, machine learning basics4 to 6 weeks
1How LLMs work and effective prompting2 to 3 weeks
2Building with APIs: structured output and tool use3 to 4 weeks
3Embeddings, vector search and RAG4 to 5 weeks
4Fine-tuning and adaptation3 to 4 weeks
5Agents, orchestration and MCP4 to 6 weeks
6Evaluation, safety, observability and cost3 to 4 weeks
7Capstone, portfolio and deployment4 to 6 weeks

That is roughly seven to ten months in total, less if you already know machine learning.

Syllabus: what to study at each stage

Stage 0: Foundations

  • Python: functions, classes, packaging, virtual environments, async basics
  • Working with web APIs, JSON, authentication and rate limits
  • Machine learning basics: training, validation, overfitting, evaluation metrics
  • Neural network basics and an intuition for how a Transformer processes text
  • Git and GitHub, and the command line

Stage 1: How LLMs work and effective prompting

  • Tokens, context windows, sampling settings and why outputs vary
  • Prompting techniques: clear instructions, examples, role and context, structured prompts, step-by-step reasoning, prompt chaining
  • Defining success criteria and test cases before tuning prompts
  • Knowing when prompting is not the right fix: sometimes a different model or a different approach cuts cost and latency more than rewriting the prompt

Stage 2: Building with APIs

  • Calling model APIs, streaming responses and handling errors and retries
  • Structured output: asking for JSON that matches a schema and validating it
  • Tool use: defining tool schemas, handling tool calls, parallel calls, returning results to the model
  • Conversation state, memory and context management
  • Security basics for API keys and user input

Stage 3: Embeddings, vector search and RAG

  • Embeddings and similarity search; vector databases and indexes
  • Document processing: cleaning, chunking strategies, metadata
  • Building a RAG pipeline: retrieve, rank, assemble context, generate, cite sources
  • Improving retrieval: hybrid search, reranking, query rewriting
  • Evaluating retrieval and answers separately, and handling "I don't know"

Stage 4: Fine-tuning and adaptation

  • When to prompt, when to retrieve and when to fine-tune
  • Preparing and curating training data
  • Parameter-efficient fine-tuning such as LoRA and the Hugging Face PEFT library
  • Evaluating a fine-tuned model against the base model and against a strong prompt
  • Post-training ideas at an introductory level, such as supervised fine-tuning and preference tuning

Stage 5: Agents, orchestration and MCP

  • Workflow patterns: prompt chaining, routing, parallelisation, orchestrator-workers and evaluator-optimiser loops
  • Agents: tools, thoughts, actions and observations; stopping conditions and human checkpoints
  • Frameworks you may meet, such as smolagents, LangGraph and LlamaIndex, and the case for starting with plain code
  • The Model Context Protocol: exposing tools and data to AI applications through a standard interface
  • Memory for long-running agents and multi-agent designs, and their trade-offs
  • Starting simple: use the simplest system that meets the need, and add agent autonomy only when it earns its cost

Stage 6: Evaluation, safety, observability and cost

  • Building evaluation sets, automated checks and human review; tracking regressions
  • Observability: logging prompts, tool calls and outputs, tracing multi-step runs
  • Guardrails: input and output validation, permission limits and approval steps for risky actions
  • Security: the OWASP risks for LLM applications, covered in the next section
  • Cost and latency: model choice, caching, batching and prompt length
  • Privacy and data handling for user and company data

Stage 7: Capstone, portfolio and deployment

  • One end-to-end application, such as a document assistant with RAG, evaluation results and a short write-up of failures and fixes
  • Deployment behind an API or web app with logging, rate limits and a clear privacy note
  • A repository with documentation, a demo and an honest limitations section
  • Interview preparation: system-design discussions for LLM applications, evaluation strategies, trade-offs between RAG, fine-tuning and agents

Risks and responsible use

Generative systems can be confidently wrong, can be manipulated and can leak data if built carelessly. Treat the following as core skills.

  • The OWASP Top 10 for LLM and Gen AI applications (2025 edition) lists: prompt injection, sensitive information disclosure, supply chain, data and model poisoning, improper output handling, excessive agency, system prompt leakage, vector and embedding weaknesses, misinformation and unbounded consumption. Learn each one and how you would test for it. "Excessive agency" matters especially for agents: give tools the least permission they need.
  • NIST published a Generative AI Profile (AI 600-1) in July 2024 as a voluntary companion to its AI Risk Management Framework.
  • The EU AI Act applies in phases. Rules for general-purpose AI models began applying on 2 August 2025, with models already on the market given until 2 August 2027, and other obligations have been adjusted since. Check the official sources for current dates before relying on any of them.
  • India's Digital Personal Data Protection Act, 2023 sets rules for processing personal data, with its rules being brought into force in phases. If your system handles personal data, read the official text and take proper advice.
  • Practical habits: cite sources for factual answers, test with adversarial inputs, keep a human in the loop for high-stakes actions, log what the system does and be transparent with users that they are interacting with AI.

Free, credible resources

Portfolio projects

  • Document assistant: a RAG app over a set of PDFs or web pages that cites its sources, with an evaluation set of real questions.
  • Structured extraction: turn messy invoices, resumes or emails into validated JSON, and measure accuracy.
  • Tool-using assistant: an assistant that calls a calendar, a database or a search tool, with permission limits and logs.
  • Small fine-tune: adapt a small open model with LoRA for a narrow task and compare it with a good prompt.
  • MCP server: expose a useful data source or tool through the Model Context Protocol and document how to connect to it.
  • Evaluation harness: a reusable test suite that scores an LLM application and flags regressions.

Whatever you build, write down what fails. Honest error analysis impresses reviewers more than a polished demo.

Common mistakes

  • Building an agent when a simple prompt or fixed workflow would do
  • Skipping evaluation, so nobody can tell whether a change helped
  • Putting untrusted text into prompts without considering prompt injection
  • Giving tools broad permissions and no approval step for risky actions
  • Assuming retrieved or generated content is correct without citation or checks
  • Ignoring cost, latency and privacy until launch

Careers and outlook

  • Adoption: the Stanford AI Index 2025 reports that 78 percent of organisations said they used AI in 2024, up from 55 percent the year before, and that generative AI attracted $33.9 billion in private investment globally. The 2026 edition describes AI adoption as spreading at historic speed.
  • Skills gap: the 2026 AI Index also notes that formal education is lagging behind AI while people learn AI skills at every stage of life.
  • Jobs: the World Economic Forum's Future of Jobs Report 2025, as reported in coverage of it, points to AI and data skills among the fastest-growing. We could not verify specific figures from the report itself, so we do not quote them.
  • Safety lag: the 2026 AI Index headline also warns that responsible AI is not keeping pace with capability, with safety benchmarks lagging and incidents rising sharply, which is one reason careful engineering is valued.

Demand varies by location, sector and experience, and no course can promise a job or a salary.

Where the field is heading: our view

These are opinions, not forecasts or statistics, and the tooling changes quickly; even the authors of agent guides warn that much of the tooling landscape shifts within months.

  • From chat to action. More products will let models call tools and finish tasks, so skills in tool design, permissions and verification will matter.
  • Standards will reduce glue code. Open protocols such as MCP point towards tools that work across assistants.
  • Evaluation becomes a core discipline. Teams that can measure quality, cost and safety will out-ship teams that guess.
  • Smaller, specialised and open models will keep earning a place alongside the largest hosted ones, especially where cost, privacy or latency matter.
  • Governance becomes routine. Documentation, testing and transparency will be expected, not optional.
  • Fundamentals stay valuable. Solid programming, data skills, clear thinking and communication will outlast any framework.

Start this week

  1. Get an API key from one model provider and call it from a short Python script.
  2. Ask it to extract data from a messy text into JSON, and write five test cases to check it.
  3. Add one tool, such as a calculator or a search function, and watch how the model uses it.
  4. Write down where it fails. That is the beginning of your evaluation set.
  5. Follow a structured path with feedback and projects so you build skills in the right order.

If you would like guided, project-based learning, see the courses at Nexelence Academy or talk to us about where to begin.

Sources

Keep reading