HK School of
Management and Technology

An online course for people who manage projects

AI Systems
with Claude

For Scrum Masters and Project Managers

From chatbot to AI team

Your sprint report writes itself

Plain English. No code.

Get the course for $497 USD

84 video lessons · 8 sections · one payment, yours forever

The Problem

Most project managers use AI like a smarter search box.
One question in, one answer out, then back to work. Very few have built something that keeps working after the chat window closes.

If you manage projects, you already have most of the skills this takes. You write scopes of work. You write procedures. You onboard people. A Claude skill is exactly that kind of document: a written procedure that tells Claude how to do one job, the same way every time.

Picture a small team of AI assistants instead

Each one owns a routine job you do every week. One writes your standup summary. Another reads weeks of standup notes and spots the patterns you missed. A third prepares your sprint report on a schedule, so when you sit down on Monday it is waiting for your review.

Most people assume building this takes a software developer. A few years ago, that was true. Today you build it by writing instructions in plain English. No code, no programming language. There is a learning curve and a few tools to install, and this course walks you through both, with one running project from the first lesson to the last.

84Video lessons
8Sections
5Working systems
5.1Hours of video

The Toolkit

Four things, each with one job.
None of them is a programming language.

Claude Chat

Your guide

Whenever something feels technical, ask. Step-by-step setup instructions in plain words, for your own machine.

Claude Code

Your builder

You describe what you want. It creates the files that make up your system, and you approve each step.

Claude Cowork

Your schedule

It runs your routine tasks on a schedule you set, while your computer is awake. Monday morning, the report is waiting.

CLAUDE.md

Your brief

A plain-English briefing file: your team's vocabulary, your standards, what good output looks like. Claude reads it at the start of every session.

The Method

Start small. Five steps.
The mistake we see most often is a do-everything agent on day one: hours of polishing, a fragile result, the real problem untouched. This is the other path.

  1. 01

    Pick one task you repeat every week.

    Something predictable, a little boring and a little annoying: a standup summary, a stakeholder update, a weekly backlog check.

  2. 02

    Write down how you do it, as if you were briefing a new hire.

    Then say: turn these steps into a skill called standup summary. Claude Code builds the skill for you.

  3. 03

    When the output is wrong, fix the skill, not the report.

    Tell Claude what was wrong and ask it to update the skill itself. The fix sticks for every future run. That is what makes a system self-improving.

  4. 04

    Group your skills into agents.

    An agent is a specialist with its own instructions and the skills it needs. It works through the job on its own. You describe its job in plain English; Claude Code builds it with you.

  5. 05

    Hand the routine runs to Cowork.

    The agent does the job. Cowork decides when it runs. Once it works on one project, copy it to the next project and the next team.

One skill that saves fifteen minutes a week returns about thirteen hours a year. Reinvest them, and the next skill comes faster.

What You Build

Five working systems, built in the capstone against one running project.
Jordan's team at NovaSprint: five developers, two-week sprints, work tracked in Linear, and the same four problems every sprint.

The Sprint Report Machine

The report runs as a scheduled skill instead of a Friday afternoon writing session.

The Retro Intelligence System

Finds the themes that come back across four sprints, with the evidence to take to the people who can remove the impediment.

The Stakeholder Comms Engine

Drafts the update from the project's facts. You read it, adjust it and press send.

The Backlog Health Monitor

Checks the backlog every week and flags what is stale, unsized or blocked.

The Risk and Dependency Tracker

Keeps the risk register current and follows the dependencies between teams.

The Skills Library

One hundred ready skills across five libraries. The add-on at checkout, for US$97 with the course.

Watch Four Lessons

Straight from the course, as the students see them.
Nothing is loaded from a video site; the lessons play here.

2.2What CoWork Is

1.4You Do Not Need to Be a Developer

3.2The RGCCO Framework

7.1The Sprint Report Machine

What students say about HKSM courses. This course is new, so these are from other HKSM courses, each labelled with its course.

"Very clear and crisp, straight to the point."
— Student, ICS/OT Cybersecurity Fundamentals
"Really useful. I will definitely be able to use many of these techniques and prompts. I was not expecting this to be so practical."
— Student, AI for Agile Project Managers and Scrum Masters
"I'm quite familiar with Lean from previous work, but this course is great because it gets to the point and explains concepts clearly. I don't feel like there's any wasted time."
— Student, Introduction to Lean Six Sigma
"A great introduction to project management fundamentals. Clear explanations, well-structured content, and a solid starting point for absolute beginners."
— Student, Introduction to Practical Project Management

