GitHub Certified: Agentic AI Developer study materials
GitHub Certified: Agentic AI Developer study resources

GitHub Certified: Agentic AI Developer study plan

GitHub Certified: Agentic AI Developer · Give each week a clear focus.

8 weeks · About 6 hours per week

Week 1

Operations and supervision of autonomous AI agents in GitHub-driven SDLC workflows

  • Map the full agent lifecycle in a GitHub-driven SDLC and label each hand-off point where a human must supervise

  • Write an explicit supervision contract for one agent: scope, permitted actions, escalation triggers, and stop conditions

  • Configure branch protection and required-review rules that prevent an agent from merging to a protected branch unreviewed

  • Draft three realistic failure scenarios (runaway loop, over-broad edit, silent test skip) and the operator response to each

Your checkpoint

A supervision runbook for one agent stored as a repository document, covering scope, escalation triggers, stop conditions, and three rehearsed failure responses

Week 2

Operations and supervision of autonomous AI agents in GitHub-driven SDLC workflows & Configuration of agentic systems

  • Define the agent's tool and permission surface and justify each permission against a required capability

  • Author the agent instruction file that specifies task intake, planning steps, verification steps, and reporting format

  • Simulate three supervised task runs by hand and log every point where the agent needed a human decision

  • Revise the instruction file to eliminate at least two of the logged decision points

Your checkpoint

A versioned agent instruction file plus a supervision log from three simulated runs, with a documented diff showing the revisions made in response

Week 3

Configuration of agentic systems

  • Configure an agentic system end to end: triggers, context sources, tool access, output destinations, and secrets handling

  • Separate read-only and write-capable tool access into distinct configurations and verify the restricted one blocks writes

  • Set context-window and file-scope limits, then confirm the agent refuses an out-of-scope request

  • Document every configuration parameter and its default, owner, and change-approval path

Your checkpoint

A working agent configuration in a test repository plus a parameter register listing each setting, its owner, and its change-approval requirement

Week 4

Evaluation of agent behavior and output quality

  • Build a scored evaluation rubric for agent output covering correctness, scope discipline, test coverage, and explanation quality

  • Assemble a fixed evaluation set of at least ten representative tasks with expected outcomes

  • Run the evaluation set against the configured agent and record scores per criterion

  • Identify the three lowest-scoring criteria and trace each to a specific configuration or instruction cause

Your checkpoint

An evaluation report with per-task scores across all criteria and a root-cause note for each of the three weakest areas

Week 5

Evaluation of agent behavior and output quality & Orchestration of agents in production environments

  • Automate the evaluation set so it runs on every change to agent configuration

  • Define pass/fail gates that block a configuration change from promotion when evaluation scores regress

  • Add regression cases for the failures found in week 4 and confirm the gates now catch them

  • Compare agent output quality across two model or prompt variants and select one with stated evidence

Your checkpoint

A repeatable evaluation pipeline that scores agent output automatically and blocks promotion on regression, demonstrated on at least one deliberately bad configuration change

Week 6

Orchestration of agents in production environments

  • Orchestrate two agents on a shared task with a defined hand-off contract and artifact format

  • Implement concurrency and conflict handling so parallel agent work does not collide on the same files

  • Define retry, timeout, and rollback behavior for a failed agent run and demonstrate each triggering correctly

  • Instrument the pipeline with logs and metrics that let an operator reconstruct what an agent did after the fact

Your checkpoint

A multi-agent orchestration pipeline with working hand-offs, conflict handling, timeout and rollback behavior, plus a post-run trace that reconstructs one full task

Week 7

Governance, safety, and reliable delivery with agents & Orchestration of agents in production environments

  • Enumerate the risk surface of the orchestrated system and assign each risk a mitigation, owner, and detection method

  • Enforce least-privilege credentials and verify that an agent cannot reach resources outside its declared scope

  • Write the audit trail specification required to answer who approved what, when, and on what evidence

  • Run one adversarial or malformed-input scenario and confirm the system fails safely rather than silently

Your checkpoint

A governance and safety dossier containing the risk register, least-privilege verification evidence, audit trail specification, and results of one adversarial test

Week 8

Operations and supervision of autonomous AI agents in GitHub-driven SDLC workflows & Configuration of agentic systems & Evaluation of agent behavior and output quality & Orchestration of agents in production environments & Governance, safety, and reliable delivery with agents

  • Rebuild the full agentic workflow from scratch in a clean repository without consulting prior notes

  • Re-run the complete evaluation suite and compare scores against the week 4 baseline

  • Close every gap revealed by the rebuild and re-verify the affected configuration and governance controls

  • Produce a one-page operational handover covering supervision, evaluation gates, orchestration behavior, and safety controls

Your checkpoint

A clean-room rebuild of the end-to-end agentic workflow passing the full evaluation suite, accompanied by a one-page operational handover document

Milestones

Week 2: Supervision runbook and agent instruction file both exist in version control, and three simulated runs are logged with human decision points identified

Week 4: Evaluation rubric, ten-task evaluation set, and a scored baseline report with root-cause analysis are complete

Week 6: Evaluation gates block a deliberately regressed configuration, and a two-agent pipeline completes one task with a reconstructable trace

Week 8: Clean-room rebuild passes the full evaluation suite at or above the week 4 baseline, with governance dossier and handover document complete