Skip to content

fix: lead post-run summary with editing the wording, not the look (#60)#61

Merged
earino merged 1 commit into
mainfrom
fix/issue-60-editing-discoverability
Apr 29, 2026
Merged

fix: lead post-run summary with editing the wording, not the look (#60)#61
earino merged 1 commit into
mainfrom
fix/issue-60-editing-discoverability

Conversation

@earino

@earino earino commented Apr 29, 2026

Copy link
Copy Markdown
Owner

Summary

Closes #60 (reported by @JamieP44).

The Phase 9 post-run summary already saved tailored-resume.md and cover-letter.md alongside each PDF, and already pointed at the re-render flow. But it buried both behind a "tweak the look" framing that pointed at fonts and spacing — so students who wanted to change the wording before sending didn't see the editable source they already had.

Reframed: the .md sources are now the primary editing path, named explicitly with arrow callouts, led by "these PDFs are a strong starting draft, not the final artifact — they need a personal touch before sending." The Google Docs / Pages / Word / Canva path stays as a secondary option for anyone who prefers a rendered view.

No new features — discoverability and framing fix only.

What the student sees now (SKILL.md Phase 9 summary block)

Before:

💡 Edited a markdown file after this run? Ask me to "re-render the {resume|cover|prep} PDF"
and I'll regenerate just that PDF without re-running the full pipeline.

✨ Want to tweak the look? Open resume.pdf in Google Docs, Pages, Word, or Canva —
they all import PDFs and let you adjust fonts, spacing, and colors with tools
you already know.

After:

✏️  These PDFs are a strong starting draft, not the final artifact — they
need a personal touch before sending. The editable source is saved alongside
each PDF:

   tailored-resume.md  ← your resume, in plain markdown
   cover-letter.md     ← your cover letter, in plain markdown

Edit either file in any text editor (VS Code, TextEdit, Notepad, Vim, the
editor inside this CLI), then ask me to "re-render the {resume|cover|prep}
PDF" — I'll regenerate just that PDF, no AI second pass on your edits.

🎨 Prefer editing in a rendered view? Open resume.pdf in Google Docs, Pages,
Word, or Canva — they all import PDFs directly. Re-export to PDF before
submitting (Google Docs: File → Download → PDF Document).

Test plan

  • pytest -q — 459/459 pass on the existing suite
  • No SKILL.md structural test pins the changed wording (test_skill_md_prologue.py, test_skill_md_phase6.py, test_skill_md_weak_model_guards.py, test_render_pdf.py all checked)
  • Manual: ship a real /resumasher <jd> run end-to-end after merge and read the rendered Phase 9 summary out loud — does the editing-the-wording framing arrive before the Google Docs alternative?

Files changed

🤖 Generated with Claude Code

The Phase 9 summary already saved tailored-resume.md and cover-letter.md
alongside each PDF and already pointed at the re-render flow, but buried
both behind a "tweak the look" framing. Reframed to lead with the .md
edit path and demote PDF→Google Docs to a secondary option for anyone
who'd rather edit a rendered view.

No new features — discoverability and framing fix only.

Reported by @JamieP44.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@earino earino merged commit 41af73d into main Apr 29, 2026
6 checks passed
@earino earino deleted the fix/issue-60-editing-discoverability branch April 29, 2026 11:02
@earino earino mentioned this pull request Apr 29, 2026
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

PDF to editable format prompt

1 participant