Project 4 Submission
Push your harness repository to GitHub and submit its link to the Project 4 assignment in Canvas. Compare the repository with the tree below first. Leave out your .env file.
What the repository holds
- harness.py
- systemprompt.md
- PLAN.md
- skills/coding-loop/SKILL.md
- the task code from the starter: inbox.jsonl, detector.py, score.py
- transcript.md
What each file is
- harness.py: your Project 3 harness after the three changes the handout’s Part 1 asks of the LiteLLM chat extension.
- systemprompt.md: your agent’s standing rules from Project 3, rewritten for a coding agent; the harness reads it at startup as its first message.
- PLAN.md: the plan your agent wrote in plan mode for the job, before you typed approve.
- skills/coding-loop/SKILL.md: the course’s skill, copied from the starter, unchanged.
- detector.py: the task code after your agent’s change; inbox.jsonl and score.py as the starter shipped them.
- transcript.md: the session your agent saved: the job, the plan, approve, every file it wrote, every validation run, the report.
What to leave out
Leave out your .env file and the logs/ folder VS Code wrote in Project 3. A .env file or a key in the repository costs the clean-repo check and is reported to you by name.
How to submit
Push the repository with git push. Open it on GitHub and check that the six items above are there. Paste the repository’s address into the Project 4 assignment in Canvas and submit. Fill out the feedback form.
The examples
The published examples hold a systemprompt.md grown from Project 3’s four lines into a coding agent’s rules, and a transcript.md from one run of the coding-loop skill on the starter.