| name | discover-resume-evidence |
| description | Interview a candidate and convert incomplete experience into defensible resume evidence, candidate entries, metrics, artifacts, and unresolved questions. Use for vague resume-refinement requests, new roles or projects, unsupported claims, missing outcomes, or any rewrite that cannot be completed truthfully from current files. |
Discover Resume Evidence
Build proof before polishing prose.
Start With the Sources
- Read
profile/candidate.md.
- Resolve and read the configured evidence file and master resume.
- Inspect relevant portfolio, application, or project artifacts when available.
- Separate what is confirmed from what merely sounds plausible.
Interview Method
Ask five to seven high-impact questions per round. Prioritize gaps that could change positioning, placement, dates, ownership, or outcomes.
Ask for:
- The candidate's personal contribution.
- The artifact or deliverable created.
- Users, customers, stakeholders, or systems affected.
- The problem, constraint, and decision.
- Verifiable scale or outcome.
- Dates, title, organization, and team.
- Links, screenshots, documents, repositories, or testimonials.
After each round:
- Summarize confirmed facts.
- Extract resume-ready evidence without embellishment.
- Mark assumptions and unresolved questions.
- Update the configured evidence file.
- Ask another round only when remaining gaps materially affect the result.
Evidence States
Use explicit states:
Confirmed: directly supplied or verified.Partially confirmed: core fact is supported but important details remain.Needs confirmation: not safe to use in a final artifact.Excluded: true but irrelevant, private, misleading, or narratively weak.
Treat unlisted work as a candidate entry. Record its type, organization, dates, confidence, possible placement, and remaining questions before adding it to the master resume.
Metric Rules
Use this order:
Measured fact > user-confirmed conservative estimate > concrete qualitative evidence > omission
Never reverse-engineer an impressive number from a hunch. If a calculation uses confirmed inputs, show the calculation in evidence notes and ask the user to approve the resulting claim.
Boundaries
- Do not rewrite the resume unless the user also asks for a rewrite.
- Do not force every bullet to contain a number.
- Do not convert team results into personal ownership without proof.
- Do not expose private application answers unnecessarily.
Output
Leave the evidence file stronger than you found it and give a concise handoff: confirmed additions, bullets now supportable, remaining gaps, and the next best question or action.
