Update to Vitae

{
  "description": "Coordinate a recruitment assignment from intake to candidate presentation, select the appropriate recruiter skill, and track evidence, owners, approvals, and next actions.",
  "included_files": [],
  "name": "recruitment-workflow",
  "skill_md_contents": "---\nname: recruitment-workflow\ndescription: \"Coordinate a recruitment assignment from intake to candidate presentation, select the appropriate recruiter skill, and track evidence, owners, approvals, and next actions.\"\nlicense: MIT\nmetadata:\n  version: \"0.2.4\"\n---\n\n# Recruitment workflow\n\n## Establish the assignment\n\nIdentify the role, client, workspace if connected, hiring owner, existing progress, and desired outcome. Reuse the actual current stage rather than restarting intake. Read only the records required for the assignment. Do not turn a request for one email into a full recruiting project.\n\n## Route the next step\n\n| Situation | Skill | Required handoff |\n| --- | --- | --- |\n| Requirements are unclear | `job-intake` | Brief and hiring-owner decisions |\n| Evaluation criteria are missing | `hiring-scorecard` | Agreed criteria, evidence, and anchors |\n| Need relevant candidates | `sourcing-strategy` | Search plan, approved channels/spend, provenance |\n| Have profiles to assess | `candidate-screening` | Evidence report and recruiter decision |\n| Need to approach a candidate | `candidate-outreach` | Verified facts, draft, recipient history |\n| Interview is the agreed next step | `interview-invitation` | Confirmed/proposed logistics and booking state |\n| Interviewers need a plan | `interview-kit` | Timed questions and assessment guidance |\n| Client needs a candidate summary | `candidate-presentation` | Evidence and approved sharing scope |\n\nLoad only the relevant installed skill. Skills may be installed individually; never assume a sibling directory is present. If a needed skill is missing, explain its purpose and use `bunx skills add vitaedotai/agent --skill <name>` only when installation is within the user's request. Otherwise give a concise manual handoff. Do not claim that delegation or installation happened when it did not.\n\n## Maintain state\n\nKeep a compact record with: assignment ID or descriptive label, current stage, artifact/version, evidence source, responsible person, unresolved questions, approval state, and next action with due date if supplied. Use actual Vitae records/tasks when verified tools support the requested persistence. Otherwise return a handoff table for the recruiter to save; do not claim chat memory is durable project state.\n\nPossible states are draft, ready for review, awaiting user decision, authorized, queued, completed, and failed. They are not interchangeable. Before resuming a send, record creation, import, or workflow after a timeout, inspect the current state to avoid duplication.\n\n## Execution boundaries\n\nAn agreed job brief does not authorize paid searches, candidate outreach, rejection, or public sharing. Honor explicit authorization already supplied for the same action and scope, and preserve Vitae's server approval gates. Do not repeatedly ask approval for ordinary reads or writing a requested draft.\n\nDo not auto-reject or make employment decisions. Use job-related evidence and human review. Keep candidate information out of public artifacts. If a connector lacks a needed action, produce the artifact and identify the exact manual step; do not substitute another tool with broader effects.\n\n## Beyond the initial catalog\n\nThe first release covers intake through candidate presentation. Offers, reference checks, rejection communication, placement handover, and post-placement follow-up remain explicit recruiter-owned steps. Record their owner and due action; do not invent missing specialist skills or claim those stages are automated.\n\n## Example handoff\n\nAssignment: Northbank backend engineer. Stage: screening. Completed: brief v2 and calibrated scorecard. Missing: incident-leadership evidence for Alex. Next action: recruiter reviews the screening report and chooses whether to invite Alex. Outreach: not sent. Booking: not created. No candidate stage change has been executed.\n\n## Completion\n\nReport completed artifacts and confirmed actions, open decisions, failed or unavailable capabilities, and the next owner. Stop at the requested outcome; a full assignment remains open while agreed stages still require action.\n"
}