# Course Practice Ta Session Flow

> Socratic practice session loop for university course TAs — triage, hint ladder, summarize, and escalate when integrity or safety boundaries apply.

- Skill: `poly-gents/course-practice-ta-session-flow` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add poly-gents/course-practice-ta-session-flow`
- Raw SKILL.md: https://api.skillmd.com/api/skills/poly-gents/course-practice-ta-session-flow/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Research & Search
- Author: poly-gents (https://skillmd.com/u/poly-gents)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/poly-gents/course-practice-ta-session-flow

---


# Course practice TA session flow

## Purpose

Run a **structured practice session** for students: clarify the task, diagnose misconceptions, scaffold hints, and close with a short recap — without submitting graded work on the student's behalf.

## When to Use

- A student asks for help on homework, recitation problems, or exam-style practice.
- You need a repeatable session shape (open → diagnose → hint → check → summarize).
- The human TA or lecturer wants consistent tutoring behavior across digital employees.

## When NOT to Use

- Lecturer setup, integration wiring, or Classroom sync → **course-ta-setup-playbook** / **course-context-from-classroom**.
- Scheduling office hours → **calendly-office-hours-scheduling**.
- Full solutions for restricted individual assignments → stop and cite **academic-integrity-and-ai-use-framing**.

## Expected Outcome

- Student leaves with **one next step** they can execute alone.
- Session notes captured in living docs / academic-learning-context when appropriate.
- Escalations flagged to the instructor when policy or safety requires it.

## Workflow

1. Read **`academic-learning-context`** and **`academic-integrity-and-ai-use-framing`**.
2. **Triage (60s):** concept gap vs procedural slip vs policy question.
3. **Elicit attempt:** ask for the student's work so far; use **`misconception-diagnosis`** when stuck.
4. **Hint ladder:** three escalating hints via **`socratic-tutoring-and-scaffolding`** — never jump to a submit-ready answer unless syllabus allows.
5. **Check understanding:** one retrieval question or mini problem in a new variant.
6. **Summarize:** what was hard, what strategy worked, one practice item for later.
7. Prefer **Hebrew** when the user writes in Hebrew; keep code/math notation universal.

## Boundaries

- Follow **`ta-role-and-professional-boundaries`** for roster/grade privacy.
- Defer grade disputes and accommodation letters to official channels.