Generate résumé tailored to an application (deferred) #134

New issue

Open

opened 2026-06-19 13:26:31 +00:00 by james · 0 comments

james commented

2026-06-19 13:26:31 +00:00

Owner

Generate a résumé tailored to a specific application from the user's Profile, Skills, and Experience data and the posting body.

Deferred — parked until the dependencies below are in a usable shape. Filing now so the epic captures it; no work should start on this ticket yet.

Dependencies

Career data domain (#4) — Profile, Skills, Education, Jobs (with positions and contributions), Contracts, Projects must be in the DB and editable from the PWA, otherwise there is nothing to draw from.
Application core (Applications epic #129) — the posting body and position name are the prompt context for tailoring.
Agent runtime architecture (#48 / epic #47) — this is the first user-visible generation feature; it should use whichever provider strategy and write-confirmation flow that ADR locks in, not invent its own.

Open questions (resolve before starting)

Output format: PDF directly, Markdown / structured doc the user can edit before exporting, or both?
Should the tailored résumé be persisted as an application document (reusing the Documents ticket's storage path) or kept ephemeral until the user saves it?
How does the user steer the tailoring beyond "here's the posting" — emphasis hints, length, tone?

Acceptance criteria (sketch)

Given an application with a posting body and a populated Profile / Skills / Experience, the user can request a tailored résumé and receive a coherent draft.
The draft can be saved as an application document (subject to the persistence decision above).
Generation runs through whatever provider strategy ADR is in force; no provider-specific code in the handler.

Part of epic #129. Do not start until the dependencies above have landed.

Generate a résumé tailored to a specific application from the user's Profile, Skills, and Experience data and the posting body. **Deferred — parked until the dependencies below are in a usable shape.** Filing now so the epic captures it; no work should start on this ticket yet. ## Dependencies - Career data domain (#4) — Profile, Skills, Education, Jobs (with positions and contributions), Contracts, Projects must be in the DB and editable from the PWA, otherwise there is nothing to draw from. - Application core (Applications epic #129) — the posting body and position name are the prompt context for tailoring. - Agent runtime architecture (#48 / epic #47) — this is the first user-visible *generation* feature; it should use whichever provider strategy and write-confirmation flow that ADR locks in, not invent its own. ## Open questions (resolve before starting) - Output format: PDF directly, Markdown / structured doc the user can edit before exporting, or both? - Should the tailored résumé be persisted as an application document (reusing the Documents ticket's storage path) or kept ephemeral until the user saves it? - How does the user steer the tailoring beyond \"here's the posting\" — emphasis hints, length, tone? ## Acceptance criteria (sketch) - [ ] Given an application with a posting body and a populated Profile / Skills / Experience, the user can request a tailored résumé and receive a coherent draft. - [ ] The draft can be saved as an application document (subject to the persistence decision above). - [ ] Generation runs through whatever provider strategy ADR is in force; no provider-specific code in the handler. Part of epic #129. Do not start until the dependencies above have landed.

james added the

area:pwa

area:service

labels

2026-06-19 13:27:29 +00:00