andrew-shwetzer/career-ops-plugin-do-not-fork-currently-updating-v2-

# Application Form Assistant

Help fill out job application forms with personalized, honest answers.

**CRITICAL: NEVER auto-submit an application.** Always show the user every
answer and get explicit confirmation before any form interaction. Always stop
before any submit button.

## Step 0: Load Context

1. Read `data/profile.yml` for structured background
2. Read `data/resume.md` for full resume text
3. Find the relevant evaluation in `data/evaluations/`
4. Check `data/research/{company}.md` for company intel

# Compare Opportunities

Side-by-side comparison of evaluated job opportunities.

## Step 0: Load Evaluations

Read all files in `data/evaluations/`. Parse the scores, archetype, company,
role, location, and compensation from each.

## Step 1: Select Opportunities

- If user specified companies/roles: match to evaluations (fuzzy OK)
- If "compare my top options" or no argument: select top 3-5 by score
  with non-terminal status (Evaluated, Resume Ready, Applied, Interview)

# Evaluate a Job Posting

You are a career strategist evaluating a job posting against the user's background.
Your job: give an honest, specific assessment. Not cheerleading.

Read references/scoring-rubric.md and references/archetypes.md before starting.

## Step 0: Load Profile

Read `data/profile.yml` in the current project directory.

If it doesn't exist, tell the user:

> "I need to know about your background first. Let's set that up quickly."

# career-ops Help

Guide the user through available skills based on where they are in their
job search.

## Step 0: Check State

Read `data/profile.yml` - does it exist?
Read `data/applications.md` - how many entries?
Glob `data/evaluations/*.md` - how many evaluations?
Glob `data/resumes/*.html` - how many resumes?

## Step 1: Show Skill Directory

# Draft Outreach

Create personalized outreach messages for job search networking.

## Step 0: Load Context

1. Read `data/profile.yml`
2. Check `data/research/{company}.md` for company intelligence
3. Check `data/evaluations/` for any evaluation at this company

If no company research exists:
> "I don't have research on {company} yet. Better outreach comes from
> better intel. Want me to research them first, or should I draft
> something with what I know?"

# Company Research

Build an intelligence brief on a target company.

## Step 1: Gather Data

Use WebSearch to find:

1. **Company basics:** What they do, size, founded, HQ, funding/revenue
2. **Recent news (last 6 months):** Product launches, layoffs, acquisitions,
   leadership changes, funding rounds
3. **Culture signals:** Glassdoor rating + recurring themes, any "best places
   to work" lists or notable controversies
4. **Team/department:** Who leads the department you'd join? Likely hiring

# Scan for Job Openings

Search company career portals for roles matching your profile.
Use ATS type and slug detection (see references/ats-endpoints.md) to build
targeted site-scoped WebSearch queries.

## Step 0: Load Context

1. Read `data/profile.yml` for target roles, skills, seniority
2. Read `config/portals.yml` if it exists (company watchlist)
3. Read `data/scan-history.md` if it exists (dedup against seen postings)
4. Read `data/applications.md` to exclude roles already tracked

## Step 1: Determine What to Scan

# Tailor Your Resume

Generate an ATS-optimized resume customized for a specific job posting.
Read references/ats-rules.md before generating any HTML.

## Step 0: Load Context

1. Read `data/profile.yml` for structured background data
2. Read `data/resume.md` if it exists (full resume text for detail)
3. Find the target evaluation:
   - If the user specified a company/role, search `data/evaluations/` for a match
   - If "latest" or no argument, use the most recent evaluation file
   - If ambiguous, list recent evaluations and ask which one
4. If no evaluation exists:

# Application Tracker

View and manage your job applications in one place.

## Step 0: Load Tracker

Read `data/applications.md`. If it doesn't exist, create it with the header:

```markdown
# Job Applications

| Date Added | Date Applied | Company | Role | Score | Status | Evaluation | Notes |
|---|---|---|---|---|---|---|---|
```

# Triage Pipeline

Quick-score scan results to find the best candidates for full evaluation.

## Step 0: Load Context

1. Read `data/profile.yml`
2. Read `data/pipeline.md` - the queue from scan results
3. Read `data/applications.md` - exclude already-tracked roles

If pipeline is empty:
> "Your pipeline is empty. Scan some companies first:
> say 'scan {company name}' or 'scan all' for your watchlist."