Resume Reorder Bullets

Setup

Read config.md from this skill's directory to get RESUME_PATH, CANDIDATE_NAME, and OUTPUT_DIR.

If config.md is missing or any of those variables are not set, tell the user:

"No resume path configured. Edit config.md in the skill directory and set RESUME_PATH, CANDIDATE_NAME, and OUTPUT_DIR." Then stop.

Steps

1. Validate that the user provided a JD file path as an argument. If not, tell the user and stop.
2. Read the JD file.
3. Read the resume file at RESUME_PATH.
4. Analyze the JD: identify the top priorities (e.g. cloud infra, backend performance, security, data platform). Also extract company_name and position from the JD content.
5. Produce the reordering recommendation below.
6. After printing the recommendation, ask the user:

   "Does this ordering look good? Reply yes to save the tailored resume, no to skip, or describe any changes you'd like."

7. If the user wants adjustments:
   • Incorporate their feedback into a revised recommendation.
   • Print the updated == Recommended Order == and == Summary == sections.
   • Re-ask the same confirmation question (step 6). Repeat until the user says yes or no.
8. If the user confirms:
   • Apply the recommended ordering to the full resume content (reorder subsections and bullets within them; do not change any text).
   • Derive the output filename as: {CANDIDATE_NAME}_{company_name}_{position}.pdf
     • Use underscores between words, lowercase, no special characters (e.g. karthik_siemens_senior_software_engineer.pdf).
   • Write the reordered resume to OUTPUT_DIR/{filename}.
   • Confirm to the user: Saved to OUTPUT_DIR/{filename}.
9. If the user declines, acknowledge and stop without writing any file.

Output Format

Print two sections — nothing else — before asking for confirmation.

Recommended Order

List subsections ranked by JD relevance. Within each subsection, list bullets ranked by relevance. Use only the first 5–6 words of each bullet to identify it:

== Recommended Order ==

1. Cloud and Infrastructure
   1. Cut new-region deployment...
   2. Introduced data-sovereign...
   3. Built async Lambda pipeline...
   4. Cut developer onboarding...

2. Performance and Backend
   1. Drove annotation write latency...
   2. Centralized multi-model creation...

3. Data Platform
   ...

4. Security and Auth
   ...

Summary

3–5 sentences explaining the ranking decisions: why the leading subsection leads, which subsections were deprioritized and why, and any notable intra-subsection reordering.

== Summary ==
...

Rules

• Do not edit any bullet text.
• Do not add or remove bullets.
• Do not read any files other than the JD and RESUME_PATH during the recommendation phase.
• Output only the two sections above before asking for confirmation — no preamble, no explanation outside them.