Browse / Job hunt / CAREER-OPS-2.0

CAREER-OPS-2.0

chri75252

Authoritative contributor guide for Career-Ops 2.0 — the Multi-Agent Job Search System.

Open chri75252/CAREER-OPS-2.0 → Checked against the four rules.

Works with any agent

ships AGENTS.md, the cross-tool instruction file.

In its own words

README.mdchri75252/CAREER-OPS-2.0

Authoritative contributor guide for Career-Ops 2.0 — the Multi-Agent Job Search System. This file is the authoritative project core. It covers architecture, verification protocols, mode system wiring, data contracts, and operational constraints for this repository.

0. ABSOLUTE RULES (CRITICAL)

  • NO PROACTIVE SCRIPT EDITS

NEVER proactively edit any script, configuration, or structural file if the user explicitly instructs "DO NOT EDIT ANY FILES/SCRIPTS FOR NOW" or gives a similar directive to only investigate/report. Do not ignore this instruction under any circumstances, even if you spot an obvious or trivial bug. Report the issue and WAIT for explicit permission to edit.

  • NEVER POST EVALUATION TEXT IN CHAT

For single-evaluation runs (/career-ops with JD text provided), produce Blocks A-G per modes/oferta.md and write outputs only to files (report + conditional HTML + tracker TSV). Do not post the evaluation text in chat.

  • READ REQUIRED GROUNDING FILES FIRST

Before any evaluation or mode run, read: cv.md, config/profile.yml, modes/_profile.md, templates/states.yml. These are the data contract foundation.

0.1 Evidence Collection Order (Tool Routing Policy)

Follow this default tool order when investigating or implementing tasks:

Quoting 6% of the README. Read the rest on GitHub ↗

Read from the repository's git tree on 2026-08-17.