Admissions Ops

admissions-ops Router

Output Language

Two rules. Both are fixed: there is no configuration key for either, and there is no way for a user to request a non-English artifact from this repository.

Artifacts are English. Reports, checklists, tracker cells, CV/resume prose, statement drafts, and summaries. The chat language never reaches an artifact.

Chat is the user's language. If the user writes to you in Chinese, every word you address to them is Chinese from your first sentence onward — progress narration, preambles, I'll start by… lines, descriptions of what you are about to read or run, plans, findings, and questions included. A mixed-language turn follows the user's own prose, not the command scaffold, the flags, or the URL: /admissions-ops program --write-drafts for student x: followed by one Chinese sentence is a Chinese turn. Never open in English and switch later.

• Subagents. Prepend both rules verbatim to every subagent prompt. A worker does not inherit the parent's rule.
• Program conflict. If an official source requires a statement or CV in a language other than English, this repository cannot produce it. Record the conflict in the report and say so. Never switch the artifact language.
• Diagnostics. Machine output from npm run * stays English in logs and in quoted error text. Restate it in the user's language when explaining it in chat; do not translate the error string itself.

"English" here means script, not ASCII. Saarbrücken, Kovač, and naïve are valid English-document content. The deterministic guards reject Chinese, Japanese, and Korean script only.

Mode Routing

Determine the mode from $mode:

If $mode is not recognized but contains an official university or department program URL, route to program.

Discovery Mode

Show this menu:

admissions-ops

Available commands:
  /admissions-ops {official URL}  Run the one-program draft pipeline
  /admissions-ops program         Run one URL or selected inbox entry through the draft pipeline
  /admissions-ops inbox           Review curated entries in programs/inbox.yml
  /admissions-ops compare         Compare evaluated programs only
  /admissions-ops cv              Create an academic CV or resume adaptation plan
  /admissions-ops statement       Create a statement plan and draft for a reviewed program
  /admissions-ops tracker         Review tracker and checklist state

Runtime commands that read or write applicant-specific live state require --student <student-id> and use students/{student-id}/. For the program workflow, --write-drafts is explicit user approval to write Review Required CV/resume and statement draft artifacts after successful dry-runs; it is not approval to mark anything final or externally ready.

Full Pipeline Default

The default program workflow is one agent-led draft pipeline:

1. read the selected students/{student-id}/ workspace;
2. retrieve and cite official sources for the selected program only;
3. write or update shared catalog facts and the student-scoped evaluation, report, checklist, and tracker row;
4. create or revise the LLM-authored CV/resume adaptation plan and, when official instructions require a statement and statement-brief.md exists, the LLM-authored statement_plan, statement draft, and claim map;
5. run npm run cv -- --student <student-id> --program <program-id> as the deterministic dry-run renderer and validator (append --document-type academic_cv|admissions_resume when the user explicitly overrides the plan's document type; the override is logged and, on write, persisted into the plan);
6. when a statement plan, LLM-authored draft, and claim map are in scope and statement-brief.md exists, run npm run statement -- --student <student-id> --program <program-id> as the deterministic dry-run packager and validator;
7. inspect the dry-run artifacts, links, evidence maps, and validation concerns;
8. if the user specified --write-drafts and the dry-runs succeeded without blockers, rerun the applicable deterministic renderer or packager with --write to refresh only Review Required draft artifacts and report/tracker links;
9. return one final review bundle.

Stop mid-pipeline only for a real blocker: missing selected-student files, inaccessible official sources, ambiguous program identity or intake, conflicting official requirements that prevent a truthful draft, or explicit approval before any --write operation. A user-specified --write-drafts flag is that approval only for post-dry-run draft artifact writes.

Context Loading

For program, compare, cv, statement, and tracker, read:

• AGENTS.md
• DATA_CONTRACT.md
• modes/_shared.md
• modes/{mode}.md

For inbox, read:

• AGENTS.md
• modes/inbox.md
• programs/inbox.yml if it exists, otherwise programs/inbox.example.yml

Execute the selected mode instructions. Do not run broad discovery unless a future mode explicitly implements it.