<h1 align="center">your-next-resume</h1>
<p align="center">
<b>Imagine your resume six months from now — and get the roadmap that earns it.</b><br>
An agent skill. Runs on your machine. Your resume never leaves it.
</p>
<p align="center">
<a href="https://github.com/voidforall/your-next-resume/actions/workflows/ci.yml"><img src="https://github.com/voidforall/your-next-resume/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
<a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue.svg" alt="MIT license"></a>
<img src="https://img.shields.io/badge/node-%3E%3D18-339933?logo=node.js&logoColor=white" alt="Node >= 18">
<img src="https://img.shields.io/badge/dependencies-zero-lightgrey" alt="Zero dependencies">
</p>
**No line appears on the projection unless a milestone earns it.** Every green line traces to a
dated milestone that names the evidence which would prove it — a repo, a merged PR, a design doc
your team reviewed. If nothing earns a line, it's deleted, not softened.
<p align="center">
<img src="docs/media/diptych.png" alt="Left: today's resume. Right: the projection, with reframed lines in amber and projected lines in green, under a stamp reading PROJECTED STATE · 28 FEB 2027 — EARNED ONLY IF THE ROADMAP IS COMPLETED." width="100%">
</p>
```bash
npx skills add voidforall/your-next-resume
```
Then ask your agent: *"here's my CV and the job I want — what would my resume look like in six months?"*
## The rule
**No line appears on the projection unless a milestone earns it.**
Every green line traces to a dated milestone that names the evidence which would prove it — a repo, a merged PR, a design doc your team reviewed. If nothing earns a line, the line is deleted, not softened. That is what separates this from a machine that writes you a flattering lie: the projection is a claim, and the roadmap is what makes it payable.
Amber lines are different: those are true *today*, reworded to speak the target's language, with the original kept underneath. Reframing may never add a fact.
## What you get
Seven files in `./your-next-resume/`:
| | |
| --- | --- |
| `projection.pdf` | the stamped future-state resume — **not** submittable, and it says so in the band, on every projected line, and in the PDF metadata |
| `resume-today.pdf` | everything true about you today, retuned for the target — **submittable this afternoon** |
| `roadmap.html` | the plan, offline and self-contained |
| `projection.html` · `resume-today.html` | the same two documents on screen |
| `roadmap.md` · `projection.md` | the source. Yours to edit; re-render any time |
<p align="center">
<img src="docs/media/roadmap.png" alt="A milestone card: Deliverable, Evidence and Learning fields, a Steps checklist with a nested, collapsed Tasks sub-list under each step, and a supplementary progress bar reading 2 of 9 action items done, distinct from the green Earns block below it." width="100%">
</p>
Each milestone says what to build, by when, what evidence proves it, and which resume line it buys. It is labelled **At work** or **Own time**, and the page shows the split — because a plan that quietly assumes your evenings is a plan for people who have evenings.
A milestone breaks down into **Steps**, and a Step can break down further into granular,
roughly-hour-sized **Tasks** — collapsed by default so the page stays scannable, open the moment
you're ready to work through one. Tick a task and the progress bar above it moves, its Step's
checkbox updates (checked, or a dash if partway through), and the roadmap-wide tally at the top of
the page moves too — three levels, one tick, always in gray or `--accent`, never the green that
means a milestone is actually, Evidence-backed done.
The page ships two views, switchable at the bottom: a dated **Timeline**, and a game-style **Map**
— milestones laid out by dependency, lit up or dimmed as you click through what a milestone needs
and what it unlocks, dashed and grayed out until every prerequisite is actually done.
<p align="center">
<img src="docs/media/tech-tree.png" alt="The Map view: milestones as connected nodes, one selected and highlighted along its full dependency chain while unrelated nodes dim, with a detail panel on the right showing that milestone's Deliverable, Evidence and Earns block." width="100%">
</p>
## Requirements
Node 18+ and Chrome, Chromium or Edge for the PDFs. No API keys, no account, no network — everything runs locally, and nothing is uploaded. Without a browser you still get every document, and instructions to print them yourself.
Zero runtime dependencies. The roadmap page is one self-contained HTML file — no build step, no
CDN, opens from `file://` forever.
MIT.