SuperAPI AI Directory

supervisor-review-queue

General & other

View repository

Updated 10-15 20:29

About this skill

/supervisor-review-queue
  1. Check ~/.claude/plugins/config/claude-for-legal-zh/legal-clinic/CLAUDE.md → supervision style. If not "Formal Review Queue": explain that the clinic is set to [tag/light-touch], there is no formal queue, and how to switch.
  2. Use the following workflow.
  3. Default: show what is awaiting review by urgency, by student.
  4. Actions: approve / approve with edits / send back with notes. All logged.
/legal-clinic:supervisor-review-queue
/legal-clinic:supervisor-review-queue --approve Q-003
/legal-clinic:supervisor-review-queue --return Q-004 "检查送达要求——本地规则已变更"

Supervisor Review Queue (optional)

Purpose

Some clinics want a formal gate: student drafts, supervisor reviews, output is released. Other clinics find this overly prescriptive — they supervise through case rounds and one-on-ones rather than through a queue.

This skill is active only when ~/.claude/plugins/config/claude-for-legal-zh/legal-clinic/CLAUDE.md → supervision style is "Formal Review Queue". Otherwise it is dormant — the cold-start interview asks the supervisor which mode they choose, and this is one of three options.

Whether to use a formal review workflow is a genuinely open question for clinic adoption. It depends on student experience level, case volume, and the supervisor's existing supervision approach. The supervisor decides at setup and can change it later.

Load context

~/.claude/plugins/config/claude-for-legal-zh/legal-clinic/CLAUDE.md → supervision style. If not "Formal Review Queue": respond "The clinic is set to [tag/light-touch] supervision — there is no formal queue. [Supervisor] reviews through [clinic's existing structure]. To switch to a formal queue, edit CLAUDE.md → supervision style."

If formal queue is enabled → read tag triggers and continue.

Queue

Stored at references/review-queue.yaml. Each entry:

- id: Q-001
  type: "draft"  # intake | draft | memo | status | client-letter
  client: "[姓名或编号]"
  student: "[姓名]"
  submitted: [时间戳]
  flags:
    - rule: "法院提交"
      detail: "驱逐答辩状 — 始终排队"
  content_path: "[文件路径]"
  status: "pending"  # pending | approved | edited-approved | returned

Modes

Awaiting review

## 审查队列 — [日期]

**待审查:** [N]件 | **最久等待:** [N]小时

### 🔴 截止日期敏感
| ID | 类型 | 当事人 | 学生 | 为何标记 | 等待时间 |
|---|---|---|---|---|---|

### 标准
[相同表格]

### 按学生
[分类——发现模式:谁排队很多,谁可能需要关注]

Review an item

Show full content + why flagged + student notes.

Approve / approve with edits / send back

  • Approve: status → approved, notify student, log.
  • Approve with edits: supervisor edits inline, the approved version is the edited version, the original is kept in the log so the student can see the diff (teaching moment).
  • Send back: with notes. Student revises and resubmits.

Logging

Every action is logged. The approval log is the clinic record — it proves that a licensed attorney in the clinic's jurisdiction reviewed student work before it went to a client or court. This matters for the clinic's own compliance and for student evaluation.

Teaching signals

The queue is also data. Patterns in send-backs ("student X always misses service requirements") are a coaching conversation. Patterns in edits ("everyone's demand letters are too long") are updates to next semester's /ramp .

What this skill does not do

  • Run only after the supervisor chooses it. It is one of three supervision modes, not the only one.
  • Auto-approve. Approval is by the supervisor.
  • Replace the clinic's existing supervision structure. It is a gate on work product, not a substitute for case rounds, one-on-ones, or observing students doing the actual work.