01Hand off the first ticket
Your first real fix comes back in lesson 1, checked against its tests the same day. From there, every ticket leaves with a definition of done, so Devin stops guessing where done is.
Devin course · Included in Osum membership
You handed over a ticket. The run went off the rails, you corrected it, and the summary still said done. That is the babysitting loop, and it survives every plan tier. Learn the Defined Done: the scoped ticket that comes back proven, and the review that decides what merges.
Sound familiar?
“The promise was full autonomy, but the reality still involves a lot of babysitting. You give it a task, it goes off the rails, you correct it, it sort of gets back on track.”
“when people got to use it it was slow and code didn't work”
“you need an organization that's very AI-friendly in how the whole tech stack is set up plus a lot of tweaking and setting up to get it to that level.”
More tweaking rarely fixes it. A scoped ticket with a definition of done usually does. That’s the Defined Done, and this course teaches it.
What you’ll be able to do
01Your first real fix comes back in lesson 1, checked against its tests the same day. From there, every ticket leaves with a definition of done, so Devin stops guessing where done is.
02The proof lives in the ticket: test output, screenshots, a recording. A claim without its artifact goes back as one comment, so review starts from evidence.
03The snapshot, the repo rules and the secrets mean every session boots ready. Setup is paid once, not per ticket, and credentials never enter the chat.
04Your scoped run becomes a playbook with a macro. Every next ticket starts from the same proven procedure, corrections included.
05Recurring tickets start themselves on a schedule, bounded by a session cap and an invocation cap, with email only on failure. You review; the watch queues.
06Proof, diff, status, boundaries: four checks, every pull request. Agent or teammate, the checklist decides, and a failing check goes back as one comment.
The 60-second check
Devin says the bug is fixed. You have the ticket, the diff and the summary. Make the call the way you will on every run.
| Field | The ticket says |
|---|---|
| Bug | The booking form accepts past dates |
| Repro | Pick yesterday, submit, the booking goes through |
| Definition of done | Submit rejects past dates, the form's test passes, no other file changes |
| Proof required | The test output shown, not claimed |
“Fixed date validation in the booking form. All tests pass. Ready to merge.”
Approve it, ask for proof, or send it back?
Lesson 7, “Review Devin's pull requests in minutes, not evenings”, teaches the four checks on your own pull requests. Lesson 1 has you run your first real fix and check it in 15 minutes, so the check lands on work you already own.
The curriculum
Osum’s Devin course is 12 hands-on lessons, about 4 hours in all. Lesson 1 is a 15-minute fix you check against its tests the same day. By lesson 12 you run a weekly pipeline: scoped tickets in, proven pull requests out, an automation on the watch. You need your own Devin account and a repo. You finish with a certificate you can add to LinkedIn.
Module 01
You hold one real fix on your own repo, scoped with a definition of done and returned as a pull request with proof. This is the first run of the ticket pipeline you finish in lesson 12.
Module 02
You hold a repo that boots ready: an environment snapshot, rules in the repo, and a playbook that turns any ticket into the same scoped run.
Module 03
You hold the judgment layer: split work across parallel sessions, review what comes back in minutes, and let automations start tickets under a usage leash.
Module 04
You hold the whole pipeline: you know where the quota goes, you recover a stalled session from its worklog, and you run three tickets end to end in the capstone.
Us vs. them
The docs tell you what each setting does. YouTube shows you a demo. This course takes you from your first ticket to a pipeline that runs every week.
| Feature | Osum course | Official docs | YouTube walkthroughs | Free guides |
|---|---|---|---|---|
| Step-by-step path, first ticket to weekly pipeline | ✓ | Partly | Partly | ✕ |
| Hands-on exercise after every lesson | ✓ | ✕ | ✕ | ✕ |
| Scoping tickets with a definition of done | ✓ | ✓ | Partly | Partly |
| Proof, review and the four checks, taught on your repo | ✓ | Partly | ✕ | ✕ |
| Snapshots, rules and playbooks that carry between sessions | ✓ | ✓ | Partly | ✕ |
| Practice on your own low-risk work, nothing merged blind | ✓ | ✕ | ✕ | ✕ |
| Certificate you can add to LinkedIn | ✓ | ✕ | ✕ | ✕ |
| Official, always-current settings | Links to them | ✓ | Partly | Partly |
| Cost | Membership | Free | Free | Free |
One membership
The same membership covers Cursor for work inside your editor, Claude Code for fixes in your terminal and Codex for pull requests you’d merge. Each course has its own certificate.
Certificate
Show a client, a manager or a hiring team that you can hand work to Devin and merge only what passes your checks. The certificate records a final check you passed, one question per lesson.
Questions
One Osum membership covers this course, its certificate and every other course. It is a subscription. You see the price after your 2-minute plan, before you pay anything.
You can start the lessons right away. For the hands-on exercises you need your own Devin account, and the Free plan's light quota is enough for lesson 1. Pro was $20 a month when we checked on 28 September 2026, and the exercises run on a repo you own.
12 lessons, about 4 hours in all. Lesson 1 takes 15 minutes and ends with a real fix you can check the same day.
You need to read a diff and run a test command. If you maintain any repo, even a personal one, every exercise works on it. The course never asks you to merge anything you have not checked.
Prompts say what to do, not what finished looks like. Here you practice the Defined Done on a real ticket in every lesson, with a proof step and a review to check against. You finish with a weekly pipeline: assigned tickets in, proven pull requests out.
No course can promise a model that never guesses. You’ll learn to scope tickets so there is far less to guess, to demand proof inside the ticket, and to catch the confident wrong diff in minutes. A run that stalls becomes a recovery you can do, not a rerun.
No. Osum is independent and not affiliated with Cognition. The certificate is an Osum certificate.
The Defined Done is four habits: scope first, define done, prove it, review before merge. You get a checked fix in lesson 1, a weekly pipeline by lesson 12, a certificate and every other course in the library. A few quick questions, then your plan.
Keep exploring