When should you use it?
- You read feedback once and forget it
- Your course materials live in a repo
- You teach several similar courses
Not for: Courses without version control; Feedback with personal details you cannot share
What do you need, and what do you get?
You need
- Exported evaluations
- Course repo
You get
- Themed summary
- One issue whose checkboxes map to the themes
- Commits linked to each item
How does it work, step by step?
- Summarize the evaluationsAsk for praise and, more importantly, the constructive themes.
- File one tracking issueList every theme as its own checkbox in one issue.
- Work items as specsPoint agents at each box and review their changes.
- Note what shippedLink each checked box to the commit that fixed it.
- Clone to other coursesReuse the structure for courses with similar issues.
The prompt
Our own prompt, inspired by Nick Feamster and written to work in Claude Code and Claude. Values in lime are placeholders.
Here is my course evaluation export (anonymized). Summarize what students liked, then list the constructive themes with a count of comments for each. Draft a GitHub issue called Course feedback follow-ups where each theme is a checkbox followed by a short proposed change. Do not change any course files yet.
Inspired by Nick Feamster: Using Claude Code to Modernize My Courses. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Strip student names and identifying details before sharing evaluations with a tool.
- Rubric and grading changes still need your judgment.
Our take
Turning each intention into an issue that then serves as the brief is a clean way to use agents on anything that drifts, not just code. The checklist doubling as a changelog is a nice touch. Nick's method keeps feedback from evaporating. Summarize the evaluations for constructive themes, not just praise, then open one GitHub issue with a checkbox per theme. Each box becomes a brief an agent can work from, and linking every checked box to the commit that fixed it turns the issue into a changelog for the course. Review every change the agents make; rubric and grading decisions still need your judgment. Strip student names and anything identifying before sharing evaluations with any tool, and check your institution's rules on that. The structure carries over to similar courses with similar complaints, which is where it saves the most time. Courses whose materials are not in version control would need that step first, or the tracking falls apart.
Where the time goes back: Feedback turns into tracked work instead of a memory that fades by next term.
FAQ
Why one issue?
What changed first?
Source and credit
Inspired by Nick Feamster. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Using Claude Code to Modernize My Courses
- Creator
- Nick Feamster
- Published on
- practicespace.substack.com (Substack)
- Original date
- Jun 3, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude Code
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.