Use this folder for markdown copies of job descriptions you want to evaluate through the pipeline without a live URL (paywalled boards, exports, or text you pasted from email).
-
Add a line to
data/pipeline.md(create the file if needed; see docs/SETUP.md) using thelocal:prefix:- [ ] local:jds/example-role-at-acme.md
-
Run
/job-forge pipeline(or your usual pipeline flow). The agent resolveslocal:jds/{filename}tojds/{filename}in the repo root and reads that file as the JD source. Seemodes/pipeline.md.
- One posting per file is easiest to track; name files so you recognize the role and company (slug-style names work well).
- Keep content as plain markdown or pasted JD text; no special front matter is required by the tooling described above.
- For a fictional structural example (safe to commit), see
examples/sample-jd.md. Your real files stay underjds/and remain gitignored.
Individual *.md JD files under jds/ are gitignored so real postings and employer text stay local. Only placeholders such as .gitkeep and this README.md are intended to ship with the repo.