Inside

Eight sections, 84 video lessons, one running project.
Every section adds one layer to what you take home at the end.

  1. 01

    Course Introduction 5 lessons

    What you will build, the three tools, and the running project: Jordan, a Scrum Master at NovaSprint, and the four problems every sprint brings.

  2. 02

    Claude CoWork 17 lessons

    Your scheduled assistant: projects and instructions, your first session, scheduling, the skills directory, MCP for non-developers, connecting Linear.

  3. 03

    Prompt Engineering 6 lessons

    From chatting to directing: the RGCCO framework, prompting for delegation, content engineering, common mistakes, reusable skills.

  4. 04

    Claude Code: Getting Started 9 lessons

    Why Claude Code, installing it on Windows, the terminal demystified, how Claude Code thinks, your first build, permissions and controls.

  5. 05

    Claude Code: Your World 16 lessons

    VS Code, CLAUDE.md, a project structure for PM work, real inputs, output formats, slash commands, your own skills, sub-agents and hooks.

  6. 06

    Connecting and Skills 12 lessons

    Node and Python, Linear via MCP, the pattern that generalises, your skills library strategy, a sprint report skill, a visual sprint report.

  7. 07

    Capstone 12 lessons

    The five systems, your project set-up, installing the skills library, what is in it, skills ownership, rolling it out to your team safely.

  8. 08

    Codex and Antigravity 7 lessons

    Your skills are not locked to one tool: Claude Code and Codex command by command, what ports cleanly and what breaks, choosing your tool.

The Offer

All you have to do is say maybe.
And you keep everything in the course, forever.

Everything in the course, as one set
  • The course, eight sections against one running project$497
  • Five working systems, yours to keep and modify$1,485
  • Seventy-six working files, real sprint data$197
  • Three framework one-pagers$47
  • Community access, first year$87
  • The support promise, until your system runs$1,997
  • The learning-hours record and claiming guide$47
  • Prompt and Content Engineering, nine page guide$47

Total value $4,502

Today, just $497 USD one payment

Already have an HKSM account? Use the same email at checkout and the course is added to it.

A paid Claude subscription is required to build the systems and is not included.

30-day money-back guarantee

My Ludicrous Guarantee

Thirty days. If you have completed 50 percent or less of the course and it is not what you needed, write to us and we refund you.

And there is a promise that runs the other way. We do not stop at the last lecture. Ask anything this course does not answer, in the community, and we work with you until your system is running. If a lecture is not clear and a written answer is not enough, we record a video explaining it.

You will finish this course with a working self-improving system. If you do not, we keep working with you until you do.

Questions

Do I need to pay for Claude as well?

Yes. The systems you build run in your own Claude account, which is a separate paid subscription to Anthropic and is not included in the course price. It is not something we resell or mark up, and you keep the account whatever you do with the course.

My employer will not allow it. Security will not approve it.

Demonstrate an outcome rather than asking permission for a tool. Use your own machine and the demo data supplied with the course, so no company information needs to move anywhere for you to learn this. When you do want it at work, ask for a sandbox and a pilot rather than a blanket yes.

Do I need to be technical?

No. Two lectures exist purely to explain why you are not becoming a developer. You need to scope work, write it down so somebody else can act on it, and judge whether what came back is acceptable. You have been doing that for years.

Is this just another prompting course?

Prompting is layer one of five, and it is genuinely foundational. The other four layers are what turn a good prompt into something that runs without you. If you already prompt well, layers two to five are the course.

How long does it take?

The video runs about five hours. Built along with the exercises, which is how it is meant to be taken, it runs closer to eleven. You can have the first system running in an evening.

Can I claim PDUs?

See our learning-hours record and claiming guide. Your certification body decides eligibility; report only your actual eligible learning time.

What if it is not for me?

Thirty days, and if you have completed 50 percent or less, write to us and we refund you.

Say “Maybe”

Pick one weekly task tonight, write its steps, and test them. That page is your first skill. You already know how to write it; you have been writing them your whole career. The course turns that page into a system that runs without you.