Week 5

The brief: scope and variants

Rules of the build

Submission & final checklist

Back to Track

Deliverable: a shipped project + an honest record.

What you submit

1. The repo — public or shared with mentors: CLAUDE.md, your subagent(s), full commit history showing the stages.
2. The final PR with the track's honest-description format: what it does (against the "done" definition, point by point) · what the agent did vs. what you changed by hand · one thing you rejected during review and why · the debugging note of the week.
3. A 5-minute demo or write-up in the group channel: show the thing working, then one honest reflection — where the agent saved you the most time, and where it cost you time.
4. Cross-review: review one classmate's capstone PR — with your reviewer subagent as input and your own read as the verdict. Leave at least two substantive comments.

You are done with the track when

• [ ] The project meets every statement in your "done" definition — and nothing was quietly added or dropped.
• [ ] Every diff in the final PR is one you can explain line by line.
• [ ] The security pass is clean: no secrets in files, history, or screenshots.
• [ ] Your PR description honestly separates the agent's work from yours.
• [ ] You reviewed a classmate's work and gave substantive feedback.
• [ ] You can answer, in your own words: what does the agent amplify — and what stays yours?

That last question is Week 1's thesis, closed as a loop. If your answer today is richer than it would have been five weeks ago — the track did its job.

The HackYourFuture curriculum is licensed under CC BY-NC-SA 4.0 *https://hackyourfuture.net/*

Built with ❤️ by the HackYourFuture community · Thank you, contributors

Found a mistake or have a suggestion? Let us know in the feedback form.