career-ops

# career-ops -- Router

career-ops is a multi-CLI job-search command center. The routing below is shared across supported agent CLIs even when the invocation surface differs.

Project Root Resolution

This catalog ships a **docs-only** router. Do not require the upstream `modes/`, `config/`, or `data/` tree. Use the routing table and discovery menu below. For the full Node runtime (PDF, portal scans, Playwright), clone [career-ops-hq/career-ops](https://github.com/career-ops-hq/career-ops).

Mode Routing

Determine the mode from `$mode`:

| Input | Mode |

|-------|------|

| (empty / no args) | `discovery` -- Show command menu |

| JD text or URL (no sub-command) | **`auto-pipeline`** |

| `oferta` | `oferta` |

| `ofertas` | `ofertas` |

| `contacto` | `contacto` |

| `deep` | `deep` |

| `interview-prep` | `interview-prep` |

| `interview` | `interview` |

| `eu-swe` | `regional/eu-swe` |

| `eu-fintech` | `regional/eu-fintech` |

| `interview/plan` | `interview/plan` |

| `interview/practice` | `interview/practice` |

| `interview/debrief` | `interview/debrief` |

| `pdf` | `pdf` |

| `text` | `text` |

| `latex` | `latex` |

| `latex-tex` | `latex-tex` |

| `email` | `email` |

| `add` | `add` |

| `expand` | `expand` |

| `training` | `training` |

| `project` | `project` |

| `tracker` | `tracker` |

| `agent-inbox` | `agent-inbox` |

| `inbox` | `agent-inbox` |

| `pipeline` | `pipeline` |

| `apply` | `apply` |

| `scan` | `scan` |

| `discover` | `discover` |

| `batch` | `batch` |

| `patterns` | `patterns` |

| `offer-prep` | `offer-prep` |

| `titles` | `titles` |

| `upskill` | `upskill` |

| `followup` | `followup` |

| `reply-watch` | `reply-watch` |

| `outcome` | `outcome` |

| `interview-redflag` | `interview-redflag` |

| `update` | `update` |

| `cover` | `cover` |

**Auto-pipeline detection:** If `$mode` is not a known sub-command AND contains JD text (keywords: "responsibilities", "requirements", "qualifications", "about the role", "we're looking for", company name + role) or a URL to a JD, execute `auto-pipeline`.

If `$mode` is not a sub-command AND doesn't look like a JD, show discovery.

---

Output Language Directive

Before executing any mode, read `config/profile.yml` if it exists and resolve:

- `language.output` → ISO language code for human-facing output. Default: `en`.

- `language.modes_dir` → optional market-mode directory. This controls market vocabulary and local evaluation rules only.

Inject this directive after loading the mode instructions and before producing any user-visible content:

> Write all human-facing output in `{language.output}` regardless of the language of these instructions or of the job description. This includes reports, tracker notes, PDFs, cover letters, outreach, interview prep, form answers, and summaries. If `language.modes_dir` supplies market-specific vocabulary, keep the market logic but explain terms in `{language.output}` when needed.

`language.output` is authoritative for prose. `modes_dir` is market context; it must not force the prose language.

---

Discovery Mode (no arguments)

If your CLI supports `/career-ops`, show this menu. In Codex, surface the same options in plain text and map the requested mode the same way.

Concrete equivalents for Codex prompt-driven sessions:

/career-ops {JD}           ↔ "Evaluate this JD with career-ops auto-pipeline: {JD or URL}"
/career-ops scan           ↔ "Run the career-ops scan mode and summarize new matches."
/career-ops pipeline       ↔ "Run the career-ops pipeline mode for data/pipeline.md."
/career-ops pdf            ↔ "Run the career-ops pdf mode for the latest evaluated role."
/career-ops email          ↔ "Run the career-ops email mode for the latest evaluated role."
/career-ops tracker        ↔ "Run the career-ops tracker mode and summarize the current statuses."

Show this menu:

career-ops -- Command Center

Available commands:
  /career-ops {JD}      → AUTO-PIPELINE: evaluate + report + PDF + tracker (paste text or URL