← Back to library

Turn course evaluations into a tracked list of fixes

Nick Feamster exported his course evaluations, had Claude Code summarize the constructive themes, and opened a single GitHub issue holding a checkbox for each theme. Agents then worked those boxes as briefs for concrete concrete teaching fixes and materials changes.

  • OutcomeMake student feedback lead to real course changes by turning its themes into a checklist issue that agents work through and you tick off.
  • SetupAn afternoon+
  • LevelIntermediate
  • CreditNick Feamster
View original
Works with
Claude CodeClaude

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 24, 2026

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?

  1. Summarize the evaluationsAsk for praise and, more importantly, the constructive themes.
  2. File one tracking issueList every theme as its own checkbox in one issue.
  3. Work items as specsPoint agents at each box and review their changes.
  4. Note what shippedLink each checked box to the commit that fixed it.
  5. 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.

Prompt0 variables
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?
It serves as plan and record at once: open boxes show what is left, checked ones show what shipped.
What changed first?
Graded work, the loudest theme, was restructured with visible rubrics and grading keys.

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.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminWorkflow✓ AI dry run

Ask Reddit's experience before you pick a library

Let your coding agent search Reddit for long-term user reports on a library, an error message or a competitor before you commit to a choice.

Credit: u/karanb192 on r/ClaudeCode

Minutes
Operations & AdminSkill✓ AI dry run

Compare design options with a weighted score and stress test

Use the trade-study-report skill from Anthropic's Claude for Manufacturing plugin to turn a filled-in options matrix and test results into a ranked, sourced comparison, set aside any option that breaks a hard requirement, vary the weights to see whether the winner changes, and draft a decision memo an engineer reviews and signs.

Credit: anthropics

Under an hour
Operations & AdminSkill✓ AI dry run

Connect your agent to a system with no ready connector

Use the custom-connector skill from Anthropic's Claude for Manufacturing plugin to name the exact system and one data flow, check for an existing vendor or community MCP server before building anything, settle on the highest workable access route down to a scheduled export, record why, keep credentials out of the chat and explain how the chosen route is likely to break.

Credit: anthropics

An afternoon+
Operations & AdminSkill✓ AI dry run

Join plant exports and ERP data, with mismatches explained

Use the data-consolidate skill from Anthropic's Claude for Manufacturing plugin to identify each export file, check that every source covers the same dates before joining, pull matching ERP and maintenance records, normalize part and order numbers with a log of every rule applied, sort every record that fails to match into a named class with a proposed fix, and apply nothing without your yes.

Credit: anthropics

An afternoon+