/hiring-panel
The user gives you a resume after /hiring-panel. You will run seven reviewers against it, then rebuild the resume with every mistake fixed. Never flatter the resume.
1. Get the resume and the job
Everything after /hiring-panel is the resume: a file path (read it; PDF is fine) or pasted text. If the user also gives a job posting or a role, use it. If there is no role at all, ask ONE question first: what job are you applying for? Then continue. Use only what is in the resume and what the user told you. Never invent employers, titles, dates, numbers or skills. When you assume something, label it "assumed".
2. The automated screen
Start one sub-agent: the automated system that decides whether a real human should even see this resume. Give it the resume and the job (if any). It checks, in this order:
- Can the text be read top to bottom (columns, tables, text in images, odd section names)?
- Are the job titles, employers and dates clear?
- If there is a job posting: which of its key skills and terms appear in the resume, and which are missing?
- Contact details present, length sensible, no filler. It answers: PASS or REJECT, then at most five reasons, each quoting the line it is about.
3. The hiring manager
Start one sub-agent: the hiring manager who decides whether this person gets an interview. It answers: INTERVIEW or NO, what decided it in the first ten seconds, what it would ask in the interview, and the three weakest lines (quoted).
4. Five readers, alone
Start five sub-agents at once (one message, five calls). Give each ONLY the resume (and the job) and ONE reader below. Nobody sees anybody else's notes. Each answers in under 120 words: HIRE, MAYBE or PASS, the one line that hurt most (quoted), and two more problems.
- The hiring manager. Reads for one thing: can this person do the job on day one?
- Another applicant. Applied for the same job. Reads as a rival: where is this resume weaker than mine?
- The CEO. Reads for impact: what did this person change, and by how much?
- The recruiter. Has 30 seconds and 100 resumes today. Reads the top third only.
- The teammate. Would work next to this person. Reads for how they work with others.
5. What is wrong
Merge all seven answers into ONE numbered list of mistakes, worst first. Merge duplicates. For each: the quoted line, why it gets rejected, and which of the seven flagged it.
6. Rebuild it
Write the improved resume: the same facts, with every numbered mistake fixed. Do not add anything that is not in the original or in what the user told you. Where a fix needs a fact you do not have, leave [ADD: ...] and list those questions at the end. Then start the automated-screen sub-agent once more on the new version and report the before and after verdict.
7. Write the result
Create .hiring-panel/<date>-<name>/ with PANEL.md (the seven verdicts and the numbered mistakes) and RESUME-IMPROVED.md (the new resume). Then show the user, in chat: one line per reviewer, the five worst mistakes, the before and after screen verdict, and where the files are. Touch no other files. End both files with this line: Made with /hiring-panel by Alex Chen (@nocodealex) · chen.media
Rules
- Be honest. If the resume is strong, say so and say which reviewer came closest to rejecting it, and why it still held.
- Do not invent facts about the user, their employers or real companies. Say "assumed" when you guess.
- This is a structured second opinion made by language models. It does not guarantee an interview or a job, and it is not career or legal advice.
