Route job workflows and applications

Route job application workflows via command or JD parsing

Centralizing multi-path job search workflows (research, evaluation, application, tracking) where auto-detection of intent saves friction.

• · mode string (empty, JD URL, JD text, or sub-command name)
• · job description (optional for auto-pipeline)
• · context file: data/pipeline.md (for pipeline mode)

• · command menu (discovery mode)
• · routed subagent or mode-specific behavior
• · discovery of JD vs sub-command intent

• · 15+ subagent modes (oferta, ofertas, contacto, deep, interview-prep, pdf, training, project, tracker, pipeline, apply, scan, batch, patterns, followup)

• · mode files exist in modes/ directory
• · context files (modes/_shared.md + mode-specific .md) are readable

• · JD text doesn't contain keyword triggers (responsibilities, requirements, about the role, etc.) — falls back to discovery
• · URL/file parsing fails — no auto-detection

• · explicit mode routing table with 15 modes
• · auto-pipeline keyword detection list (responsibilities, requirements, qualifications, about the role, we're looking for, company name + role)
• · documented subagent delegation for scan, apply, pipeline modes
• · inbox integration pattern (data/pipeline.md)