executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
cover-letterWrite a tailored cover letter for a specific job posting
Independent GitHub snapshot · Automated classification · Original documentation governs
Priority hierarchy: See
references/priority-hierarchy.mdfor conflict resolution.
Write natural, persuasive cover letters that sound like a real professional wrote them.
scripts/
write-cover-letter.md # Cover letter writing agent prompt
Resolve the data directory using references/data-directory.md.
Resolve the data directory, then check prerequisites per references/prerequisites.md. Resume is required; profile is recommended but not blocking.
If $ARGUMENTS is "last" or empty:
DATA_DIR/jobs/ for the most recently modified folderposting.md and resume.md from that folderIf $ARGUMENTS is a URL:
DATA_DIR/jobs/posting.md and resume.mdreferences/browser-setup.mdDATA_DIR/jobs/[company-slug]-[date]/posting.md if not already savedIf the page can't be loaded, ask the user to paste the job description directly.
For the target job folder, check what exists:
posting.md - the job description (required)resume.md - a tailored resume (optional, improves quality significantly)If no tailored resume exists, use the original resume and work history profile directly.
Follow the framework in scripts/write-cover-letter.md. Use:
The cover letter must:
Save to DATA_DIR/jobs/[company-slug]-[date]/cover-letter.md
Present the cover letter to the user with:
Ask if the user wants to adjust:
Apply changes and re-save.
Structure user-facing output with these sections: