Self-paced learning
Build with a team of AI agents
Coordinate several agents and integrate their work.
Your lessons
-
Split work by dependency and write set
Turn three tracker features into a written plan with owners, checks, write sets, and an honest parallel-versus-sequential split before any worker starts.
-
Assign roles, contracts and acceptance criteria
Give every task one owner, a least-privilege OpenCode subagent, a frozen contract, and acceptance criteria a stranger can check.
-
Isolate worktrees, ports and secrets
Give every parallel worker its own Git worktree, branch, Vite port, and gitignored placeholder secret so two workers cannot overwrite files or verify the wrong app.
-
Dispatch workers and verify handoffs
Run each worker in its own worktree, keep shared context small, bound its steps, and treat every “done” as an unverified claim until you re-run the checks.
-
Merge in order and resolve conflicts
Merge verified branches in dependency order, resolve src/main.ts by combining intents, re-check after every merge, and undo safely without reset --hard.
-
Prove the combined outcome
Add Today view and Clear completed + Undo with two isolated workers, then prove behaviour that only exists when due, tags, search, view, and archive work together.
Your project
Coordinate several agents and integrate their work.
Publish the merged task tracker (due dates, tags, search, Today view, Clear completed + Undo) and explain how you split, isolated, verified, and integrated the workers. The URL must be public HTTPS. Do not include API keys, .env contents, tokens, or OpenCode share links. This save is self-reported evidence pending review — it is not automatically checked, certified, or instructor-approved.
Check your work
- Decomposition
Every task has an owner, a deliverable, a check, and an explicit dependency (or none). Parallel tasks have disjoint feature files, and every shared file is labelled interface or merge point.
- Contracts and roles
Each worker is a least-privilege subagent with a frozen contract and binary acceptance criteria, including one regression check.
- Isolation
No two workers share a worktree, branch, --strictPort, or untracked secret path. Placeholder values only; .env.local is gitignored.
- Orchestration
Handoffs include exact command output and a not-verified line. Status uses planned / in progress / blocked / done, unverified / verified. No worker claim is accepted without a check you ran.
- Integration
Merges follow dependency order. Conflicts record both intents and the rule. Combined npm test, typecheck, and the browser script pass on the integration port after the last merge.
- Evidence
The pack is dated and reproducible. The submitted URL is public HTTPS with secrets redacted. The save is self-reported pending review, not an automated certificate.