application-packagelisted

# Application Package The full pipeline for one role: evaluate honestly, build only if it is worth building, verify everything, log it, and hand it to the human to send. **This skill never submits an application.** It prepares. The human sends. ## Prerequisite Run **`jd-analyser`** first, before loading anything else. It separates stated requirements from post-hire responsibilities and returns the positioning brief. Build from that brief, not from your own read of the JD. Skipping this step is how a role that exists to *train* someone gets mis-built as a role that requires an expert. ## Files this skill expects ``` facts.md the only source of claimable facts profile.yml constraints, exclusions, deal-breakers applications.tsv the tracker reports/ one report per evaluated role output/cvs/ cv-<slug>.tex and .pdf output/cover-letters/ cl-<slug>.tex and .pdf ``` Scaffold from `examples/` if these do not exist. Never invent the user's background to fill a gap. ## Workflow ### 1. Quick score, immediately One line, before any other work: `**<Company> — <Role>. X/5.** <one-sentence reason>` Then stop and wait. Do not build documents until the user says go. Most roles should not be built, and finding that out in ten seconds is the point. ### 2. Verify the posting is actually live Never trust a search result or a cached link. Open the posting. A page showing only a navbar and a footer means the rol