Beginner · Builder · 45 minutes
Available · Short lesson
From idea to verified release
See how priorities, requirements, Linear issues, Cursor, GitHub PRs and CI form one accountable delivery workflow without duplicating project tracking.
Before you start
No earlier Academy lesson required.
Optional: Git Workflow EssentialsThink of it like this
A restaurant order has one ticket, a recipe, a kitchen station and a quality check. You do not need five copies of the same order to know whether dinner is ready.
What you should remember
- Follow three core stops: save/check/publish, define a small change, then justify a release decision. The 45-minute core is a suggested study budget; optional extensions are separate.
- Commit records a version, merge accepts a change and deployment publishes a version. Verify the intended revision and actual user journey before calling a release complete.
- Define the problem, user, owner, requirement, non-goal and dependency before assigning implementation. Keep the PRD in the owning repository and delivery work in Linear.
- Checks apply to a particular commit and prove only the behaviors they test. Code review and acceptance evidence still matter; new changes need relevant checks again.
- Use one fictional lesson-edit example throughout the core. Detailed PRD/team material is reference reading; revenue planning is an alternative exercise.
- First-deployment settings, security review and agent coordination are optional companions. Add services when implemented behavior needs them, with appropriate access and cost controls.
- Reading, attempting an exercise and demonstrating its criteria are different. Paper exercises do not submit data to another app or automatically award progress.
Try it yourself
Open the companion guide and follow its three core stops using one fictional lesson edit. Explain save/check/publish; write a problem, owner, requirement, non-goal and dependency; then complete the worked exercise's five-line handoff and recovery decision. Write fictional answers in a practice note you control and compare with the guide's answer key. Stop after the core; choose first-deployment settings, security review or agent coordination only when useful. Never enter confidential information. The guide's paper exercises have no submission or storage mechanism of their own.
Practice lab · Fictional example
Decide what happens next
Work through six stages. Choose the best action, see why, and learn what evidence belongs in each system. Nothing is saved or sent to an external service.
Stage 1 of 6
Qualify an incoming request
A fictional Sales rep reports that audit exports require manual work. They ask for a new button but have one anecdote and no estimate of frequency.
0 of 6 decisions correct
Case study · Public record · 2026-10-11
From a source lesson to a visible Academy card
This is the public path of the Cursor workflows lesson. A merged document, a catalog change, and a closed issue are different events. Nothing you type here is saved.
1. Requirement
The Academy card needs an exercise, one knowledge check, and sources. The long Cursor lesson stays in docs/builder-academy/cursor-agent-workflows.md.
2. Plan
The accepted trade-off is one record in lib/ai-academy.ts. A new app, or pasting the full Markdown into the card, was rejected.
3. Agent
Implementation is a bounded edit on a feature branch. The agent stops before merge and deploy.
4. Diff and CI
Local tests are not GitHub CI. The reviewable evidence for the card is pull request #68.
5. Linear
Pull request #67 merged the Markdown at c635cc4 on 2026-10-11. Pull request #68 merged the catalog record at 451147c at 18:40 UTC the same day, and Linear closed KRU-19 seconds later. A closed issue records status. It does not check the live site.
6. Next issue
Name one smaller follow-up. A reflection stays in this browser session and is not saved.
Stays in this browser tab. Refreshing clears it.
Sources checked 2026-10-11
Pull request #67, merged 2026-10-11 ↗Pull request #68, merged 2026-10-11 ↗