$ loading_
Professor's review queue — student output waits here for professor approval before going to clients or courts. Only active if "formal review queue" supervision style was chosen at setup; otherwise dormant. Use when the professor wants to see what's waiting for review, approve, edit-then-approve, or return an item.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "supervisor-review-queue" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/claude-for-legal/main/legal-clinic/skills/supervisor-review-queue/SKILL.md 2. Save it as ~/.claude/skills/supervisor-review-queue/SKILL.md 3. Reload skills and tell me it's ready
~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md → supervision style. If NOT "formal review queue": explain the clinic is set up for [flags/lighter-touch], no formal queue exists, and how to switch./legal-clinic:supervisor-review-queue
/legal-clinic:supervisor-review-queue --approve Q-003
/legal-clinic:supervisor-review-queue --return Q-004 "Check the service requirement — local rules changed"
Some clinics want a formal gate: student drafts, professor reviews, output releases. Others find that too prescriptive — they supervise through case rounds and one-on-ones, not through a queue.
This skill is only active if ~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md → Supervision style is "formal review queue." Otherwise it's dormant — the cold-start interview asks the professor which model they want, and this is one of three options.
Whether to use a formal review workflow is genuinely an open question for clinic adoption. It depends on student experience level, caseload, and how the professor already runs supervision. The professor decides at setup and can change it later.
~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md → supervision style. If NOT "formal review queue": respond with "The clinic is set up for [flags/lighter-touch] supervision — there's no formal queue. [Professor] reviews through [the clinic's existing structure]. To switch to a formal queue, edit CLAUDE.md → Supervision style."
If formal queue IS enabled → read flag triggers and proceed.
Lives at references/review-queue.yaml. Each entry:
- id: Q-001
type: "draft" # intake | draft | memo | status | client-letter
client: "[name or ID]"
student: "[name]"
submitted: [timestamp]
flags:
- rule: "Court filing"
detail: "Eviction answer — always queued"
content_path: "[path to the document]"
status: "pending" # pending | approved | edited-approved | returned
## Review Queue — [date]
**Pending:** [N] | **Oldest:** [N] hours
### 🔴 Deadline-sensitive
| ID | Type | Client | Student | Why flagged | Waiting |
|---|---|---|---|---|---|
### Standard
[same table]
### By student
[Breakdown — spot patterns: who's queueing a lot, who might need a check-in]
Show full content + why it was flagged + student notes.
Every action logged. Approval logs are clinic records — they document that a licensed attorney, solicitor, barrister, or other authorised legal professional in the clinic's jurisdiction reviewed student work before it went to a client or court. That matters for the clinic's own compliance and for student evaluation.
The queue is also data. Pattern in returns ("Student X keeps missing the service requirement") is a coaching conversation. Pattern in edits ("Everyone's demand letters are too long") is a /ramp update for next semester.
Diff a proposed handbook change against the current version, flag ripple effects and state supplement impacts. Use when user says "update the handbook", "add this to the handbook", "handbook change", or has a policy ready for insertion.
Review an offer letter and any restrictive covenants — jurisdiction check included. Substantive rules (covenant enforceability, pay-transparency, salary-history limits, exemption criteria) are researched per hire, not stored. Use when the user says "review this offer", "can we use a non-compete here", "check this offer letter", "hiring in [state]", or attaches an offer.
Draft an audience-specific summary from the privileged investigation memo — HR, leadership, or outside counsel versions. Use when an investigation memo needs to be communicated to an audience that should not see the full privileged work product.
Track the IP portfolio — registrations, renewals, maintenance fees, and use declarations. Use when checking what's renewing, adding or updating an asset, recording a maintenance filing, or auditing the register for gaps, lapses, and use-in-commerce questions. Receives handoffs from prosecution and clearance work.
IRAC-scaffolded case analysis memo with research gaps flagged — the scaffold, not the analysis. Rule blocks are RESEARCH NEEDED, Application is STUDENT ANALYSIS prompts, Conclusion is blank. Use when a student needs to scaffold a case analysis memo, write up their analysis, or build an IRAC memo for a case.
Read VDR documents and extract issues per house categories and materiality thresholds, producing findings in house memo format. Use when user says "review the data room", "extract issues from [folder]", "diligence review", "what's in the VDR", or points at VDR documents.