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 Before reading any repo-relative path, derive `PROJECT_ROOT` from this loaded `SKILL.md`: start at the skill file's directory and walk upward until the nearest directory containing both `AGENTS.md` and `modes/`. Resolve every path in this router (`modes/`, `config/`, `data/`, scripts, templates, and output paths) against `PROJECT_ROOT`, never against the process's current working directory. This is required even when the checkout itself is nested (for example `Development\\career-ops`) or the command starts from a subdirectory. If those two sentinels cannot be found, stop and locate the career-ops checkout before reading or writing files. ## Invocation Notes - CLIs with slash-command registration can expose this router as `/career-ops`. - In Cursor, this skill lives at `.cursor/skills/career-ops/` and is auto-discovered; ask for a mode by name, or paste a JD/URL to trigger auto-pipeline. - Interactive Codex sessions use `codex` in the repo root. Slash commands are not guaranteed in Codex, so ask Codex to run the same mode by name if `/career-ops` is unavailable. - Headless Codex workers use `codex exec "prompt"`. - The routing semantics below stay the same regardless of whether the entrypoint is a slash command or a natural-language prompt. Codex prompt examples that map t...